Re: querying on field of type string doesn't work as expected

That’s correct - the original source of my data which I was crawling had 160 as space. This took a while to find. :) Solr is working fine. Thank you ! On Tue, 20 Nov 2018 at 1:28, Shawn Heisey wrote: > On 11/19/2018 3:31 PM, Angel Todorov wrote: > > the *real* issue is that SOL

Re: querying on field of type string doesn't work as expected

this "Some Text". But why does SOLR do this ? Thanks On Mon, Nov 19, 2018 at 11:50 PM Angel Todorov wrote: > The only thing that works is this: {!term f=MyCustomField}Some Text > > Thanks > > > On Thu, Nov 15, 2018 at 7:13 PM Erick Erickson > wrote: >

Re: querying on field of type string doesn't work as expected

Try comparing strings char by char. White spaces are sometimes > unprintable characters.Eric.Sent from my Samsung Galaxy smartphone. > > Original message From: Angel Todorov < > attodo...@gmail.com> Date: 2018-11-15 04:06 (GMT-05:00) To: > solr-user@lucene.apache.org Su

Re: querying on field of type string doesn't work as expected

ustomField:\"Some Text\"", "parsedquery":"MyCustomField:Some Text", "parsedquery_toString":"MyCustomField:Some Text", "explain":{}, "QParser":"LuceneQParser", Thank you On Thu, Nov 15, 2018 at 3:54 A

querying on field of type string doesn't work as expected

Hi guys, I have SOLR 6.5 , and a custom defined field which is of type string (not text or text_general). In some document, there is the value for that field, for example, "Some Text" . When I query by myFieldName:"Some Text" , I don't get any matches, but I think I should, because this matches

Luke request handler - lastModified - is this for a softCommit or a hardCommit ?

Hello, Wondering whether the Luke handler's response for the lastModified field refers to a hard commit only, or any that has happened last, including a soft commit? Thank you Angel

Re: autoSoftCommit doesn't work as expected / documented

So that's why you need one extra... > > On Thu, Aug 24, 2017 at 6:59 AM, Angel Todorov <attodo...@gmail.com> > wrote: > > > I also tested, of course, by setting a value of 0, expecting that it > would > > work in the way I expect it to , but unfortunately -

Re: autoSoftCommit doesn't work as expected / documented

I also tested, of course, by setting a value of 0, expecting that it would work in the way I expect it to , but unfortunately - it doesn't. Nothing is committed in that case. Thanks On Thu, Aug 24, 2017 at 1:54 PM, Angel Todorov <attodo...@gmail.com> wrote: > Hi all, > > I

autoSoftCommit doesn't work as expected / documented

Hi all, I have this in my config: 1 My expectation is that SOLR will make changes available in the index after every document change. But this doesn't work - I need to do _ another _ update in order for the changes to be visible. Basically it's like: if maxDocs is 1, it

Re: FreeTextSuggester throwing error "token must not contain separator byte"

Hi guys, Thank you very much for the help. I think I see what is going on. yes it is related to the Shingle filter added to the analyzer. It shouldn't be there if a FreeTextLookup factory is used in the suggester, because it creates conflict. The StandardTokenizer removes punctuation, including

Re: FreeTextSuggester throwing error "token must not contain separator byte"

see 6 non-space tokens. > > Have a look at your analysis chain and see why you are getting this. > Cheers -- Rick > > On July 24, 2017 4:27:00 PM EDT, Angel Todorov <attodo...@gmail.com> > wrote: > >Hi guys, > > > >I am trying to setup the FreeTextSuggeste

FreeTextSuggester throwing error "token must not contain separator byte"

Hi guys, I am trying to setup the FreeTextSuggester/ Lookup Factory in a suggester definition in SOLR. Unfortunately while the index is building, I am encountering the following errors: *"msg":"tokens must not contain separator byte; got token=[30 20 30 20 32 20 72 20 61 6c 6c 65 6e 20 72] but

Solr suggester query with quotes produces different results

Hi guys, I have the Suggester configured using the FreeTextFactory. Noticed that if I dont use quotation marks, I only get single term results. If i use quotation marks around my query, then I only get results that are comprised of multiple terms. There is no configuration that would return both

Re: SOLR Suggester returns either the full field value or single terms only

Hi Alessandro, Thanks. I've experimented a bit more and here is what I have discovered - If my query is enclosed with quotes, then i get multi terms, if it is not enclosed in quotes, i only get single terms, Example: will only return single terms:

Re: SOLR Suggester returns either the full field value or single terms only

hi Alessandro, Thanks very much. I've read your article - which is really great by the way! , and configured my suggester in the following way: mySuggester FreeTextLookupFactory DocumentDictionaryFactory content_suggest true 3

SOLR Suggester returns either the full field value or single terms only

Hi guys, I am trying to configure the Suggester in a way that i get google-style auto suggestions: - I don't want the suggestions to be the _whole_ field value - I don't want the suggestions to be single terms For example, if I have a field that has the value "The brown fox jumped over the

ramBufferSizeMB and maxIndexingThreads

hi guys, quick question - is the ramBufferSizeMB the maximum value no matter how maxIndexingThreads I have, or is it multiplied by the number if indexing threads? So, if I have ramBufferSizeMB set to 100 MB, and 8 indexing threads, does this mean the total ram buffer will be 100 MB or 800 MB ?

Re: Indexing gets significantly slower after every batch commit

to put something to it is log(n) четверг, 21 мая 2015 г. пользователь Angel Todorov написал: hi Shawn, Thanks a bunch for your feedback. I've played with the heap size, but I don't see any improvement. Even if i index, say , a million docs, and the throughput is about 300 docs per

Indexing gets significantly slower after every batch commit

hi guys, I'm crawling a file system folder and indexing 10 million docs, and I am adding them in batches of 5000, committing every 50 000 docs. The problem I am facing is that after each commit, the documents per sec that are indexed gets less and less. If I do not commit at all, I can index

Re: Indexing gets significantly slower after every batch commit

Heisey apa...@elyograg.org wrote: On 5/21/2015 2:07 AM, Angel Todorov wrote: I'm crawling a file system folder and indexing 10 million docs, and I am adding them in batches of 5000, committing every 50 000 docs. The problem I am facing is that after each commit, the documents per sec

After language detection is enabled, SOLR (5.1) isn't indexing anything

Hi guys, I've enabled language detection in solrconfig.xml: updateRequestProcessorChain name=langid processor class= org.apache.solr.update.processor.TikaLanguageIdentifierUpdateProcessorFactory lst name=defaults str name=langid.flcontent,title/str str