I was wondering if there was a way to return a substring (with offset &
count) on a field in a GET request? The problem I am hitting is, I have the
ID of the document, but I only want to retrieve N number of bytes from M
offset.
there is no such thing that can do that currently.
simon
On Thursday, March 7, 2013 2:57:48 PM UTC+1, Anurag wrote:
Hi!
I was wondering if there was a way to return a substring (with offset &
count) on a field in a GET request? The problem I am hitting is, I have the
ID of the document, but I only want to retrieve N number of bytes from M
offset.
there is no such thing that can do that currently.
simon
On Thursday, March 7, 2013 2:57:48 PM UTC+1, Anurag wrote:
Hi!
I was wondering if there was a way to return a substring (with offset &
count) on a field in a GET request? The problem I am hitting is, I have the
ID of the document, but I only want to retrieve N number of bytes from M
offset.
Hi, I have some quite large documents (about 30k) and I want to get only an excerpt
of each document, for example, 250 characters. It really does not matter
if they are the first 250 characters or a chunk in the middle. I would
prefer not doing it a client side to avoid these large documents moving in
the network. This thread looks very related.
Is there any progress on this (use a GET request) from March?
Can this be done with a preparedSearch or any other mechanism?
Looks something quite trivial to not have an easy response.
Hi, I have some quite large documents (about 30k) and I want to get
only an *excerpt
of each document*, for example, 250 characters. It really does not matter
if they are the first 250 characters or a chunk in the middle. I would
prefer not doing it a client side to avoid these large documents moving in
the network. This thread looks very related.
Is there any progress on this (use a GET request) from March?
Can this be done with a preparedSearch or any other mechanism?
Looks something quite trivial to not have an easy response.
Highlighting can return an excerpt from the beginning of the document if it
doesn't find a match in the document. You can't do that with an HTTP GET.
You still have to POST the search with the right highlihting configuration.
Tested with 1.0.0.beta1 but does not seem to be working.
For the query below, the highlights are returned successfully when the
record matches key. However, despite *setHighlighterNoMatchSize(250) *has
been set, unmatching records does not return 250 characters from the start
of the record as expected.
Tested in 0.90.9 (December 23, 2013) as seems newer than 1.0.0.beta1 (November
6, 2013) and same issue: no highlighting results when key does not match,
despite setHighlighterNoMatchSize(250) has been set.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.