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
Allow AnalyzeRequestBuilder to be given an arbitrary text array #3023
Labels
Comments
s1monw
added a commit
that referenced
this issue
May 14, 2013
The default size used to be 2x availableProcessors which seemed to be a to lowish value in practice. 3x appeared to be a sweetspot for most application. The default is now 3 x availableProcessors Closes #3023
I referenced the wrong issue from this commit... reopening |
This could be supported when #5866 is implemented |
johtani
added a commit
to johtani/elasticsearch
that referenced
this issue
Apr 28, 2015
Add support array text as a multi-valued for AnalyzeRequestBuilder Add support array text as a multi-valued for Analyze REST API Add docs Closes elastic#3023
johtani
added a commit
to johtani/elasticsearch
that referenced
this issue
Apr 28, 2015
Add support array text as a multi-valued for AnalyzeRequestBuilder Add support array text as a multi-valued for Analyze REST API Add docs Closes elastic#3023
johtani
added a commit
to johtani/elasticsearch
that referenced
this issue
Apr 30, 2015
Fix some comments Closes elastic#3023
johtani
added a commit
to johtani/elasticsearch
that referenced
this issue
May 2, 2015
Change names of IndicesAdminClient methods Closes elastic#3023
johtani
added a commit
to johtani/elasticsearch
that referenced
this issue
May 13, 2015
Remove bad naming method Add prepareAnalyze() with no params Add setText to AnalyzeRequestBuilder Closes elastic#3023
johtani
added a commit
to johtani/elasticsearch
that referenced
this issue
May 15, 2015
remove setSource JSON Closes elastic#3023
mute
pushed a commit
to mute/elasticsearch
that referenced
this issue
Jul 29, 2015
The default size used to be 2x availableProcessors which seemed to be a to lowish value in practice. 3x appeared to be a sweetspot for most application. The default is now 3 x availableProcessors Closes elastic#3023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The AnalyzeRequestBuilder is useful for seeing exactly how a text string value will be analyzed. But when a document can contain multiple values, it's often difficult to guess the tokens and token positions that result when ES is indexing a multi-valued field.
It would be very helpful to have the AnalyzeRequestBuilder accept an array of String objects, or perhaps even a JSON document with some restrictions, so that a real-world multi-valued document field is more accurately modeled and analyzed.
The text was updated successfully, but these errors were encountered: