[GitHub] [lucene] dweiss commented on issue #12057: ban finalizers in the build somehow (worst-case: use error-prone)

dweiss commented on issue #12057: URL: https://github.com/apache/lucene/issues/12057#issuecomment-1368723771 Even a simplistic regexp/substring expression added to rat checks would work here, I think? this method is fairly uniquely-named. There are better alternatives but they will add over

[GitHub] [lucene] uschindler commented on issue #12057: ban finalizers in the build somehow (worst-case: use error-prone)

uschindler commented on issue #12057: URL: https://github.com/apache/lucene/issues/12057#issuecomment-1368738480 Yeah, similar like the LOG statement checks in Solr? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the

[GitHub] [lucene] sebastiano1972 opened a new issue, #12059: Recurring index corruption

sebastiano1972 opened a new issue, #12059: URL: https://github.com/apache/lucene/issues/12059 We are experimenting with Elastic Search deployed in Azure Container Instances (Debian + OpenJDK). The ES indexes are stored into an Azure file share mounted via SMB (3.0). The Elastic Search clust

[GitHub] [lucene] uschindler commented on issue #12059: Recurring index corruption

uschindler commented on issue #12059: URL: https://github.com/apache/lucene/issues/12059#issuecomment-1368787343 Hi, Samba/CIFS is generally working as file store - in contrast to NFS, which should never ever be used as file system; but the problems you describe here are surely related t

[GitHub] [lucene] uschindler closed issue #12059: Recurring index corruption

uschindler closed issue #12059: Recurring index corruption URL: https://github.com/apache/lucene/issues/12059 -- 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-

[GitHub] [lucene] uschindler commented on issue #12059: Recurring index corruption

uschindler commented on issue #12059: URL: https://github.com/apache/lucene/issues/12059#issuecomment-1368788012 This issue should be better discussed on the mailing list, it is not a bug/iusse at all. -- This is an automated message from the Apache Git Service. To respond to the message,

[GitHub] [lucene] uschindler commented on issue #11701: Deadlock in AnalysisSPILoader [LUCENE-10665]

uschindler commented on issue #11701: URL: https://github.com/apache/lucene/issues/11701#issuecomment-1368789210 Thanks for feedback, well appreciated. -- 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

[GitHub] [lucene] sebastiano1972 commented on issue #12059: Recurring index corruption

sebastiano1972 commented on issue #12059: URL: https://github.com/apache/lucene/issues/12059#issuecomment-1368804331 Hi Uwe, thank you for your kind reply. To answer your question, we are experimenting with Azure Container Instances, because of their relative simplicity, but th

[GitHub] [lucene] rmuir commented on issue #12057: ban finalizers in the build somehow (worst-case: use error-prone)

rmuir commented on issue #12057: URL: https://github.com/apache/lucene/issues/12057#issuecomment-1368933723 that's true, it is another option. I am still investigating the ECJ one. It is a bit sad that we are so messy about deprecations and can't simply use the compiler's support. Fo

[GitHub] [lucene] gsmiller commented on pull request #12055: Better skipping for multi-term queries with a FILTER rewrite.

gsmiller commented on PR #12055: URL: https://github.com/apache/lucene/pull/12055#issuecomment-1369212139 +1 to this approach in general. I do wonder if the distribution assumptions generally hold if we start looking at "term in set" queries though. That's sort of irrelevant right now

[GitHub] [lucene] vatsalpatel3689 opened a new pull request, #12060: fixing fkltr change'

vatsalpatel3689 opened a new pull request, #12060: URL: https://github.com/apache/lucene/pull/12060 ### Description -- 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 commen

[GitHub] [lucene] rmuir commented on pull request #12055: Better skipping for multi-term queries with a FILTER rewrite.

rmuir commented on PR #12055: URL: https://github.com/apache/lucene/pull/12055#issuecomment-1369222376 there's no reason to duplicate a bunch of code just because of minor changes to a rewrite method. we can have more than one or two of these rewritemethods, and use different ones for diffe

[GitHub] [lucene] vatsalpatel3689 closed pull request #12060: fixing fkltr change'

vatsalpatel3689 closed pull request #12060: fixing fkltr change' URL: https://github.com/apache/lucene/pull/12060 -- 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

[GitHub] [lucene] aykutfirat commented on issue #11507: Increase the number of dims for KNN vectors to 2048 [LUCENE-10471]

aykutfirat commented on issue #11507: URL: https://github.com/apache/lucene/issues/11507#issuecomment-1369369480 Lots of things happened since Aug, like the arrival of ChatGPT, and people's increased desire to use OpenAI's state of the art embeddings which are of size 1536. Can you at least

[GitHub] [lucene] LuXugang merged pull request #12046: Out of boundary in CombinedFieldQuery#addTerm

LuXugang merged PR #12046: URL: https://github.com/apache/lucene/pull/12046 -- 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...@lucene.ap