Hi Tomoko
Just noticed that you resolved the issue and also did some additional
improvement :-)
Thanks a lot!
Michael
Am 14.07.21 um 07:52 schrieb Michael Wechner:
sure, I understand, but I just wanted to ask whether such a change
makes sense actually.
I have created a Jira ticket
sure, I understand, but I just wanted to ask whether such a change makes
sense actually.
I have created a Jira ticket
https://issues.apache.org/jira/browse/LUCENE-10024
and added the patch as attachment. Let me know if you prefer a pull request.
Cheers
Michael
Am 14.07.21 um 03:43 schrieb
We don't accept patches by email... please open a Jira.
2021年7月14日(水) 5:58 Michael Wechner :
>
> would the following patch make sense?
>
> git diff lucene/luke/src/
> diff --git
> a/lucene/luke/src/java/org/apache/lucene/luke/app/IndexHandler.java
>
would the following patch make sense?
git diff lucene/luke/src/
diff --git
a/lucene/luke/src/java/org/apache/lucene/luke/app/IndexHandler.java
b/lucene/luke/src/java/org/apache/lucene/luke/app/IndexHandler.java
index f3fc635872b..ad13745eec8 100644
---
I analyzed the logs and the class/method
lucene/luke/src/java/org/apache/lucene/luke/models/util/IndexUtils.java#openIndex(String,
String)
and realized that the problem was not the index itself, but that the
index directory/path did not exist anymore.
I forgot that I renamed the index
thanks again for your feeback!
I will give it a try and get back if I should have more questions :-)
Thanks
Michael
Am 13.07.21 um 09:58 schrieb Tomoko Uchida:
I think beside the query it would be nice if Luke would display some
"stats" of the index, for example the various fields beside the
> I think beside the query it would be nice if Luke would display some
> "stats" of the index, for example the various fields beside the actual
> vector and also how many vectors are inside the index
It would be a good start point, I think.
> Can you give me a hint where in the code this check
Am 13.07.21 um 04:22 schrieb Tomoko Uchida:
There isn't any plans for that, and I'm not sure what is actually
expected of the GUI tool
yes, I understand, the input for the query would have to be an embedding
(vector of for example 768 dimensions).
I currently see two possibilities to do
There isn't any plans for that, and I'm not sure what is actually
expected of the GUI tool to support vector search codec (it'd be
costly operation to decode vectors with several hundreds of
dimensions); though I am open to new ideas which are feasible and
useful.
Nonetheless the error you saw is
