[jira] [Updated] (ATLAS-4332) DSL Query : query with like operator and "/" in search text throws 500

[Pinal (Jira)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-4332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pinal updated ATLAS-4332:
-
Fix Version/s: 2.1.0

> DSL Query : query with like operator and "/" in search text throws 500
> --
>
> Key: ATLAS-4332
> URL: https://issues.apache.org/jira/browse/ATLAS-4332
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Pinal Shah
>Assignee: Pinal
>Priority: Major
>  Labels: AdvancedSearch
> Fix For: 2.1.0
>
>
> hdfs_path name="/warehouse/tablespace/external/hive/db_fdchj.db" returns 
> right entity.
> hdfs_path name like "/warehouse/*" throws following exception: 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (ATLAS-4332) DSL Query : query with like operator and "/" in search text throws 500

[ASF subversion and git services (Jira)]

[ 
https://issues.apache.org/jira/browse/ATLAS-4332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17361391#comment-17361391
 ] 

ASF subversion and git services commented on ATLAS-4332:


Commit 37d3c6d99c7db347280a8d9098fa5327f7dd4dd1 in atlas's branch 
refs/heads/branch-2.0 from Pinal
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=37d3c6d ]

ATLAS-4332 : DSL Query : query with like operator and / in search text throws 
500

Signed-off-by: Pinal 


> DSL Query : query with like operator and "/" in search text throws 500
> --
>
> Key: ATLAS-4332
> URL: https://issues.apache.org/jira/browse/ATLAS-4332
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Pinal Shah
>Assignee: Pinal
>Priority: Major
>  Labels: AdvancedSearch
>
> hdfs_path name="/warehouse/tablespace/external/hive/db_fdchj.db" returns 
> right entity.
> hdfs_path name like "/warehouse/*" throws following exception: 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (ATLAS-4332) DSL Query : query with like operator and "/" in search text throws 500

[ASF subversion and git services (Jira)]

[ 
https://issues.apache.org/jira/browse/ATLAS-4332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17361389#comment-17361389
 ] 

ASF subversion and git services commented on ATLAS-4332:


Commit 2afbf4daa650f49674ca1c7481697b852cb6a446 in atlas's branch 
refs/heads/master from Pinal
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=2afbf4d ]

ATLAS-4332 : DSL Query : query with like operator and / in search text throws 
500

Signed-off-by: Pinal 


> DSL Query : query with like operator and "/" in search text throws 500
> --
>
> Key: ATLAS-4332
> URL: https://issues.apache.org/jira/browse/ATLAS-4332
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Pinal Shah
>Assignee: Pinal
>Priority: Major
>  Labels: AdvancedSearch
>
> hdfs_path name="/warehouse/tablespace/external/hive/db_fdchj.db" returns 
> right entity.
> hdfs_path name like "/warehouse/*" throws following exception: 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (ATLAS-4325) [Atlas: Glossary Term Bulk Import] [UI] Unable to perform bulk import glossary term via UI

[Prasad P. Pawar (Jira)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-4325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prasad P. Pawar updated ATLAS-4325:
---
Fix Version/s: 2.2.0
   3.0.0

> [Atlas: Glossary Term Bulk Import] [UI] Unable to perform bulk import 
> glossary term via UI
> --
>
> Key: ATLAS-4325
> URL: https://issues.apache.org/jira/browse/ATLAS-4325
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Prasad P. Pawar
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: 
> 0001-ATLAS-4325-Atlas-Glossary-Term-Bulk-Import-UI-Unable.patch, Screenshot 
> 2021-06-03 at 5.41.57 PM.png
>
>
> Bulk import is failing with "\{"msgDesc":"Missing header or invalid Header 
> value for CSRF Vulnerability Protection"}" !Screenshot 2021-06-03 at 5.41.57 
> PM.png|width=443,height=273!
> NOTE: the same succeeds via api



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (ATLAS-4335) Hook Notifications through Rest Interface

[Deep Singh (Jira)]

Deep Singh created ATLAS-4335:
-

 Summary: Hook Notifications through Rest Interface
 Key: ATLAS-4335
 URL: https://issues.apache.org/jira/browse/ATLAS-4335
 Project: Atlas
  Issue Type: New Feature
  Components:  atlas-core
Reporter: Deep Singh
Assignee: Deep Singh


In Data-lake <-> Workload-cluster scenario, versions of the services available 
on clusters are not always the same. Especially when Kafka versions are 
different on the clusters, many a time the Kafka client (on workload-cluster) 
becomes incompatible with the Kafka broker (on data-lake). This leads to 
failure in the delivery of Atlas Hook notification as the mechanism is 
dependent on the Kafka client's capability to deliver messages.

To resolve such an issue there is no other way but to make Kafka client 
compatible with the broker by upgrading or degrading the client or the broker. 
Often this is not straight-fwd and the easiest thing to do.

We need another mechanism independent of the Kafka client to deliver hook 
notifications to the Atlas consumer.

There are various REST API available today to perform CURD on Atlas entities. 
Those APIs process notifications in real-time as they arrive, since event 
processing is slow and time-consuming these APIs cannot give the throughput 
which hooks require.

We need another REST interface that is lightweight and does not process 
messages as they arrive instead, it could dump the messages to the local kafka. 
Since Kafka will be available locally in the cluster, the interface will never 
face the problem of version mismatch of client-broker, as faced by service 
hooks running on a different cluster. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: Review Request 73404: ATLAS-4324: FS entity created for load data inpath is created as shell entity - Part 2

[Sarath Subramanian]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/73404/#review223135
---


Ship it!




Ship It!

- Sarath Subramanian


On June 8, 2021, 4:07 p.m., Ashutosh Mestry wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/73404/
> ---
> 
> (Updated June 8, 2021, 4:07 p.m.)
> 
> 
> Review request for atlas, Mandar Ambawane, Radhika Kundam, and Sarath 
> Subramanian.
> 
> 
> Bugs: ATLAS-4324
> https://issues.apache.org/jira/browse/ATLAS-4324
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> **Approach**
> Updates:
> - Simplified approach.
> - Maintained abstraction.
> - Updated unit tests.
> 
> 
> Diffs
> -
> 
>   addons/hive-bridge/src/main/java/org/apache/atlas/hive/hook/HiveHook.java 
> 94ef22577 
>   
> addons/hive-bridge/src/main/java/org/apache/atlas/hive/hook/utils/ActiveEntityFilter.java
>  737c637bf 
>   
> addons/hive-bridge/src/main/java/org/apache/atlas/hive/hook/utils/HiveDDLEntityFilter.java
>  9163c4709 
>   
> addons/hive-bridge/src/test/java/org/apache/atlas/hive/hook/utils/ActiveEntityFilterTest.java
>  4dde1dc2f 
>   addons/hive-bridge/src/test/resources/json/hs2-create-db-v2.json 881ee105e 
>   
> addons/hive-bridge/src/test/resources/json/hs2-create-db-with-no-pathentities-to-retain-v2.json
>  42553b5cf 
>   
> addons/hive-bridge/src/test/resources/json/hs2-create-db-with-no-pathentities-to-retain.json
>  a5b810f72 
>   addons/hive-bridge/src/test/resources/json/hs2-create-process-v2.json 
> 8e55b7282 
>   addons/hive-bridge/src/test/resources/json/hs2-create-table-v2.json 
> 801918e04 
>   addons/hive-bridge/src/test/resources/json/hs2-load-inpath-v2.json 
> dd31aa073 
>   
> addons/hive-bridge/src/test/resources/json/hs2-load-inpath-with-no-pathentities-to-retain-v2.json
>  7f90d1986 
>   
> addons/hive-bridge/src/test/resources/json/hs2-load-inpath-with-no-pathentities-to-retain.json
>  dd31aa073 
>   addons/hive-bridge/src/test/resources/json/hs2-load-inpath.json dd31aa073 
>   addons/hive-bridge/src/test/resources/json/hs2-table-rename-v2.json 
> f2b2bf7a8 
> 
> 
> Diff: https://reviews.apache.org/r/73404/diff/2/
> 
> 
> Testing
> ---
> 
> **Unit tests**
> - Additional unit test.
> 
> **PC Build**
> https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/617/
> 
> 
> File Attachments
> 
> 
> Screen Shot 2021-06-08 at 4.05.26 PM.png
>   
> https://reviews.apache.org/media/uploaded/files/2021/06/08/b15b33fc-007d-4ee3-8862-64750af16432__Screen_Shot_2021-06-08_at_4.05.26_PM.png
> 
> 
> Thanks,
> 
> Ashutosh Mestry
> 
>

[jira] [Commented] (ATLAS-4333) [MATERIALIZED VIEW]Column Lineage and hive_process missing in case of CREATE MATERIALIZED VIEW query at Hive

[ASF subversion and git services (Jira)]

[ 
https://issues.apache.org/jira/browse/ATLAS-4333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17361225#comment-17361225
 ] 

ASF subversion and git services commented on ATLAS-4333:


Commit 62c702422f7523b662743a5e2de15ecef6a27c3c in atlas's branch 
refs/heads/branch-2.0 from Radhika Kundam
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=62c7024 ]

ATLAS-4333: [MATERIALIZED VIEW]Column Lineage and hive_process missing in case 
of CREATE MATERIALIZED VIEW query at Hive


> [MATERIALIZED VIEW]Column Lineage and hive_process missing in case of CREATE 
> MATERIALIZED VIEW query at Hive
> 
>
> Key: ATLAS-4333
> URL: https://issues.apache.org/jira/browse/ATLAS-4333
> Project: Atlas
>  Issue Type: Bug
>Reporter: Radhika Kundam
>Assignee: Radhika Kundam
>Priority: Major
>
> Column Lineage and the hive_process are missing in case of materialised view
> {code:java}
> CREATE TABLE tbl1(id int, name string);  
> CREATE MATERIALIZED VIEW tbl1_materialized_view as SELECT * from tbl1;
> {code}
> With above create materialized query, tbl1_view is created but with missing 
> "ddlQueries(hive_table_ddl)" relationship and 
> "outputFromProcesses(hive_column_lineage)" for columns.
> HiveContext is not sending lineage info for columns of materialized view, 
> once Hive fixes the issue it'll resolve missing lineage issue. Jira# 
> HIVE-25236 created for Hive.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (ATLAS-4333) [MATERIALIZED VIEW]Column Lineage and hive_process missing in case of CREATE MATERIALIZED VIEW query at Hive

[ASF subversion and git services (Jira)]

[ 
https://issues.apache.org/jira/browse/ATLAS-4333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17361220#comment-17361220
 ] 

ASF subversion and git services commented on ATLAS-4333:


Commit 01f5eea5c60b710e16370b7e09a60a5353f8d17d in atlas's branch 
refs/heads/master from Radhika Kundam
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=01f5eea ]

ATLAS-4333: [MATERIALIZED VIEW]Column Lineage and hive_process missing in case 
of CREATE MATERIALIZED VIEW query at Hive


> [MATERIALIZED VIEW]Column Lineage and hive_process missing in case of CREATE 
> MATERIALIZED VIEW query at Hive
> 
>
> Key: ATLAS-4333
> URL: https://issues.apache.org/jira/browse/ATLAS-4333
> Project: Atlas
>  Issue Type: Bug
>Reporter: Radhika Kundam
>Assignee: Radhika Kundam
>Priority: Major
>
> Column Lineage and the hive_process are missing in case of materialised view
> {code:java}
> CREATE TABLE tbl1(id int, name string);  
> CREATE MATERIALIZED VIEW tbl1_materialized_view as SELECT * from tbl1;
> {code}
> With above create materialized query, tbl1_view is created but with missing 
> "ddlQueries(hive_table_ddl)" relationship and 
> "outputFromProcesses(hive_column_lineage)" for columns.
> HiveContext is not sending lineage info for columns of materialized view, 
> once Hive fixes the issue it'll resolve missing lineage issue. Jira# 
> HIVE-25236 created for Hive.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: Review Request 73404: ATLAS-4324: FS entity created for load data inpath is created as shell entity - Part 2

[Radhika Kundam]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/73404/#review223133
---


Ship it!




Ship It!

- Radhika Kundam


On June 8, 2021, 4:07 p.m., Ashutosh Mestry wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/73404/
> ---
> 
> (Updated June 8, 2021, 4:07 p.m.)
> 
> 
> Review request for atlas, Mandar Ambawane, Radhika Kundam, and Sarath 
> Subramanian.
> 
> 
> Bugs: ATLAS-4324
> https://issues.apache.org/jira/browse/ATLAS-4324
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> **Approach**
> Updates:
> - Simplified approach.
> - Maintained abstraction.
> - Updated unit tests.
> 
> 
> Diffs
> -
> 
>   addons/hive-bridge/src/main/java/org/apache/atlas/hive/hook/HiveHook.java 
> 94ef22577 
>   
> addons/hive-bridge/src/main/java/org/apache/atlas/hive/hook/utils/ActiveEntityFilter.java
>  737c637bf 
>   
> addons/hive-bridge/src/main/java/org/apache/atlas/hive/hook/utils/HiveDDLEntityFilter.java
>  9163c4709 
>   
> addons/hive-bridge/src/test/java/org/apache/atlas/hive/hook/utils/ActiveEntityFilterTest.java
>  4dde1dc2f 
>   addons/hive-bridge/src/test/resources/json/hs2-create-db-v2.json 881ee105e 
>   
> addons/hive-bridge/src/test/resources/json/hs2-create-db-with-no-pathentities-to-retain-v2.json
>  42553b5cf 
>   
> addons/hive-bridge/src/test/resources/json/hs2-create-db-with-no-pathentities-to-retain.json
>  a5b810f72 
>   addons/hive-bridge/src/test/resources/json/hs2-create-process-v2.json 
> 8e55b7282 
>   addons/hive-bridge/src/test/resources/json/hs2-create-table-v2.json 
> 801918e04 
>   addons/hive-bridge/src/test/resources/json/hs2-load-inpath-v2.json 
> dd31aa073 
>   
> addons/hive-bridge/src/test/resources/json/hs2-load-inpath-with-no-pathentities-to-retain-v2.json
>  7f90d1986 
>   
> addons/hive-bridge/src/test/resources/json/hs2-load-inpath-with-no-pathentities-to-retain.json
>  dd31aa073 
>   addons/hive-bridge/src/test/resources/json/hs2-load-inpath.json dd31aa073 
>   addons/hive-bridge/src/test/resources/json/hs2-table-rename-v2.json 
> f2b2bf7a8 
> 
> 
> Diff: https://reviews.apache.org/r/73404/diff/2/
> 
> 
> Testing
> ---
> 
> **Unit tests**
> - Additional unit test.
> 
> **PC Build**
> https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/617/
> 
> 
> File Attachments
> 
> 
> Screen Shot 2021-06-08 at 4.05.26 PM.png
>   
> https://reviews.apache.org/media/uploaded/files/2021/06/08/b15b33fc-007d-4ee3-8862-64750af16432__Screen_Shot_2021-06-08_at_4.05.26_PM.png
> 
> 
> Thanks,
> 
> Ashutosh Mestry
> 
>

[jira] [Created] (ATLAS-4334) Creating an external table/database, overrides the qualfiedName of an already existing aws_s3_v2_directory type

[Umesh Padashetty (Jira)]

Umesh Padashetty created ATLAS-4334:
---

 Summary: Creating an external table/database, overrides the 
qualfiedName of an already existing aws_s3_v2_directory type
 Key: ATLAS-4334
 URL: https://issues.apache.org/jira/browse/ATLAS-4334
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Reporter: Umesh Padashetty


The expectation is that every time an EXTERNAL Table is created in Hive, Atlas 
creates an entity of type hive_process connecting the aws_s3_v2_directory and 
the hive_table

A new unique entity of the type aws_s3_v2_directory and hive_table is created 
in atlas for every new external table created.

For instance, if I create an external table with the name test_ext_1, then 
there is an aws_s3_v2_directory and hive_table entity created with a similar 
name test_ext_1 

But observing a strange behaviour where whenever a new external table is 
created, even though a new hive_table entity is created, the previously created 
aws_s3_v2_directory entity itself is getting overridden with the new 
qualifiedName

For instance, I ran the below queries 
 * create external table test_ext_1(name string);
 * create external table test_ext_2(name string);
 * create external table test_ext_3(name string);
 * create database net1;

The expectation is that the above 4 queries will create
 * 3 hive_table entities
 * 1 hive_db entity
 * 3 aws_s3_v2_directory entities 

But it is actually creating
 * 3 hive_table entities
 * 1 hive_db entity
 * 1 aws_s3_v2_directory entity

The same aws_s3_v2_directory gets updated with a new qualifiedName every time I 
create a new external table or a database 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: Review Request 73412: ATLAS-4332 : DSL Query : query with like operator and "/" in search text throws 500

[Pinal Shah]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/73412/
---

(Updated June 10, 2021, 4:48 p.m.)


Review request for atlas, Ashutosh Mestry, Jayendra Parab, Nixon Rodrigues, and 
Sarath Subramanian.


Changes
---

addressed comments


Bugs: ATLAS-4332
https://issues.apache.org/jira/browse/ATLAS-4332


Repository: atlas


Description
---

**Problem:** In DSL query , searching with like operator in combination of 
special characters like '/' in search text throws 500

**Example:** 
hdfs_path name="/warehouse/tablespace/external/hive/db_fdchj.db" returns right 
entity.

hdfs_path name like "/warehouse/*" throws following exception:


Diffs (updated)
-

  repository/src/main/java/org/apache/atlas/query/GremlinQueryComposer.java 
320acbe22 
  repository/src/main/java/org/apache/atlas/query/IdentifierHelper.java 
c53a324a1 
  repository/src/test/java/org/apache/atlas/BasicTestSetup.java 99e075ac5 
  repository/src/test/java/org/apache/atlas/query/BaseDSLComposer.java 
b10400157 
  repository/src/test/java/org/apache/atlas/query/DSLQueriesTest.java 0c1dd59d2 
  repository/src/test/java/org/apache/atlas/query/GremlinQueryComposerTest.java 
3a2d66d8c 


Diff: https://reviews.apache.org/r/73412/diff/3/

Changes: https://reviews.apache.org/r/73412/diff/2-3/


Testing
---

unit testcase added

Precommit : 
https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/640/console
 (In Progress)


Thanks,

Pinal Shah

[jira] [Created] (ATLAS-4333) [MATERIALIZED VIEW]Column Lineage and hive_process missing in case of CREATE MATERIALIZED VIEW query at Hive

[Radhika Kundam (Jira)]

Radhika Kundam created ATLAS-4333:
-

 Summary: [MATERIALIZED VIEW]Column Lineage and hive_process 
missing in case of CREATE MATERIALIZED VIEW query at Hive
 Key: ATLAS-4333
 URL: https://issues.apache.org/jira/browse/ATLAS-4333
 Project: Atlas
  Issue Type: Bug
Reporter: Radhika Kundam
Assignee: Radhika Kundam


Column Lineage and the hive_process are missing in case of materialised view
{code:java}
CREATE TABLE tbl1(id int, name string);  
CREATE MATERIALIZED VIEW tbl1_materialized_view as SELECT * from tbl1;

{code}
With above create materialized query, tbl1_view is created but with missing 
"ddlQueries(hive_table_ddl)" relationship and 
"outputFromProcesses(hive_column_lineage)" for columns.

HiveContext is not sending lineage info for columns of materialized view, once 
Hive fixes the issue it'll resolve missing lineage issue. Jira# HIVE-25236 
created for Hive.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: Next release - 2.2 or 3.0?

[Adam Bellemare]

Hi Ashutosh

Thanks for the fast reply! It does provide some clarity.

I am looking at the branch-2.0, and there are enough differences between it
and trunk that the PR I am proposing doesn't patch nicely. I am fine with
making a patch for branch-2.0 if that's where the next release is coming
from. Alternately, if all releases always come from master branch, then I
can go spend some time on improving a few parts of the documentation
instead :).

Please advise accordingly!

On Thu, Jun 10, 2021 at 11:39 AM Ashutosh Mestry
 wrote:

> Hi Adam
>
> Thanks for following up.
>
> About releases: We discussed a rough plan in our team meeting last night.
> We are planning a release in the coming weeks. We will keep the mailing
> list posted with details.
>
> About your PR: We will be running the patch through our internal tests to
> ensure that our performance baseline in unaffected. I looked at the
> implementation briefly and it seems to be fine. Right now, I don’t have any
> comments. Once committed, we will try to get it in the upcoming outgoing
> release.
>
> Hope this helps!
>
> Best regards,
>
> ~ ashutosh
> Ashutosh Mestry . Staff Software Engineer .
> Cloudera, Inc.
>
>
> From: Adam Bellemare 
> Date: Thursday, June 10, 2021 at 8:13 AM
> To: dev@atlas.apache.org 
> Subject: Next release - 2.2 or 3.0?
> Hi
>
> I'm looking to have my PR (https://github.com/apache/atlas/pull/139)
> released in the next official release. Are there any plans for if that is
> 2.2 or 3.0?
>
> I take it that I should be committing to branch-2.0 for the next 2.2
> release, correct?
>
> Thanks
> Adam
>

Re: Review Request 73412: ATLAS-4332 : DSL Query : query with like operator and "/" in search text throws 500

[Ashutosh Mestry via Review Board]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/73412/#review223130
---


Ship it!




Ship It!

- Ashutosh Mestry


On June 10, 2021, 11:32 a.m., Pinal Shah wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/73412/
> ---
> 
> (Updated June 10, 2021, 11:32 a.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry, Jayendra Parab, Nixon Rodrigues, 
> and Sarath Subramanian.
> 
> 
> Bugs: ATLAS-4332
> https://issues.apache.org/jira/browse/ATLAS-4332
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> **Problem:** In DSL query , searching with like operator in combination of 
> special characters like '/' in search text throws 500
> 
> **Example:** 
> hdfs_path name="/warehouse/tablespace/external/hive/db_fdchj.db" returns 
> right entity.
> 
> hdfs_path name like "/warehouse/*" throws following exception:
> 
> 
> Diffs
> -
> 
>   repository/src/main/java/org/apache/atlas/query/GremlinQueryComposer.java 
> 320acbe22 
>   repository/src/main/java/org/apache/atlas/query/IdentifierHelper.java 
> c53a324a1 
>   repository/src/test/java/org/apache/atlas/BasicTestSetup.java 99e075ac5 
>   repository/src/test/java/org/apache/atlas/query/BaseDSLComposer.java 
> b10400157 
>   repository/src/test/java/org/apache/atlas/query/DSLQueriesTest.java 
> 0c1dd59d2 
>   
> repository/src/test/java/org/apache/atlas/query/GremlinQueryComposerTest.java 
> 3a2d66d8c 
> 
> 
> Diff: https://reviews.apache.org/r/73412/diff/2/
> 
> 
> Testing
> ---
> 
> unit testcase added
> 
> Precommit : 
> https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/640/console
>  (In Progress)
> 
> 
> Thanks,
> 
> Pinal Shah
> 
>

Re: Next release - 2.2 or 3.0?

[Ashutosh Mestry]

Hi Adam

Thanks for following up.

About releases: We discussed a rough plan in our team meeting last night. We 
are planning a release in the coming weeks. We will keep the mailing list 
posted with details.

About your PR: We will be running the patch through our internal tests to 
ensure that our performance baseline in unaffected. I looked at the 
implementation briefly and it seems to be fine. Right now, I don’t have any 
comments. Once committed, we will try to get it in the upcoming outgoing 
release.

Hope this helps!

Best regards,

~ ashutosh
Ashutosh Mestry . Staff Software Engineer . 
Cloudera, Inc.


From: Adam Bellemare 
Date: Thursday, June 10, 2021 at 8:13 AM
To: dev@atlas.apache.org 
Subject: Next release - 2.2 or 3.0?
Hi

I'm looking to have my PR (https://github.com/apache/atlas/pull/139)
released in the next official release. Are there any plans for if that is
2.2 or 3.0?

I take it that I should be committing to branch-2.0 for the next 2.2
release, correct?

Thanks
Adam

Re: Review Request 73412: ATLAS-4332 : DSL Query : query with like operator and "/" in search text throws 500

[Ashutosh Mestry via Review Board]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/73412/#review223129
---




repository/src/main/java/org/apache/atlas/query/IdentifierHelper.java
Lines 40 (patched)


Rename: ESCAPE_CHARACTERS_SET


- Ashutosh Mestry


On June 10, 2021, 11:32 a.m., Pinal Shah wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/73412/
> ---
> 
> (Updated June 10, 2021, 11:32 a.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry, Jayendra Parab, Nixon Rodrigues, 
> and Sarath Subramanian.
> 
> 
> Bugs: ATLAS-4332
> https://issues.apache.org/jira/browse/ATLAS-4332
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> **Problem:** In DSL query , searching with like operator in combination of 
> special characters like '/' in search text throws 500
> 
> **Example:** 
> hdfs_path name="/warehouse/tablespace/external/hive/db_fdchj.db" returns 
> right entity.
> 
> hdfs_path name like "/warehouse/*" throws following exception:
> 
> 
> Diffs
> -
> 
>   repository/src/main/java/org/apache/atlas/query/GremlinQueryComposer.java 
> 320acbe22 
>   repository/src/main/java/org/apache/atlas/query/IdentifierHelper.java 
> c53a324a1 
>   repository/src/test/java/org/apache/atlas/BasicTestSetup.java 99e075ac5 
>   repository/src/test/java/org/apache/atlas/query/BaseDSLComposer.java 
> b10400157 
>   repository/src/test/java/org/apache/atlas/query/DSLQueriesTest.java 
> 0c1dd59d2 
>   
> repository/src/test/java/org/apache/atlas/query/GremlinQueryComposerTest.java 
> 3a2d66d8c 
> 
> 
> Diff: https://reviews.apache.org/r/73412/diff/2/
> 
> 
> Testing
> ---
> 
> unit testcase added
> 
> Precommit : 
> https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/640/console
>  (In Progress)
> 
> 
> Thanks,
> 
> Pinal Shah
> 
>

Next release - 2.2 or 3.0?

[Adam Bellemare]

Hi

I'm looking to have my PR (https://github.com/apache/atlas/pull/139)
released in the next official release. Are there any plans for if that is
2.2 or 3.0?

I take it that I should be committing to branch-2.0 for the next 2.2
release, correct?

Thanks
Adam

[jira] [Commented] (ATLAS-4058) UI - On entity details page, for Hive column 'position' is getting set as 0(zero)

[ASF subversion and git services (Jira)]

[ 
https://issues.apache.org/jira/browse/ATLAS-4058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17360939#comment-17360939
 ] 

ASF subversion and git services commented on ATLAS-4058:


Commit 55cb08102214c8095fb0241d19ee792b035a58c2 in atlas's branch 
refs/heads/branch-2.0 from Nixon Rodrigues
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=55cb081 ]

Revert "ATLAS-4058: UI: Fix Entity detail page Hive Column Position with 0 is 
set to NA."

This reverts commit de87800c19ea06f53904a2948fcde29a57d2f051.

(cherry picked from commit 1078f25e90134be4a7e9f35f9774c113909aba97)


> UI - On entity details page, for Hive column 'position' is getting set as 
> 0(zero)
> -
>
> Key: ATLAS-4058
> URL: https://issues.apache.org/jira/browse/ATLAS-4058
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 2.1.0
>Reporter: Durga Kadam
>Assignee: Prasad P. Pawar
>Priority: Minor
> Fix For: 3.0.0, 2.2.0
>
> Attachments: 
> 0001-ATLAS-4058-UI-Entity-detail-page-Hive-Column-Positio.patch, 
> Atlas-4058.png, Atlas-4058_1.png, 
> screenshot-issues.apache.org-2020.12.03-10_47_09.png
>
>
> Hive Column position should get set to N/A OR blank instead of 0.
> PFA image



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (ATLAS-4058) UI - On entity details page, for Hive column 'position' is getting set as 0(zero)

[ASF subversion and git services (Jira)]

[ 
https://issues.apache.org/jira/browse/ATLAS-4058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17360935#comment-17360935
 ] 

ASF subversion and git services commented on ATLAS-4058:


Commit 1078f25e90134be4a7e9f35f9774c113909aba97 in atlas's branch 
refs/heads/master from Nixon Rodrigues
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=1078f25 ]

Revert "ATLAS-4058: UI: Fix Entity detail page Hive Column Position with 0 is 
set to NA."

This reverts commit de87800c19ea06f53904a2948fcde29a57d2f051.


> UI - On entity details page, for Hive column 'position' is getting set as 
> 0(zero)
> -
>
> Key: ATLAS-4058
> URL: https://issues.apache.org/jira/browse/ATLAS-4058
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 2.1.0
>Reporter: Durga Kadam
>Assignee: Prasad P. Pawar
>Priority: Minor
> Fix For: 3.0.0, 2.2.0
>
> Attachments: 
> 0001-ATLAS-4058-UI-Entity-detail-page-Hive-Column-Positio.patch, 
> Atlas-4058.png, Atlas-4058_1.png, 
> screenshot-issues.apache.org-2020.12.03-10_47_09.png
>
>
> Hive Column position should get set to N/A OR blank instead of 0.
> PFA image



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (ATLAS-4058) UI - On entity details page, for Hive column 'position' is getting set as 0(zero)

[Nixon Rodrigues (Jira)]

[ 
https://issues.apache.org/jira/browse/ATLAS-4058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17360934#comment-17360934
 ] 

Nixon Rodrigues commented on ATLAS-4058:


Need to revert the commit , since showing showing 0 instead NA is proper by 
design.

> UI - On entity details page, for Hive column 'position' is getting set as 
> 0(zero)
> -
>
> Key: ATLAS-4058
> URL: https://issues.apache.org/jira/browse/ATLAS-4058
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 2.1.0
>Reporter: Durga Kadam
>Assignee: Prasad P. Pawar
>Priority: Minor
> Fix For: 3.0.0, 2.2.0
>
> Attachments: 
> 0001-ATLAS-4058-UI-Entity-detail-page-Hive-Column-Positio.patch, 
> Atlas-4058.png, Atlas-4058_1.png, 
> screenshot-issues.apache.org-2020.12.03-10_47_09.png
>
>
> Hive Column position should get set to N/A OR blank instead of 0.
> PFA image



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (ATLAS-4038) Client ID field in the Admin audit result captures the Server/Host IP instead of the Client IP

[Mandar Ambawane (Jira)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-4038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mandar Ambawane resolved ATLAS-4038.

Resolution: Fixed

> Client ID field in the Admin audit result captures the Server/Host IP instead 
> of the Client IP
> --
>
> Key: ATLAS-4038
> URL: https://issues.apache.org/jira/browse/ATLAS-4038
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Mandar Ambawane
>Priority: Major
>
> The Client ID field is supposed to capture the Client address from which the 
> request is made, but it captures the server address on which this request 
> lands instead.
> This incorrect behaviour is observed in all the operations audits except 
> SERVER_START and SERVER_STATE_ACTIVE



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: Review Request 73412: ATLAS-4332 : DSL Query : query with like operator and "/" in search text throws 500

[Pinal Shah]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/73412/
---

(Updated June 10, 2021, 11:32 a.m.)


Review request for atlas, Ashutosh Mestry, Jayendra Parab, Nixon Rodrigues, and 
Sarath Subramanian.


Changes
---

addressed review comment


Bugs: ATLAS-4332
https://issues.apache.org/jira/browse/ATLAS-4332


Repository: atlas


Description
---

**Problem:** In DSL query , searching with like operator in combination of 
special characters like '/' in search text throws 500

**Example:** 
hdfs_path name="/warehouse/tablespace/external/hive/db_fdchj.db" returns right 
entity.

hdfs_path name like "/warehouse/*" throws following exception:


Diffs (updated)
-

  repository/src/main/java/org/apache/atlas/query/GremlinQueryComposer.java 
320acbe22 
  repository/src/main/java/org/apache/atlas/query/IdentifierHelper.java 
c53a324a1 
  repository/src/test/java/org/apache/atlas/BasicTestSetup.java 99e075ac5 
  repository/src/test/java/org/apache/atlas/query/BaseDSLComposer.java 
b10400157 
  repository/src/test/java/org/apache/atlas/query/DSLQueriesTest.java 0c1dd59d2 
  repository/src/test/java/org/apache/atlas/query/GremlinQueryComposerTest.java 
3a2d66d8c 


Diff: https://reviews.apache.org/r/73412/diff/2/

Changes: https://reviews.apache.org/r/73412/diff/1-2/


Testing
---

unit testcase added

Precommit : 
https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/640/console
 (In Progress)


Thanks,

Pinal Shah

[jira] [Commented] (ATLAS-4283) UI: Description cannot be made blank for classification

[Prasad P. Pawar (Jira)]

[ 
https://issues.apache.org/jira/browse/ATLAS-4283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17360596#comment-17360596
 ] 

Prasad P. Pawar commented on ATLAS-4283:


cdpd commit id: f048f84e78840387822d5ab5a5678f17756aa0b1

> UI: Description cannot be made blank for classification
> ---
>
> Key: ATLAS-4283
> URL: https://issues.apache.org/jira/browse/ATLAS-4283
> Project: Atlas
>  Issue Type: Bug
>Reporter: Rahul Kurup
>Assignee: Prasad P. Pawar
>Priority: Minor
> Attachments: 
> 0001-ATLAS-4283-UI-Description-cannot-be-made-blank-for-c.patch
>
>
> If there is an existing description for a classification, and if the user 
> attempts to update it to blank, he will not be able to do so.
> The API response for when the user inputs a blank value shows that the 
> updated value for the description is the same as the original value.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Comment Edited] (ATLAS-4283) UI: Description cannot be made blank for classification

[Prasad P. Pawar (Jira)]

[ 
https://issues.apache.org/jira/browse/ATLAS-4283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17360596#comment-17360596
 ] 

Prasad P. Pawar edited comment on ATLAS-4283 at 6/10/21, 6:39 AM:
--

cdpd master:commit id: f048f84e78840387822d5ab5a5678f17756aa0b1


was (Author: prasadpp13):
cdpd commit id: f048f84e78840387822d5ab5a5678f17756aa0b1

> UI: Description cannot be made blank for classification
> ---
>
> Key: ATLAS-4283
> URL: https://issues.apache.org/jira/browse/ATLAS-4283
> Project: Atlas
>  Issue Type: Bug
>Reporter: Rahul Kurup
>Assignee: Prasad P. Pawar
>Priority: Minor
> Attachments: 
> 0001-ATLAS-4283-UI-Description-cannot-be-made-blank-for-c.patch
>
>
> If there is an existing description for a classification, and if the user 
> attempts to update it to blank, he will not be able to do so.
> The API response for when the user inputs a blank value shows that the 
> updated value for the description is the same as the original value.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (ATLAS-4295) UI: The short/long description of term & category doesnt get updated immediately when made blank

[Prasad P. Pawar (Jira)]

[ 
https://issues.apache.org/jira/browse/ATLAS-4295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17360594#comment-17360594
 ] 

Prasad P. Pawar commented on ATLAS-4295:


commit it: 5c11def9ed377d18199281c223d57c9725ff054a

> UI: The short/long description of term & category doesnt get updated 
> immediately when made blank
> 
>
> Key: ATLAS-4295
> URL: https://issues.apache.org/jira/browse/ATLAS-4295
> Project: Atlas
>  Issue Type: Bug
>Reporter: Rahul Kurup
>Assignee: Prasad P. Pawar
>Priority: Minor
> Attachments: 
> 0001-ATLAS-4295-UI-UI-The-short-long-description-of-term-.patch
>
>
> When one empties the the short and long description fields of term & category 
> and saves,
> the UI doesn't get reflected immediately. But on refresh, it gets reflected.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (ATLAS-3926) Atlas1.2 with Kerberos problem

[wentaoyang (Jira)]

[ 
https://issues.apache.org/jira/browse/ATLAS-3926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17360582#comment-17360582
 ] 

wentaoyang commented on ATLAS-3926:
---

I use kinit operation before  run the import script,But I still have the same 
problem.

> Atlas1.2 with Kerberos problem
> --
>
> Key: ATLAS-3926
> URL: https://issues.apache.org/jira/browse/ATLAS-3926
> Project: Atlas
>  Issue Type: Bug
>  Components: falcon-integration, hive-integration
>Affects Versions: 1.2.0
>Reporter: yuyu
>Priority: Major
> Fix For: 1.2.0
>
> Attachments: 1.png, 2.png, image-2020-08-25-16-29-12-906.png, 
> image-2020-08-25-16-29-29-667.png, image-2020-08-25-16-30-34-221.png, 
> image-2020-08-25-16-31-23-439.png, image-2020-08-25-16-31-28-330.png, 
> image-2020-08-25-16-34-41-642.png, image-2020-08-25-16-35-09-836.png, 
> image-2020-08-25-16-38-45-645.png, image-2020-08-26-16-34-34-457.png
>
>
> Hello, everyone. Recently, I encountered a problem with Kerberos when 
> deploying atlas.I tried to deploy atlas service on my CDH cluster with CDH 
> version 5.16 and Kerberos service deployed.My installation method is Atlas 
> 1.2 integrated CDH HBase and external 5.5.1 Solr
> When I start the atlas service, I can successfully access the atlas web page 
> through my computer：
> !image-2020-08-25-16-29-29-667.png!
> But when I tried to import hive metadata information, something went wrong，as 
> shown in the figure below:
> !image-2020-08-25-16-30-34-221.png!
> !image-2020-08-25-16-38-45-645.png!
> !image-2020-08-25-16-31-28-330.png!
> It seems to indicate that I don't have a valid Kerberos principal?
> Here is part of my atlas configuration file  atlas-application.properties：
> !image-2020-08-25-16-34-41-642.png!
> !image-2020-08-25-16-35-09-836.png!
> Can anyone tell me what the problem is,thanks.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)