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
[GEO] Fork Lucene's LatLonShape Classes to local lucene package #36794
Conversation
Lucene 7.6 uses a smaller encoding for LatLonShape. This commit forks the LatLonShape classes to Elasticsearch's local lucene package. These classes will be removed on the release of Lucene 7.6.
Pinging @elastic/es-analytics-geo |
@imotov having some issues w/ sql-cli and |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This might be more a build issue than a sql-cli issue. It looks like the forbidden APIs in es-server-signatures.txt
are applied to all modules rather than just the server module like the name suggests, which turns out to be an issue for modules that don't depend on lucene-sandbox where LatLonShape lives. Maybe the best way to proceed in the short term is to have a dedicated signatures file for these classes that live in sandbox and add them only in the Gradle build file for the server module (see eg. how rest-high-level-client specific signatures are added in client/rest-high-level/build.gradle
)? @atorok Any opinion?
server/src/test/java/org/elasticsearch/index/query/GeoShapeQueryBuilderTests.java
Outdated
Show resolved
Hide resolved
@nknize found it. Running the rest of precommit to make sure it didn't break anything else and then will push the changes. |
SQL cli doesn't use the server and doesn't pull most of the server's dependencies. So, we shouldn't try checking server's signatures here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm good with Igor's workaround.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM2
Excellent... as soon as CI comes back (hopefully succesfully) I will merge this to master. We'll let CI settle out overnight with these two big PRs and if all looks good tomorrow (and approvals are in), I'll merge #36743 and backport this to 6.6 |
…tic#36794) Lucene 7.6 uses a smaller encoding for LatLonShape. This commit forks the LatLonShape classes to Elasticsearch's local lucene package. These classes will be removed on the release of Lucene 7.6.
@jpountz The reason we configure the server signatures is that it's possible for projects depending on server to use the APIs forbidden in server via transitive dependencies. We could however be smarter about it and only add those signature if the project actually depends on server. I'll send a PR to make this happen. |
I run the command
Removing the Lucene tags remove the problem. |
Remove lucene tags as they break gradle javadoc job Relates elastic#36794
Remove lucene tags as they break gradle javadoc task Relates #36794
Remove lucene tags as they break gradle javadoc task Relates elastic#36794
Remove lucene tags as they break gradle javadoc task Relates #36794
Remove lucene tags as they break gradle javadoc task Relates elastic#36794
Lucene 7.6 uses a smaller encoding for LatLonShape. This commit forks the LatLonShape classes to Elasticsearch's local lucene package. These classes will be removed on the release of Lucene 7.6.