[
https://issues.apache.org/jira/browse/ATLAS-3370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16912945#comment-16912945
]
Bolke de Bruin edited comment on ATLAS-3370 at 8/22/19 4:29 AM:
----------------------------------------------------------------
Why is the indexing changed from fulltext to string based? this changes search
behavior. per documentation of janus:
When a string mapping is configured, the string value is indexed and can be
queried "as-is" - including stop words and non-letter characters. However, in
this case the query must match the entire string value. Hence, the string
mapping is useful when indexing short character sequences that are considered
to be one token.
For the (dsl) search it might be that due to this change the performance
suffers as the different indices make use of different predicates. This can be
a 100x perf hit, as we haveseen in our system on the linked issue.
was (Author: bolke):
why is the indexing changed from fulltext to string based? this changes search
behavior. per documentation of janus:
When a string mapping is configured, the string value is indexed and can be
queried "as-is" - including stop words and non-letter characters. However, in
this case the query must match the entire string value. Hence, the string
mapping is useful when indexing short character sequences that are considered
to be one token.
> Aggregation Metrics with quick search, Counts don't add up
> ----------------------------------------------------------
>
> Key: ATLAS-3370
> URL: https://issues.apache.org/jira/browse/ATLAS-3370
> Project: Atlas
> Issue Type: Bug
> Reporter: Sridhar
> Assignee: Sridhar
> Priority: Major
>
> The issue was happening because of tokenization done for the fields in issue.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
