Skip to content

GH-174 #175

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Feb 18, 2025
Merged

GH-174 #175

merged 2 commits into from
Feb 18, 2025

Conversation

mipo256
Copy link
Contributor

@mipo256 mipo256 commented Feb 16, 2025

WIP

Solving #174.

Spring Data, as of 3.4, does not expose the repository invocation metadata unless explicitly specified to do so. The motivation for this change is that adding an Advisor for exposing methods is a bit resource intensive.

Unfortunately, we cannot really do anything in the dialect itself, since the Dialect by its design, is supposed to work on SQL level only. That is to say, it does not know anything about PersistentEntity or the QueryExecutorMethodInterceptor.

So, what we're actually doing is - we're enabling the metadata exposure per RepositoryFactoryBeanSupport-basis. That is to say, we do not enable it for every repository in the system. We're just enabling it for those that require that, in our case, annotated with @ViewIndex

@mipo256 mipo256 marked this pull request as ready for review February 17, 2025 09:46
@KirillKurdyukov KirillKurdyukov linked an issue Feb 17, 2025 that may be closed by this pull request
@KirillKurdyukov KirillKurdyukov merged commit bb7321d into ydb-platform:main Feb 18, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[BUG]: No MethodInvocation found
2 participants