Re: [PR] Add AbstractKnnVectorQuery.seed for seeded HNSW [lucene]

2024-10-30 Thread via GitHub
github-actions[bot] commented on PR #13635: URL: https://github.com/apache/lucene/pull/13635#issuecomment-2448727288 This PR has not had activity in the past 2 weeks, labeling it as stale. If the PR is waiting for review, notify the d...@lucene.apache.org list. Thank you for your contributi

Re: [PR] Introduce multiSelect for ScalarQuantizer [lucene]

2024-10-30 Thread via GitHub
github-actions[bot] commented on PR #13919: URL: https://github.com/apache/lucene/pull/13919#issuecomment-2448726887 This PR has not had activity in the past 2 weeks, labeling it as stale. If the PR is waiting for review, notify the d...@lucene.apache.org list. Thank you for your contributi

Re: [I] Performance difference between files getting opened with IOContext.RANDOM vs IOContext.READ during merges [lucene]

2024-10-30 Thread via GitHub
navneet1v commented on issue #13920: URL: https://github.com/apache/lucene/issues/13920#issuecomment-2448575148 > So as said before: Just change the madvise on already open indexinput. @uschindler, sorry for the confusion. The plan was never to open multiple files. The question was mo

Re: [I] Can Lucene support selective preloading of just slices/files within a CFS file? [lucene]

2024-10-30 Thread via GitHub
uschindler commented on issue #13967: URL: https://github.com/apache/lucene/issues/13967#issuecomment-2448351255 In general, I would recommend to allow that, too. We are currently a bit planning how to make CFS files and madvise work together in a better way and this already improved

Re: [I] Performance difference between files getting opened with IOContext.RANDOM vs IOContext.READ during merges [lucene]

2024-10-30 Thread via GitHub
uschindler commented on issue #13920: URL: https://github.com/apache/lucene/issues/13920#issuecomment-2448346922 > > Opening new readers is too expensive and mostly not useful. > > @uschindler one question on this, the reason why you say opening new readers is expensive because reader

Re: [PR] Add a Better Binary Quantizer (RaBitQ) format for dense vectors [lucene]

2024-10-30 Thread via GitHub
mayya-sharipova commented on code in PR #13651: URL: https://github.com/apache/lucene/pull/13651#discussion_r1823251497 ## lucene/core/src/java/org/apache/lucene/codecs/lucene101/Lucene101BinaryQuantizedVectorsFormat.java: ## @@ -0,0 +1,125 @@ +/* + * Licensed to the Apache Soft

Re: [PR] Parse escaped brackets and spaces in range queries [lucene]

2024-10-30 Thread via GitHub
benchaplin commented on PR #13887: URL: https://github.com/apache/lucene/pull/13887#issuecomment-2448040728 Sorry for the failed builds, didn't realize I had an incorrect checksum. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitH

Re: [I] Can Lucene support selective preloading of just slices/files within a CFS file? [lucene]

2024-10-30 Thread via GitHub
mikemccand commented on issue #13967: URL: https://github.com/apache/lucene/issues/13967#issuecomment-2447946332 One simple workaround is to disable compound file format (`.cfs` files). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to

Re: [I] Could Lucene's default Directory (`FSDirectory.open`) somehow preload `.vec` files? [lucene]

2024-10-30 Thread via GitHub
gautamworah96 commented on issue #13551: URL: https://github.com/apache/lucene/issues/13551#issuecomment-2447869710 Opened https://github.com/apache/lucene/issues/13967 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use t

[I] Can Lucene support selective preloading of just slices/files within a CFS file? [lucene]

2024-10-30 Thread via GitHub
gautamworah96 opened a new issue, #13967: URL: https://github.com/apache/lucene/issues/13967 ### Description At Amazon Product Search, we warm up our service by preloading vector files into RAM and use the `mmapDir.setPreload` API for this. However, when vector files get compacted

Re: [PR] Remove vector values copy() methods, moving IndexInput.clone() and temp storage into lower-level interfaces [lucene]

2024-10-30 Thread via GitHub
ChrisHegarty commented on PR #13872: URL: https://github.com/apache/lucene/pull/13872#issuecomment-2446886272 FYI - I created the following issue to track the possibility of adding a scorer interface that scores one ordinal against another, without the need to create an instance of a scorer

[I] Evaluate adding a double addressing vector scorer [lucene]

2024-10-30 Thread via GitHub
ChrisHegarty opened a new issue, #13966: URL: https://github.com/apache/lucene/issues/13966 Merging and rebuilding the HNSW graph is heavy on the creation of vector scorer, when in many common cases, we just wanna score one vector ordinal against another. ![Screenshot 2024-10-25 at

Re: [I] Unable to Tessellate shape for a valid Polygon according to GDAL/OGR and PostGIS [lucene]

2024-10-30 Thread via GitHub
iverase commented on issue #13841: URL: https://github.com/apache/lucene/issues/13841#issuecomment-2446320111 >According to [GeoJSONLint](https://geojsonlint.com/) this polygon doesn't follow the "right-hand rule". I don't think that matters as the tessellation algorithm would order the

Re: [PR] Speed up advancing within a block, take 2. [lucene]

2024-10-30 Thread via GitHub
jpountz merged PR #13958: URL: https://github.com/apache/lucene/pull/13958 -- 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.apa