[
https://issues.apache.org/jira/browse/ATLAS-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16164477#comment-16164477
]
Péter Gergő Barna commented on ATLAS-2121:
------------------------------------------
What is exactly the expected behavior here? The docs on the basic search does
not mention whether it is case sensitive or not:
http://atlas.apache.org/Search.html Do we really want the basic search to be
case sensitive?
If yes, then do we want this to be fixed in the index backend? I mean do we
want to configure Solr to be case sensitive?
I reproed this and investigated it with Solr as index backend.
Basic search uses the fulltext_index and its case sensitivity is configured in
the schema.xml:
https://github.com/apache/incubator-atlas/blob/0.8-incubating/distro/src/conf/solr/schema.xml
This is the field used:
{noformat}
<dynamicField name="*_t" type="text_general" indexed="true" stored="true"/>
{noformat}
And this is the fieldType:
{noformat}
<fieldType name="text_general" class="solr.TextField"
positionIncrementGap="100">
<analyzer type="index">
<tokenizer class="solr.StandardTokenizerFactory"/>
<filter class="solr.StopFilterFactory" ignoreCase="true"
words="stopwords.txt" />
<!-- in this example, we will only use synonyms at query time
<filter class="solr.SynonymFilterFactory" synonyms="index_synonyms.txt"
ignoreCase="true" expand="false"/>
-->
<filter class="solr.LowerCaseFilterFactory"/>
</analyzer>
<analyzer type="query">
<tokenizer class="solr.StandardTokenizerFactory"/>
<filter class="solr.StopFilterFactory" ignoreCase="true"
words="stopwords.txt" />
<filter class="solr.SynonymFilterFactory" synonyms="synonyms.txt"
ignoreCase="true" expand="true"/>
<filter class="solr.LowerCaseFilterFactory"/>
</analyzer>
</fieldType>
{noformat}
> Inconsistency in basic search results due to case sensitivity of type names
> ---------------------------------------------------------------------------
>
> Key: ATLAS-2121
> URL: https://issues.apache.org/jira/browse/ATLAS-2121
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
> Affects Versions: 0.8-incubating, 0.9-incubating
> Reporter: Sharmadha Sainath
> Assignee: Péter Gergő Barna
> Priority: Critical
>
> Type names are case sensitive hence 2 types can be created with different
> cases.
> Example :
> 1. type1 with attributes a , b
> 2. TYPE1 with attributes c , d
> The types creation succeeds and
> {code}
> /api/atlas/v2/types/entitydef/name/type1
> /api/atlas/v2/types/entitydef/name/TYPE1
> {code}
> return the corresponding type definitions correctly.
> When an entity e1 of type1 is created,
> and when a BASIC search is fired with
> typeName= type1 , e1 is returned and
> typeName=TYPE1 also , e1 is returned.
> But in the case of DSL search ,
> typeName = type1 returns e1
> typeName = TYPE1 doesn't return any result - which is the correct behavior.
> This issue is major from tag side too because , UI Tag search is Basic and
> returns entity tagged with tag1 when searched for tag1 or TAG1.
> Whereas DSL search with
> classification=tag1 returns entity
> classification=TAG1 does not return any entity. - which is the correct
> behavior.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
