Changed auto generated index name - #503
Conversation
mikemccand
left a comment
There was a problem hiding this comment.
Thank you for tackling this! It is super annoying when it strikes!
As a short-term workaround, you can tell your local Competition (or Index instance maybe) which index name you want to use, overriding this overly-verbose default.
|
Looks like you need a |
|
This PR has not had activity in the past 2 weeks, labeling it as stale. If the PR is waiting for review, notify the dev@lucene.apache.org list. Thank you for your contribution! |
| JAVA_COMMAND = "%s -server -Xms2g -Xmx2g --add-modules jdk.incubator.vector -XX:+HeapDumpOnOutOfMemoryError -XX:+UseParallelGC" % JAVA_EXE | ||
| else: | ||
| print("use java command %s" % JAVA_COMMAND) # pyright: ignore[reportUnboundVariable] # TODO: fix how variables are managed here | ||
| print("use java command %s" % JAVA_COMMAND) # pyright: ignore[reportUndefinedVariable] # TODO: fix how variables are managed here |
There was a problem hiding this comment.
LOL this is so painful -- it fails on GitHub actions this way, but passes for our dev boxes. I go back and forth which is the lesser evil. And I wish we could explain why it's not consistent b/w our dev boxes and GitHub actions... we fix the version of basedpyright=1.29.0 in requirements.txt.
There was a problem hiding this comment.
Yeah, it was failing in the build on Github, shall we keep it like this?
| # /root/jdk1.6.0_31/bin/java -XX:+UnlockExperimentalVMOptions -XX:+UseG1GC | ||
|
|
||
| /opt/zing/zingLX-jdk1.6.0_31-5.2.0.0-18-x86_64/bin/java -verbose:gc -Xms40G -Xmx40G -cp .:$LUCENE_HOME/build/core/classes/java:$LUCENE_HOME/build/highlighter/classes/java:$LUCENE_HOME/build/test-framework/classes/java:$LUCENE_HOME/build/queryparser/classes/java:$LUCENE_HOME/build/suggest/classes/java:$LUCENE_HOME/build/analysis/common/classes/java:$LUCENE_HOME/build/grouping/classes/java perf.SearchPerfTest \ | ||
| -indexPath /large/indices/wikimediumall.lucene4x.Lucene40.nd33.3326M/index \ |
There was a problem hiding this comment.
Is this just noise/wrong? Since we turn it into hash, this new version (removing the Lucene40 part) won't be right either?
| import org.apache.lucene.util.fst.Util; | ||
|
|
||
| // javac -cp lucene/core/build/libs/lucene-core-10.0.0-SNAPSHOT.jar IndexToFST.java; java -cp .:lucene/core/build/libs/lucene-core-10.0.0-SNAPSHOT.jar IndexToFST /l/indices/wikimediumall.trunk.facets.taxonomy:Date.taxonomy:Month.taxonomy:DayOfYear.taxonomy:RandomLabel.taxonomy.sortedset:Date.sortedset:Month.sortedset:DayOfYear.sortedset:RandomLabel.sortedset.Lucene90.Lucene90.dvfields.nd33.3326M/index | ||
| // javac -cp lucene/core/build/libs/lucene-core-10.0.0-SNAPSHOT.jar IndexToFST.java; java -cp .:lucene/core/build/libs/lucene-core-10.0.0-SNAPSHOT.jar IndexToFST /l/indices/wikimediumall.trunk.nd33.3326M/index |
| raise | ||
|
|
||
| # After successful indexing, write the config file | ||
| write_index_config(fullIndexPath, current_config) |
There was a problem hiding this comment.
Can we assert can_reuse_index(...) here?
mikemccand
left a comment
There was a problem hiding this comment.
Very close! Thank you @shubhamsrkdev!
|
This PR has not had activity in the past 2 weeks, labeling it as stale. If the PR is waiting for review, notify the dev@lucene.apache.org list. Thank you for your contribution! |
|
This PR has not had activity in the past 2 weeks, labeling it as stale. If the PR is waiting for review, notify the dev@lucene.apache.org list. Thank you for your contribution! |
The auto generated index name though informative is very long leading to errors like:
This PR reduces the file name size and also added a metadata file to verify if the index is not reduced.
Fixes #198