Re: [PR] Update required JTS version [solr]

2024-03-22 Thread via GitHub
dsmiley commented on PR #2273: URL: https://github.com/apache/solr/pull/2273#issuecomment-2016355523 Thanks again for contributing @ejn ; that took too long for us to merge. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and

Re: [PR] Update required JTS version [solr]

2024-03-22 Thread via GitHub
dsmiley merged PR #2273: URL: https://github.com/apache/solr/pull/2273 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@solr.apache.or

Re: [PR] Update required JTS version [solr]

2024-03-11 Thread via GitHub
janhoy commented on PR #2273: URL: https://github.com/apache/solr/pull/2273#issuecomment-1989452934 @dsmiley What do you propose as next steps? Can we cross-link issues in spatial4j and/or lucene that would be dependencies? -- This is an automated message from the Apache Git Service. To r

Re: [PR] Update required JTS version [solr]

2024-02-19 Thread via GitHub
dsmiley commented on PR #2273: URL: https://github.com/apache/solr/pull/2273#issuecomment-1953209892 If we ponder bundling JTS, I'd prefer to do such with a new "spatial-extras" Solr module for it to be included along with the subset of spatial field types that would use JTS. LatLonPointFi

Re: [PR] Update required JTS version [solr]

2024-02-18 Thread via GitHub
ejn commented on PR #2273: URL: https://github.com/apache/solr/pull/2273#issuecomment-1951787674 Note that currently Spatial4J 0.9-SNAPSHOT declares JTS 1.18.1 in its pom.xml - the last release of Spatial4J was however 0.8 back in 2020. The Spatial4J changelog notes the following regarding

Re: [PR] Update required JTS version [solr]

2024-02-18 Thread via GitHub
ejn commented on PR #2273: URL: https://github.com/apache/solr/pull/2273#issuecomment-1951776336 @risdenk I got an error with the following log entry using JTS 1.15: ` 2024-02-16 09:30:40.817 ERROR (qtp124734309-19784) [geo shard1 core_node7 geo_shard1_replica_n4] o.a.s.s.HttpSolrCall

Re: [PR] Update required JTS version [solr]

2024-02-16 Thread via GitHub
jdyer1 commented on PR #2273: URL: https://github.com/apache/solr/pull/2273#issuecomment-1948635119 With JTS on a compatible license is there any reason not to distribute it in the WEB-INF folder, making this documentation moot? -- This is an automated message from the Apache Git Service.

Re: [PR] Update required JTS version [solr]

2024-02-16 Thread via GitHub
risdenk commented on PR #2273: URL: https://github.com/apache/solr/pull/2273#issuecomment-1948518961 @ejn what errors are you seeing to back up `Due to API changes a JTS 1.17.x version is currently required`? I would recommend that Lucene upgrade. Calcite has been on 1.19.x for ~2yrs

Re: [PR] Update required JTS version [solr]

2024-02-16 Thread via GitHub
janhoy commented on PR #2273: URL: https://github.com/apache/solr/pull/2273#issuecomment-1948467690 Question: I see now that Solr already bundles `solr/modules/sql/lib/jts-core-1.19.0.jar`, pulled in by Calcite SQL parser. Is that JAR even used by the SQL parser? Could we coordinate by movi

[PR] Update required JTS version [solr]

2024-02-16 Thread via GitHub
ejn opened a new pull request, #2273: URL: https://github.com/apache/solr/pull/2273 Due to API changes a JTS 1.17.x version is currently required. The appropriate JTS version may be determined based on the JTS version used for tests in Lucene, referenced in https://github.com/apache/