Re: [Atlas][Search] Not able to leverage the index backend to search hive table by qualified name

[Jiaxin Ye <ji...@airbnb.com>]

Hi Pinal,

Thanks for the info! I was still using Atlas 1.3 because the version of our
HBase was not 2.0 yet. Let me see how I can apply the patch to our Atlas
repo.

Thanks,
Jiaxin

On Wed, Mar 31, 2021 at 6:53 AM Pinal Shah <pi...@freestoneinfotech.com>
wrote:

> Hi Jiaxin,
>
> Yes, adding a special character like '@' in the search value string will
> avoid using index query.
> ATLAS-4112 <https://issues.apache.org/jira/browse/ATLAS-4112> will help
> to trigger index queries in such cases.
>
> Thanks,
> Pinal Shah
> <https://issues.apache.org/jira/browse/ATLAS-4112>
>
>
> On Wed, Mar 31, 2021 at 5:07 AM Jiaxin Ye <ji...@airbnb.com> wrote:
>
>> Hi All,
>>
>> I am using Hbase as the storage backend and elasticSearch as the index
>> backend for Atlas.
>>
>> When using the Atlas UI, I found that I was not able to search for a hive
>> table using the qualified name filter by the elasticsearch index because
>> the qualifiedName of the hive table contains the special character `@`.
>> (Hive table qualifiedName = [db_name].[table_name]@[cluster_name]). Because
>> of that special character, the UI search triggers a full scan on the hive
>> table entities in hbase which it's super inefficient.
>>
>> Did anyone meet this issue before? Or this is nothing that I am missing?
>>
>> Thanks,
>> Jiaxin
>>
>