Hi,
I have updated my schema.xml as mentioned in the previous posts using
This does the auto-complete, but it does it at every portion of the text
(not just at the beginning) (prefix)
Hi Salman,
that's because you're using a StandardTokenizer. Try with something like
this (copied, pasted and changed using my phone so probably with a lot of
mistakes ;) but you should be able to get what I mean). BTW I don't know if
that's the case but I would also put a MappingCharFilterFactory
Thanks a lot Andrea. It did work.
However, just for my understanding, can you please explain more how did you
make it work for prefixes. I know you mentioned using another Tokenizer but
for example, if I want to tweak it later on to work on suffixes or within
phrases how should I go about that?
T
Do you mean "phrase" or "term" prefixes? If you try to put a field value
(two or more terms) in the analysis page you will see what the index
analyzer chain (of my example field type) is doing. The whole value is
managed as a single-ngrammed token, so you will get only a phrase prefix
search, as in
Sorry, my damned mobile: "Is that close to what you were looking for?"
2015-12-06 12:07 GMT+01:00 Andrea Gazzarini :
> Do you mean "phrase" or "term" prefixes? If you try to put a field value
> (two or more terms) in the analysis page you will see what the index
> analyzer chain (of my example fi
That is right. I am actually looking for phrase prefixes not each term
prefix within the phrase. That satisfies my requirements. However, my
additional question was how do I manipulate the filedType to later allow
for suffix matches as well? or will that be a completely different
fieldType definiti
There's nothing cluster specific in security.json if you're using those
plugins. It is totally safe to just take the file from one cluster and
upload it for another for things to work.
On Sat, Dec 5, 2015 at 3:38 AM, Oakley, Craig (NIH/NLM/NCBI) [C] <
craig.oak...@nih.gov> wrote:
> Looking throug
For suffix matches, you copy text the field and in the different type add
string reversal for both index and query portions. So you are doing prefix
matching algorithm but on reversed strings.
I can dig up an example if it is not clear.
On 6 Dec 2015 8:06 am, "Salman Ansari" wrote:
> That is rig
Hi,
I am trying to import xml files using data import request handler.
When i import xml file of 1,4 kB size, it works correctly. However, i
cannot import xml file of 4 GB size to Solr. It does not present any
error, but i receive the following answer:
*Indexing completed. Added/Updated: 0 docu
There should be no limit. Try 100K, 50K sizes. Maybe you have an error
somewhere. Also check Solr logs, not just DIH messages.
On 6 Dec 2015 3:56 pm, "Kate Kas" wrote:
> Hi,
>
> I am trying to import xml files using data import request handler.
>
> When i import xml file of 1,4 kB size, it works
Scenario: Document should be matched/returned ONLY IF user entered search
text is having ALL the terms of single indexed field in any order.
Ex.
Document has got only 2 fields. Id and title.
Below document is indexed.
{"id":"1", "title": "refrigerator water filter"}
Below search text should NOT
Still, 4GB is going to take a lot of resources to
1> hold the whole thing in memory and parse
2> process.
You may simply be hitting a timeout.
But I would ask what practical use indexing a 4GB file is.
Likely it'll be found by virtually every search (assuming
there's a huge text field or two in t
12 matches
Mail list logo
