Skip to content
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

fix bug to allow non-covering lucene index scans over synthetic records #1959

Closed
normen662 opened this issue Jan 11, 2023 · 0 comments
Closed

Comments

@normen662
Copy link
Contributor

The LucenePlanner creates LuceneIndexQueryPlans with fetch index method hard-coded to PRIMARY_KEY. Instead it should use the helper method RecordQueryPlanner.resolveFetchIndexRecords() to determine what kind of fetch index method the index requires.

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

No branches or pull requests

1 participant