Hi,
It's hard to determine the issue with seeing the data getting indexed and
the search that is ran. if you create a recreation following the below
guidelines, you're much more likely to get accurate answers.
Best Regards,
Paul
On Friday, July 26, 2013 11:39:36 AM UTC-6, Rebeca De San Martin wrote:
*Hello!
It does not work "Stop Word"
I have this mapping:*
fos_elastica:
clients:
default: {host: localhost, port: 9200}
indexes:
website:
settings:
index:
analysis:
analyzer:
my_analyzer:
language: english
tokenizer: nonutf8letter
filter: [standard, lowercase,
asciifolding, stop, custom_stop]
tokenizer:
nonutf8letter:
type: pattern
pattern: '[^ \ pL \ pM \ p {Nd} \ p {Nl}
\ p {Pc} [\ p {InEnclosedAlphanumerics} && \ p {So}]]'
filter:
custom_stop:
type: length
min: 3
max: 2000
types:
deals:
mappings:
id: boost {3}
nombreoa {analyzer: my_analyzer}
idareaestudio:
type: "nested"
properties:
name: {type: String, index: not_analyzed}
*
When I search "to" bring me everything and I want it excluded.
If I search "to" should exclude all results and get me 0 results and what
they are doing is bringing me all results where it finds "a". It does not
work.
El viernes, 26 de julio de 2013 14:39:36 UTC-3, Rebeca De San Martin
escribió:
*Hello!
It does not work "Stop Word"
I have this mapping:*
fos_elastica:
clients:
default: {host: localhost, port: 9200}
indexes:
website:
settings:
index:
analysis:
analyzer:
my_analyzer:
language: english
tokenizer: nonutf8letter
filter: [standard, lowercase,
asciifolding, stop, custom_stop]
tokenizer:
nonutf8letter:
type: pattern
pattern: '[^ \ pL \ pM \ p {Nd} \ p {Nl}
\ p {Pc} [\ p {InEnclosedAlphanumerics} && \ p {So}]]'
filter:
custom_stop:
type: length
min: 3
max: 2000
types:
deals:
mappings:
id: boost {3}
nombreoa {analyzer: my_analyzer}
idareaestudio:
type: "nested"
properties:
name: {type: String, index: not_analyzed}
*
When I search "to" bring me everything and I want it excluded.
Sorry, still need more context to be of any help. Can you please create a
curl based recreation as described here:
Minimally, I need to see how the index is created, how the data is indexed,
and how the data is searched.
Best Regards,
Paul
On Monday, July 29, 2013 6:18:19 AM UTC-6, Rebeca De San Martin wrote:
If I search "to" should exclude all results and get me 0 results and
what they are doing is bringing me all results where it finds "a". It
does not work.
El viernes, 26 de julio de 2013 14:39:36 UTC-3, Rebeca De San Martin
escribió:
*Hello!
It does not work "Stop Word"
I have this mapping:*
fos_elastica:
clients:
default: {host: localhost, port: 9200}
indexes:
website:
settings:
index:
analysis:
analyzer:
my_analyzer:
language: english
tokenizer: nonutf8letter
filter: [standard, lowercase,
asciifolding, stop, custom_stop]
tokenizer:
nonutf8letter:
type: pattern
pattern: '[^ \ pL \ pM \ p {Nd} \ p {Nl}
\ p {Pc} [\ p {InEnclosedAlphanumerics} && \ p {So}]]'
filter:
custom_stop:
type: length
min: 3
max: 2000
types:
deals:
mappings:
id: boost {3}
nombreoa {analyzer: my_analyzer}
idareaestudio:
type: "nested"
properties:
name: {type: String, index: not_analyzed
}
*
When I search "to" bring me everything and I want it excluded.
Here's a tip that might help... I like to use facets in order to determine
what terms are actually being stored in the underlying engine.
So run a query for your specific document and add a facet on the field you
are having issues with. That will show you if stopwords are actually making
it into the index or something else is going on.
Best Regards,
Paul
On Monday, July 29, 2013 11:57:13 AM UTC-6, ppearcy wrote:
Minimally, I need to see how the index is created, how the data is
indexed, and how the data is searched.
Best Regards,
Paul
On Monday, July 29, 2013 6:18:19 AM UTC-6, Rebeca De San Martin wrote:
If I search "to" should exclude all results and get me 0 results and
what they are doing is bringing me all results where it finds "a". It
does not work.
El viernes, 26 de julio de 2013 14:39:36 UTC-3, Rebeca De San Martin
escribió:
*Hello!
It does not work "Stop Word"
I have this mapping:*
fos_elastica:
clients:
default: {host: localhost, port: 9200}
indexes:
website:
settings:
index:
analysis:
analyzer:
my_analyzer:
language: english
tokenizer: nonutf8letter
filter: [standard, lowercase,
asciifolding, stop, custom_stop]
tokenizer:
nonutf8letter:
type: pattern
pattern: '[^ \ pL \ pM \ p {Nd} \ p {Nl
} \ p {Pc} [\ p {InEnclosedAlphanumerics} && \ p {So}]]'
filter:
custom_stop:
type: length
min: 3
max: 2000
types:
deals:
mappings:
id: boost {3}
nombreoa {analyzer: my_analyzer}
idareaestudio:
type: "nested"
properties:
name: {type: String, index:
not_analyzed}
*
When I search "to" bring me everything and I want it excluded.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.