-
Notifications
You must be signed in to change notification settings - Fork 642
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Code snippets on https://lucenenet.apache.org/ doesn't works. #453
Comments
Thanks for letting us know about the issues you are having with the examples on the home page. We will surely look into finding ways to make the code that you see there runnable. In the meantime, there are several runnable demos that you can inspect to get a feel for how the components work together to provide indexing and search: General SearchFaceted Search
Runnable DemosDo note that all of the above examples from |
I tried to run the cli to see if the issue is not specific to my PC, but it look like the CLI need configuration after install and the doc doesn't specify it:
So I found out that, the demo is working, but I was catching every exception and never let it run to completion ><. |
Thanks for the additional report. I have confirmed the behavior and discovered this has been failing since 4.8.0-beta00009.
It seems that when the I am considering just supplying a In addition, it is clear we need some basic smoke tests to ensure that the tool will install and run without throwing exceptions. In the meantime, you can work around this problem by manually adding an empty JSON file named appsettings.json{
}
The location it is looking for the file on your system in is in the error message:
But if you need more help locating where the tool is located, see How to manage .NET tools. |
I was running the tool only to know if LuceneNet could run on my machine :p. Is it expected that Lucene.Net throws exceptions internally (but catches them) in normal operations? |
This is a line-by-line port of Java Lucene. The designers made the unfortunate choice of relying on exceptions for control flow by using exceptions as messages similar to events. This behavior was deemed too much of a risk to change due to the fact that some bugs can only be found by comparing where the execution paths diverge between Lucene and Lucene.NET. |
…d run it to ensure it can be installed and has basic functionality. (See apache#453)
…t server, since it is required by installation tests (See apache#453)
…d run it to ensure it can be installed and has basic functionality. (See apache#453)
…t server, since it is required by installation tests (See apache#453)
…d run it to ensure it can be installed and has basic functionality. (See apache#453)
…t server, since it is required by installation tests (See apache#453)
…d run it to ensure it can be installed and has basic functionality. (See #453)
…t server, since it is required by installation tests (See #453)
Hello,
I'm currently trying to get started on lucene.net, but no success so far.
First small issue:
The snippet on https://lucenenet.apache.org/ requires
Lucene.Net.Analysis.Common
which was not indicated.Second issue, if I simply copy/paste the first snippet, it throws me a
Lucene.Net.Index.IndexNotFoundException: 'no segments* file found in [truncated]
, on the IndexWriter constructor.The text was updated successfully, but these errors were encountered: