lucenenet-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Itamar Syn-Hershko <ita...@code972.com>
Subject Re: Colon in search query
Date Sat, 18 Feb 2017 20:35:44 GMT
It is, but it's also highly dependent on your code and document structure.
If you can post some code maybe we can assist.

--

Itamar Syn-Hershko
Freelance Developer & Consultant
Elasticsearch Consulting Partner
Microsoft MVP | Lucene.NET PMC
http://code972.com | @synhershko <https://twitter.com/synhershko>
http://BigDataBoutique.co.il/

On Wed, Jan 11, 2017 at 8:03 PM, Bowles, Mickey <
Mickey.Bowles@aftonchemical.com> wrote:

> I have the following end of a url to webapi, where LuceneSearch is the
> controller action, that returns the correct result set restricted to Type
> =  Container
>
> /api/LuceneSearch?q=t*st&Type=Container
>
> In the Lucene docs, I should be able to use Type:Container, but this
> returns a result set not limited to Container.  Odd part is, this was
> working and I have not changed the code nor updated Lucene (that I am aware
> of)
>
>
> Is Type:Container proper syntax?
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message