These are the (known) special characters that would trigger such warnings.
private static boolean isIndexQuerySpecialChar(char c) {
switch (c) {
case '+':
case '-':
case '&':
case '|':
case '!':
case '(':
case ')':
case '{':
case '}':
case '[':
case ']':
case '^':
case '"':
case '~':
case '*':
case '?':
case ':':
case '/':
case '#':
case '$':
case '%':
case '@':
case '=':
return true;
}
return false;
}
On 5/4/18, 1:52 PM, "Apoorv Naik" <an...@hortonworks.com> wrote:
What is the qualified name that you're searching on ? If it has special
characters then the index query won't be executed because the indexing backend
tokenizes the search string on every occurrence of a special character.
Hence the warning.
On 5/4/18, 1:29 PM, "Pierre Padovani" <pierre.padov...@civitaslearning.com>
wrote:
I don't have it of hand, but this is the code snippet with the Atlas
client
we used:
SearchParameters.FilterCriteria qualifiedNameCriteria = new
SearchParameters.FilterCriteria();
qualifiedNameCriteria.setAttributeName(QUALIFIED_NAME);
qualifiedNameCriteria.setOperator(SearchParameters.Operator.EQ);
qualifiedNameCriteria.setAttributeValue(qualifiedName);
SearchParameters searchParams = new SearchParameters();
searchParams.setTypeName(typeName);
searchParams.setExcludeDeletedEntities(true);
searchParams.setEntityFilters(qualifiedNameCriteria);
searchParams.setLimit(ATLAS_SEARCH_LIMIT);
AtlasSearchResult searchResult =
atlas.facetedSearch(searchParams);
On Fri, May 4, 2018 at 2:37 PM, Apoorv Naik <an...@hortonworks.com>
wrote:
> What is the search criteria that you're working with ? If it's
basically
> search , can you share the request JSON ?
>
> Sent from Nine<http://www.9folders.com/>
> ________________________________
> From: Pierre Padovani <pierre.padov...@civitaslearning.com>
> Sent: Friday, May 4, 2018 12:34 PM
> To: dev@atlas.apache.org
> Subject: Odd warning during search
>
> We are seeing this warning message:
>
> not using index-search for attribute 'Referenceable.qualifiedName';
might
> cause poor performance
>
> I have not been able to find a configuration related to
indexing/search or
> documentation that could help us resolve this.
>
> Can someone help clarify what would cause this?
>
> Thanks!
>
> Pierre Padovani
>
