Thanks Adrien, Micheal, Trejkaz.
You guys were right.
I was concentrating my energy at wrong place.
We have two types of indexes:
1. File based directory: which we use for text search. Here we make use of
searcher manager.
2. In memory directory: which we use for auto complete/auto suggestio
If you open the source, you will see it internally calls
this.getBestFragments(tokenStream, text, maxNumFragments) which in turn
calls
this.getBestTextFragments(tokenStream, text, true, maxNumFragments) (*with
flag true*) which will merge the fragments automatically.
Regards.
--
View this
Thanks for advice
However I asked about different API semantic:
String fragments = highlighter.*getBestFragments*(tokenStream, value,
*3*,FRAGMENT_DELIMITER
);
when
fragmenter = new SimpleSpanFragmenter(queryScorer,*5*);
highlighter.setTextFragmenter(fragmenter);
Regards
Please pass false to mergeContiguousFragments in
getBestTextFragments(TokenStream tokenStream, String text, boolean
mergeContiguousFragments, int maxNumFragments) and it should work as
expected.
Regards.
--
View this message in context:
http://lucene.472066.n3.nabble.com/getBestFragments-with-
Hi all,
I have the following 2 indexed data for the field, title_t_en:
"\"War and Peace\" by \"Leo Tolstoy\"
\"Three sisters" by \"Anton Chekhov\""
I am searching by : +((title_t_en:war) (title_t_en:sister))
For every found doc's index *value* the following code is called:
On Fri, Oct 14, 2016 at 2:47 AM, Ashley Ryan wrote:
> Obviously, our work around of escaping the angle brackets works as we need
> it to, but it seems to me that your documentation is incorrect. Am I
> misunderstanding the documentation or conflating the issue I'm seeing with
> the topic of specia
Hello,
I'm looking to see if there is any documentation describing situations
which could trigger a shard replica to go into recovery. We're having
issues with some of our replicas randomly going into recovery mode. For
example, I know of certain conditions when this may happen such as if
the
Hi,
I'm working on a project that uses
the org.apache.lucene.queryparser.flexible.standard.parser.StandardSyntaxParser.
I found in the documentation online that the list of special characters is
as follows:
+ - && || ! ( ) { } [ ] ^ " ~ * ? : \
This list does not include angle brackets (< >) but
These sounds like good ideas Trejkaz ... maybe open an issue and make
a starting patch so we can iterate?
I agree a try-w-resources solution, and/or a lambda solution, could be better.
Did you already share how you got it working for multiple indices?
Mike McCandless
http://blog.mikemccandless.
Thanks, will follow this way.
> On 13 Oct 2016, at 06:02, Trejkaz wrote:
>
> On Thu, Oct 13, 2016 at 5:04 AM, Mikhail Khludnev wrote:
>> Hello,
>> Why not "To:local.one -(To:[* TO local.one} To:{local.one TO *)" ?
>
> That would not match example 2:
>
>> 2. To:other.one, third.one,
>
> Thi
10 matches
Mail list logo