[jira] [Commented] (ATLAS-3852) Entity Bulk Create with unique reference

2020-07-01 Thread Vasanth kumar RJ (Jira)


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

Vasanth kumar RJ commented on ATLAS-3852:
-

[~madhan] I shared my use case and patch got test cases. Can you guide me 
whether this patch is useful or not? 

> Entity Bulk Create with unique reference
> 
>
> Key: ATLAS-3852
> URL: https://issues.apache.org/jira/browse/ATLAS-3852
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Vasanth kumar RJ
>Priority: Major
> Fix For: 2.1.0
>
> Attachments: ATLAS-3852.patch, BulkPostCreate.json
>
>
> Entities created in bulk and unique referenced in same request. Bulk create 
> DB, Table and Column referenced in a request itself.



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


[jira] [Commented] (ATLAS-3852) Entity Bulk Create with unique reference

2020-06-25 Thread Vasanth kumar RJ (Jira)


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

Vasanth kumar RJ commented on ATLAS-3852:
-

[~nikhilbonte] - I feel using actual unique attribute (qualifiedName) for 
reference will avoid error and readable when a bulk request got multiple db, 
table and columns. Negative guid is temporary value.

> Entity Bulk Create with unique reference
> 
>
> Key: ATLAS-3852
> URL: https://issues.apache.org/jira/browse/ATLAS-3852
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Vasanth kumar RJ
>Priority: Major
> Fix For: 2.1.0
>
> Attachments: ATLAS-3852.patch, BulkPostCreate.json
>
>
> Entities created in bulk and unique referenced in same request. Bulk create 
> DB, Table and Column referenced in a request itself.



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


[jira] [Commented] (ATLAS-3852) Entity Bulk Create with unique reference

2020-06-23 Thread Vasanth kumar RJ (Jira)


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

Vasanth kumar RJ commented on ATLAS-3852:
-

[~madhan] - Currently in Entity Bulk POST API, every entity referenced ( Table 
entity -> DB reference) using guid or unique attribute which is created 
already. We cannot create DB and Table Entity with referenced in same bulk 
request.

Fix to support bulk create DB entity and table entity reference to DB in same 
request.

Use case to support creation new DB entity, its new Table entities and new 
Column Entities in a bulk request.

> Entity Bulk Create with unique reference
> 
>
> Key: ATLAS-3852
> URL: https://issues.apache.org/jira/browse/ATLAS-3852
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Vasanth kumar RJ
>Priority: Major
> Fix For: 2.1.0
>
> Attachments: ATLAS-3852.patch
>
>
> Entities created in bulk and unique referenced in same request. Bulk create 
> DB, Table and Column referenced in a request itself.



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


[jira] [Commented] (ATLAS-3852) Entity Bulk Create with unique reference

2020-06-23 Thread Vasanth kumar RJ (Jira)


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

Vasanth kumar RJ commented on ATLAS-3852:
-

[~mad...@apache.org] [~sarath] Please review this ticket.

> Entity Bulk Create with unique reference
> 
>
> Key: ATLAS-3852
> URL: https://issues.apache.org/jira/browse/ATLAS-3852
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Vasanth kumar RJ
>Priority: Major
> Fix For: 2.1.0
>
> Attachments: ATLAS-3852.patch
>
>
> Entities created in bulk and unique referenced in same request. Bulk create 
> DB, Table and Column referenced in a request itself.



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


[jira] [Updated] (ATLAS-3852) Entity Bulk Create with unique reference

2020-06-21 Thread Vasanth kumar RJ (Jira)


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

Vasanth kumar RJ updated ATLAS-3852:

Attachment: ATLAS-3852.patch

> Entity Bulk Create with unique reference
> 
>
> Key: ATLAS-3852
> URL: https://issues.apache.org/jira/browse/ATLAS-3852
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Vasanth kumar RJ
>Priority: Major
> Fix For: 2.1.0
>
> Attachments: ATLAS-3852.patch
>
>
> Entities created in bulk and unique referenced in same request. Bulk create 
> DB, Table and Column referenced in a request itself.



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


[jira] [Created] (ATLAS-3852) Entity Bulk Create with unique reference

2020-06-21 Thread Vasanth kumar RJ (Jira)
Vasanth kumar RJ created ATLAS-3852:
---

 Summary: Entity Bulk Create with unique reference
 Key: ATLAS-3852
 URL: https://issues.apache.org/jira/browse/ATLAS-3852
 Project: Atlas
  Issue Type: Improvement
Reporter: Vasanth kumar RJ
 Fix For: 2.1.0


Entities created in bulk and unique referenced in same request. Bulk create DB, 
Table and Column referenced in a request itself.



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


[jira] [Commented] (ATLAS-3167) Exception while starting Atlas with Cassandra

2019-04-27 Thread Vasanth kumar RJ (JIRA)


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

Vasanth kumar RJ commented on ATLAS-3167:
-

Exception thrown for build with 'mvn clean -DskipTests package -Pdist' and then 
start Atlas with Cassandra backend.

> Exception while starting Atlas with Cassandra
> -
>
> Key: ATLAS-3167
> URL: https://issues.apache.org/jira/browse/ATLAS-3167
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Chaitra Rao
>Assignee: Madhan Neethiraj
>Priority: Critical
> Fix For: 2.0.0
>
> Attachments: ATLAS-3167.patch
>
>
> When I try to start Atlas (2.0.0-SNAPSHOT), I get the following error - 
> ==
> 019-04-23 19:11:37,094 ERROR - [MemtableFlushWriter:1:] ~ Exception in thread 
> Thread[MemtableFlushWriter:1,5,main] (CassandraDaemon$1:223)
> java.lang.NoSuchMethodError: 
> com.google.common.util.concurrent.MoreExecutors.sameThreadExecutor()Lcom/google/common/util/concurrent/ListeningExecutorService;
>         at 
> org.apache.cassandra.db.ColumnFamilyStore$Flush.run(ColumnFamilyStore.java:1127)
>         at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>         at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>         at java.lang.Thread.run(Thread.java:748)
>  
> ==
> Guava jar - com.google.guava:guava:jar:25.1 is used throughout. Do not see 
> any conflicting guava jars, except for com.google.guava:guava:jar:12.0.1 from 
> kafka-bridge pom. Excluding this did not work as well.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (ATLAS-3167) Exception while starting Atlas with Cassandra

2019-04-27 Thread Vasanth kumar RJ (JIRA)


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

Vasanth kumar RJ commented on ATLAS-3167:
-

[~madhan.neethiraj]
Is this patch only for 'embedded-cassandra-solr'? 
we tried changing guava version to 19.0 at \{atlas.home}/pom.xml. All test 
cases passed and worked as expected with Non-Embedded Cassandra backend. 

> Exception while starting Atlas with Cassandra
> -
>
> Key: ATLAS-3167
> URL: https://issues.apache.org/jira/browse/ATLAS-3167
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Chaitra Rao
>Assignee: Madhan Neethiraj
>Priority: Critical
> Fix For: 2.0.0
>
> Attachments: ATLAS-3167.patch
>
>
> When I try to start Atlas (2.0.0-SNAPSHOT), I get the following error - 
> ==
> 019-04-23 19:11:37,094 ERROR - [MemtableFlushWriter:1:] ~ Exception in thread 
> Thread[MemtableFlushWriter:1,5,main] (CassandraDaemon$1:223)
> java.lang.NoSuchMethodError: 
> com.google.common.util.concurrent.MoreExecutors.sameThreadExecutor()Lcom/google/common/util/concurrent/ListeningExecutorService;
>         at 
> org.apache.cassandra.db.ColumnFamilyStore$Flush.run(ColumnFamilyStore.java:1127)
>         at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>         at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>         at java.lang.Thread.run(Thread.java:748)
>  
> ==
> Guava jar - com.google.guava:guava:jar:25.1 is used throughout. Do not see 
> any conflicting guava jars, except for com.google.guava:guava:jar:12.0.1 from 
> kafka-bridge pom. Excluding this did not work as well.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (ATLAS-3106) Atlas client request custom header

2019-03-29 Thread Vasanth kumar RJ (JIRA)


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

Vasanth kumar RJ updated ATLAS-3106:

Attachment: (was: ATLAS-3106.patch)

> Atlas client request custom header
> --
>
> Key: ATLAS-3106
> URL: https://issues.apache.org/jira/browse/ATLAS-3106
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Vasanth kumar RJ
>Priority: Minor
> Attachments: ATLAS-3106.patch
>
>
> Add custom header in Atlas client rest calls.
> Our use cases:
> - Request tracking: Add unique logging id in header for every rest api 
> request which will be set into Atlas server Logger MDC (working on this).
> - Our custom authentication and authorization requires more details from user 
> that can be passed through request header.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (ATLAS-3106) Atlas client request custom header

2019-03-29 Thread Vasanth kumar RJ (JIRA)


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

Vasanth kumar RJ updated ATLAS-3106:

Attachment: ATLAS-3106.patch

> Atlas client request custom header
> --
>
> Key: ATLAS-3106
> URL: https://issues.apache.org/jira/browse/ATLAS-3106
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Vasanth kumar RJ
>Priority: Minor
> Attachments: ATLAS-3106.patch, ATLAS-3106.patch
>
>
> Add custom header in Atlas client rest calls.
> Our use cases:
> - Request tracking: Add unique logging id in header for every rest api 
> request which will be set into Atlas server Logger MDC (working on this).
> - Our custom authentication and authorization requires more details from user 
> that can be passed through request header.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (ATLAS-3106) Atlas client request custom header

2019-03-29 Thread Vasanth kumar RJ (JIRA)
Vasanth kumar RJ created ATLAS-3106:
---

 Summary: Atlas client request custom header
 Key: ATLAS-3106
 URL: https://issues.apache.org/jira/browse/ATLAS-3106
 Project: Atlas
  Issue Type: Improvement
Reporter: Vasanth kumar RJ


Add custom header in Atlas client rest calls.

Our use cases:
- Request tracking: Add unique logging id in header for every rest api request 
which will be set into Atlas server Logger MDC (working on this).
- Our custom authentication and authorization requires more details from user 
that can be passed through request header.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)