Re: Solr NLS custom query parser

Hi Arun, your question is too generic. What do you mean with nlp search? What do you expect to happen? The short answer is: No, there is no such parser because the individual requirements will vary a lot. -Michael Am 14.06.2017 um 16:32 schrieb aruninfo100: > Hi, > > I am trying to configure

Re: Solr NLS custom query parser

Hi Michael, I have indexed the documents in such a way,I used OpenNLP to extract named entities and POS and has indexed these data to respective fields. I have read(my understanding) that for natural language search using Solr,once you have the entities extracted the next step is to create a

Re: Multiple hashJoin or innerJoin

It looks like you are running into this bug: https://issues.apache.org/jira/browse/SOLR-10512. This not been resolved yet, but I believe there is a work around which is described in the ticket. Joel Bernstein http://joelsolr.blogspot.com/ On Wed, Jun 14, 2017 at 10:09 PM, Zheng Lin Edwin Yeo

cursor with sort value along with unique key

Hello, With respects to cursors, when using a computed sort value (like score) in combination with the unique field sort (score desc, id asc) seems to cause some wildly inconsistent and incomplete results. Can I get any help out of it? Thanks & Regards Preeti chhabra

Phrase Exact Match with Margin of Error

Hi, I am trying to do phrase exact match. For this, I use KeywordTokenizerFactory. This basically does what I want to do. My field type is defined as follows: In addition to this, I want to tolerate typos of two or three

Re: Phrase Exact Match with Margin of Error

CompledPhraseQuery parser is what you need to look https://cwiki.apache.org/confluence/display/solr/Other+Parsers#OtherParsers-ComplexPhraseQueryParser. See below for e.g.

Re: cursor with sort value along with unique key

Hello, http://lucene.472066.n3.nabble.com/Pagination-bug-when-sorting-by-a-field-not-unique-field-tp4327408p4327524.html might be relevant. On Thu, Jun 15, 2017 at 12:40 PM, Preeti Chhabra < preeti.chha...@karexpert.com> wrote: > Hello, > > With respects to cursors, when using a computed sort

Re: CSV output

Is it the proxy affecting the output?What do you get going directly to Solr's endpoint? Erik > On Jun 14, 2017, at 22:13, Phil Scadden wrote: > > If I try > /getsolr? > fl=id,title,datasource,score=true=9000=unified=Wainui-1=AND=csv > > The response I get

Re: Multiple hashJoin or innerJoin

Hi Joel, Yes, I got this error: {"result-set":{"docs":[{"EXCEPTION":"Invalid JoinStream - all incoming stream comparators (sort) must be a superset of this stream's equalitor.","EOF":true}]}} Ok, will try out the work around first. Regards, Edwin On 15 June 2017 at 20:16, Joel Bernstein

Re: Phrase Exact Match with Margin of Error

Agree, that's the challenge. Since ComplexPhraseQuery parser needs terms analyzed/tokenized and if don't, it can't really operate at individual tokens with fuzzy or wildcard matches. The solution I can think of is to execute query against both the fields (KeywordTokenized..) and

Re: Phrase Exact Match with Margin of Error

Thanks Susheel. The challenge is that if I search for the word "between" alone, I still get plenty of results. In a way I want the query to match the document title exactly (up to a few characters) and the document title match the query exactly (up to a few characters). KeywordTokenizer allows

Re: Phrase Exact Match with Margin of Error

I think that's because the KeywordTokenizer by definition produces a single token (not a phrase). Perhaps you could create two fields by a copyField - the one you already have(field1), and one tokenized using StandardTokenizer or WhiteSpaceTokenizer(field2) which will produce a phrase with

Re: Issue with highlighter

Thanks for the replies. Let me try and explain this a little better. I haven't modified anything in solrconfig. All I did was get a fresh instance of solr 6.4.1 and create a core testHighlight. I then created a content field of type text_en via the Solr Admin UI. id was already there, and that

Query not working with DatePointField

Hi, We have a fieldType specified for date. Earlier it was using TrieDateField and we changed it to DatePointField. Here are the fields used in the query and one of them uses the dateType: The following query was returning correct results when the field type was Trie but not with Point:

Re: Solr 6: how to get SortedSetDocValues from index by field name

https://people.apache.org/~hossman/#xyproblem XY Problem Your question appears to be an "XY Problem" ... that is: you are dealing with "X", you are assuming "Y" will help you, and you are asking about "Y" without giving more details about the "X" so that we can understand the full issue.

RE: CSV output

Embarassing. Yes, it was the proxy. Very old code that has now had a considerable refresh. -Original Message- From: Erik Hatcher [mailto:erik.hatc...@gmail.com] Sent: Thursday, 15 June 2017 7:13 p.m. To: solr-user@lucene.apache.org Subject: Re: CSV output Is it the proxy affecting the

Re: Query not working with DatePointField

The query field:* doesn't work with point fields (numerics or dates), only exact or range queries are supported, so an equivalent query would be field:[* TO *] Sent from my iPhone > On Jun 15, 2017, at 5:24 PM, Saurabh Sethi wrote: > > Hi, > > We have a

Does Solr support multiple collapse filters - throws NullPointerException

I am trying to use solr collapse function: But seems when we use 2 or more collapse filters, it will throw NullPointerException? Does anyone have idea whether solr supports multiple collapse filters? - it doesn't mention about using 2 or more collapse filters at all at

Re: Issue with highlighter

Ali, does adding a 'hl.q' param help? q=something=something&... On 16 June 2017 at 06:21, Ali Husain wrote: > Thanks for the replies. Let me try and explain this a little better. > > > I haven't modified anything in solrconfig. All I did was get a fresh > instance of