[
https://issues.apache.org/jira/browse/ATLAS-4825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rahul Kurup updated ATLAS-4825:
-------------------------------
Description:
If we fire these queries(assuming data exists for valid results):
{code:java}
hive_table where qualifiedName like 'dataset_3' and bm1.attr1 like '*' select
bm1.attr1
hive_table where qualifiedName like 'dataset_' and bm1.attr1 like '*' select
bm1.attr1
hive_table where qualifiedName like 'dataset' and bm1.attr1 like '*' select
bm1.attr1{code}
And if we compare the results of each query above, each query fetches more
results than the previous query, which is expected behaviour.
However if we consider these queries:
{code:java}
hive_table where qualifiedName like 'dataset_3' select bm1.attr1
hive_table where qualifiedName like 'dataset_' select bm1.attr1
hive_table where qualifiedName like 'dataset' select bm1.attr1{code}
The results are unexpected. The last two queries should have fetched results,
but only shows blank. Screenshots for the same have been attached below..
The difference noted between the first three and the last three queries was
that the Business metadata attribute is not used in the last 3 queries in the
where clause.
was:
If we fire these queries(assuming data exists for valid results):
hive_table where qualifiedName like 'dataset_3' and bm1.attr1 like '*' select
bm1.attr1
hive_table where qualifiedName like 'dataset_' and bm1.attr1 like '*' select
bm1.attr1
hive_table where qualifiedName like 'dataset' and bm1.attr1 like '*' select
bm1.attr1
And if we compare the results of each query above, each query fetches more
results than the previous query, which is expected behaviour.
However if we consider these queries:
hive_table where qualifiedName like 'dataset_3' select bm1.attr1
hive_table where qualifiedName like 'dataset_' select bm1.attr1
hive_table where qualifiedName like 'dataset' select bm1.attr1
The results are unexpected. The last two queries should have fetched results,
but only shows blank. Screenshots for the same have been attached below..
The difference noted between the first three and the last three queries was
that the Business metadata attribute is not used in the last 3 queries in the
where clause.
> Some DSL/advanced queries using business metadata attribute don't work as
> expected
> ----------------------------------------------------------------------------------
>
> Key: ATLAS-4825
> URL: https://issues.apache.org/jira/browse/ATLAS-4825
> Project: Atlas
> Issue Type: Bug
> Reporter: Rahul Kurup
> Priority: Major
> Attachments: dataset_3_dsl_screenshot.png,
> dataset_no_underscore_screenshot.png, dataset_underscore_dsl_screenshot.png
>
>
> If we fire these queries(assuming data exists for valid results):
> {code:java}
> hive_table where qualifiedName like 'dataset_3' and bm1.attr1 like '*' select
> bm1.attr1
> hive_table where qualifiedName like 'dataset_' and bm1.attr1 like '*' select
> bm1.attr1
> hive_table where qualifiedName like 'dataset' and bm1.attr1 like '*' select
> bm1.attr1{code}
> And if we compare the results of each query above, each query fetches more
> results than the previous query, which is expected behaviour.
> However if we consider these queries:
> {code:java}
> hive_table where qualifiedName like 'dataset_3' select bm1.attr1
> hive_table where qualifiedName like 'dataset_' select bm1.attr1
> hive_table where qualifiedName like 'dataset' select bm1.attr1{code}
> The results are unexpected. The last two queries should have fetched results,
> but only shows blank. Screenshots for the same have been attached below..
> The difference noted between the first three and the last three queries was
> that the Business metadata attribute is not used in the last 3 queries in the
> where clause.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
