[jira] [Updated] (ATLAS-696) Add testing of titan 1 to Atlas build

[Neeru Gupta (JIRA)]

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

Neeru Gupta updated ATLAS-696:
--
Description: 
We need to have automated testing of the titan 1.0.0 support in Atlas to ensure 
that no regressions are introduced.
This is for Jenkins builds which are executed by Atlas.


  was:We need to have automated testing of the titan 1.0.0 support in Atlas to 
ensure that no regressions are introduced.


> Add testing of titan 1 to Atlas build
> -
>
> Key: ATLAS-696
> URL: https://issues.apache.org/jira/browse/ATLAS-696
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Jeffrey Hagelberg
>Assignee: Jeffrey Hagelberg
>
> We need to have automated testing of the titan 1.0.0 support in Atlas to 
> ensure that no regressions are introduced.
> This is for Jenkins builds which are executed by Atlas.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ATLAS-696) Add testing of titan 1 to Atlas build

[Neeru Gupta (JIRA)]

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

Neeru Gupta commented on ATLAS-696:
---

Titan1 tests will be executed  if build enables titan1 profile in command line. 
once #695 is committed.

> Add testing of titan 1 to Atlas build
> -
>
> Key: ATLAS-696
> URL: https://issues.apache.org/jira/browse/ATLAS-696
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Jeffrey Hagelberg
>Assignee: Jeffrey Hagelberg
>
> We need to have automated testing of the titan 1.0.0 support in Atlas to 
> ensure that no regressions are introduced.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-695) Add titan 1 implementation of graph database abstraction layer

[Neeru Gupta (JIRA)]

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

Neeru Gupta updated ATLAS-695:
--
Attachment: rb56289.patch

> Add titan 1 implementation of graph database abstraction layer
> --
>
> Key: ATLAS-695
> URL: https://issues.apache.org/jira/browse/ATLAS-695
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Jeffrey Hagelberg
>Assignee: Neeru Gupta
> Attachments: rb56289.patch
>
>
> In this task, we will do the following:
> - add titan 1.0.0 implementation of abstraction layer
> - refactor query generation to produce different gremlin for Titan 0.5.4 and 
> Titan 1.0.0.  This is needed because there are significant syntax changes 
> between Gremlin 2 and Gremlin 3.  
> - add mechanism to allow the titan version / abstraction implementation to be 
> configured in the atlas-application.properties file
> - by default, the titan 1.0.0 implementation will not be built.  It requires 
> Java 8.  There is a separate subtask for incorporating testing if Java 8 into 
> the build.
> - Upon completion of this task, you will be able to build Atlas in either 
> "titan1" or "titan0" mode.  These will mutually exclusive.  In the future we 
> can look at ways to build both at the same time.  I have some ideas about how 
> this can work, but we have a lot of things to do before we can get to that!



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (ATLAS-1591) Repository test failures with Titan1 profile

[Neeru Gupta (JIRA)]

Neeru Gupta created ATLAS-1591:
--

 Summary: Repository test failures with Titan1 profile
 Key: ATLAS-1591
 URL: https://issues.apache.org/jira/browse/ATLAS-1591
 Project: Atlas
  Issue Type: Bug
Reporter: Neeru Gupta


HBaseAuditrepostiryTests are failing with titan1 profile. It is unable to 
instantiate the hbase. It looks like current version of hbase/hadoop is not 
compatible with JDK8. 

Tests run: 6, Failures: 4, Errors: 0, Skipped: 2, Time elapsed: 4.06 sec <<< 
FAILURE! - in org.apache.atlas.repository.audit.HBaseBasedAuditRepositoryTest
setup(org.apache.atlas.repository.audit.HBaseBasedAuditRepositoryTest)  Time 
elapsed: 3.313 sec  <<< FAILURE!
java.lang.RuntimeException: Failed construction of Master: class 
org.apache.hadoop.hbase.master.HMaster
at 
org.apache.hadoop.hbase.master.MasterRpcServices.getServices(MasterRpcServices.java:262)
at 
org.apache.hadoop.hbase.regionserver.RSRpcServices.(RSRpcServices.java:863)
at 
org.apache.hadoop.hbase.master.MasterRpcServices.(MasterRpcServices.java:210)
at 
org.apache.hadoop.hbase.master.HMaster.createRpcServices(HMaster.java:532)
at 
org.apache.hadoop.hbase.regionserver.HRegionServer.(HRegionServer.java:532)
at org.apache.hadoop.hbase.master.HMaster.(HMaster.java:364)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1582) Fix Webapp test failures with titan1 as graph backend

[Neeru Gupta (JIRA)]

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

Neeru Gupta updated ATLAS-1582:
---
Description: 
Some of the webapp tests fail because of dependency on catalog project. It is 
unable to start the jetty server, as it can't find the Catalog classes. 

Catalog project is hard-coded to generate Gremlin that is specific to Tinker 
Pop 2.  It needs to be updated to use GremlinExpressionFactory to generate 
Gremlin that is appropriate for the version of Titan being used.  In addition, 
it has direct dependencies on titan 0 / Tinker Pop 2 classes. 


Caused by: java.lang.ClassNotFoundException: 
org.apache.atlas.catalog.exception.CatalogRuntimeException
at 
org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
at 
org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271)
at 
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:247)
at 
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239)
at 
org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:450)
at 
org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:403)


> Fix Webapp test failures with titan1 as graph backend
> -
>
> Key: ATLAS-1582
> URL: https://issues.apache.org/jira/browse/ATLAS-1582
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Neeru Gupta
>
> Some of the webapp tests fail because of dependency on catalog project. It is 
> unable to start the jetty server, as it can't find the Catalog classes. 
> Catalog project is hard-coded to generate Gremlin that is specific to Tinker 
> Pop 2.  It needs to be updated to use GremlinExpressionFactory to generate 
> Gremlin that is appropriate for the version of Titan being used.  In 
> addition, it has direct dependencies on titan 0 / Tinker Pop 2 classes. 
> Caused by: java.lang.ClassNotFoundException: 
> org.apache.atlas.catalog.exception.CatalogRuntimeException
> at 
> org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
> at 
> org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271)
> at 
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:247)
> at 
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239)
> at 
> org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:450)
> at 
> org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:403)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (ATLAS-1582) Fix Webapp test failures with titan1 as graph backend

[Neeru Gupta (JIRA)]

Neeru Gupta created ATLAS-1582:
--

 Summary: Fix Webapp test failures with titan1 as graph backend
 Key: ATLAS-1582
 URL: https://issues.apache.org/jira/browse/ATLAS-1582
 Project: Atlas
  Issue Type: Improvement
Reporter: Neeru Gupta






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (ATLAS-1581) Fix Atlas start up with titan1 as backend.

[Neeru Gupta (JIRA)]

Neeru Gupta created ATLAS-1581:
--

 Summary: Fix Atlas start up with titan1 as backend.
 Key: ATLAS-1581
 URL: https://issues.apache.org/jira/browse/ATLAS-1581
 Project: Atlas
  Issue Type: Improvement
Reporter: Neeru Gupta


The Atlas war file startup is currently failing when Titan1 is being used.  Due 
to the titan 0 dependencies in catalog, the catalog jar is currently being 
excluded from webapp when titan1 is being used.  However, Atlas appears to have 
runtime dependencies on the stuff in Catalog.  The war startup currently fails 
with the following exception:
Caused by: java.lang.ClassNotFoundException: 
org.apache.atlas.catalog.exception.CatalogException
at 
org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
at 
org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (ATLAS-1580) Fix Catalog project to use GremlinExpressionFactory to avoid direct dependecy on titan0 and hard coded gremlin2.

[Neeru Gupta (JIRA)]

Neeru Gupta created ATLAS-1580:
--

 Summary: Fix Catalog project to use GremlinExpressionFactory to 
avoid direct dependecy on titan0 and hard coded gremlin2.
 Key: ATLAS-1580
 URL: https://issues.apache.org/jira/browse/ATLAS-1580
 Project: Atlas
  Issue Type: Improvement
Reporter: Neeru Gupta


Catalog project is hard-coded to generate Gremlin that is specific to Tinker 
Pop 2.  It needs to be updated to use GremlinExpressionFactory to generate 
Gremlin that is appropriate for the version of Titan being used.  In addition, 
it has direct dependencies on titan 0 / Tinker Pop 2 classes.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (ATLAS-1579) Fix EntityLineageSevice Tests to run against TP3

[Neeru Gupta (JIRA)]

Neeru Gupta created ATLAS-1579:
--

 Summary: Fix EntityLineageSevice Tests to run against TP3
 Key: ATLAS-1579
 URL: https://issues.apache.org/jira/browse/ATLAS-1579
 Project: Atlas
  Issue Type: Improvement
  Components:  atlas-core
Reporter: Neeru Gupta


EntityLineageService is hard-coded to generate Gremlin that is specific to 
Tinker Pop 2.  It needs to be updated to use GremlinExpressionFactory to 
generate Gremlin that is appropriate for the version of Titan being used.

Titan1 tests fail because of this issue. #ATLAS-695



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (ATLAS-695) Add titan 1 implementation of graph database abstraction layer

[Neeru Gupta (JIRA)]

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

Neeru Gupta reassigned ATLAS-695:
-

Assignee: Neeru Gupta  (was: Jeffrey Hagelberg)

> Add titan 1 implementation of graph database abstraction layer
> --
>
> Key: ATLAS-695
> URL: https://issues.apache.org/jira/browse/ATLAS-695
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Jeffrey Hagelberg
>Assignee: Neeru Gupta
>
> In this task, we will do the following:
> - add titan 1.0.0 implementation of abstraction layer
> - refactor query generation to produce different gremlin for Titan 0.5.4 and 
> Titan 1.0.0.  This is needed because there are significant syntax changes 
> between Gremlin 2 and Gremlin 3.  
> - add mechanism to allow the titan version / abstraction implementation to be 
> configured in the atlas-application.properties file
> - by default, the titan 1.0.0 implementation will not be built.  It requires 
> Java 8.  There is a separate subtask for incorporating testing if Java 8 into 
> the build.
> - Upon completion of this task, you will be able to build Atlas in either 
> "titan1" or "titan0" mode.  These will mutually exclusive.  In the future we 
> can look at ways to build both at the same time.  I have some ideas about how 
> this can work, but we have a lot of things to do before we can get to that!



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (ATLAS-1379) Avoid object query overhead when report query selects class type alias

[Neeru Gupta (JIRA)]

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

Neeru Gupta closed ATLAS-1379.
--

> Avoid object query overhead when report query selects class type alias
> --
>
> Key: ATLAS-1379
> URL: https://issues.apache.org/jira/browse/ATLAS-1379
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Neeru Gupta
>Assignee: Neeru Gupta
>  Labels: performance
> Fix For: 0.8-incubating
>
> Attachments: rb54759(1).patch
>
>
> When the DSL query is selecting the class alias, which causes Atlas to run an 
> object query. Atlas should detect this query construct and avoid the overhead 
> of full entity retrieval, when the entity ends up being serialized as an 
> structure that just contains the guid, type, and status.
> For queries like: 'from hive_db  as h select h', even though the end result 
> only contains id object, Atlas code initially loads the entire object with 
> all its properties and while serializing it ends up serializing only the id 
> part. This bug is to avoid the overhead of loading the entire object when 
> fields other than id will be discarded anyways. This added a lot of overhead 
> and was identified as hotspot in our internal testing. This is specially 
> relevant when large number of objects are retrieved as search results. 
> Note that the fixes are backward compatible. The end result remains the same. 
> Only the overwork to load unnecessary fields is avoided.
> Sample Query: 'from hive_db as h select h'
> Result:
> rows":[
> {
>   "$typeName$":"__tempQueryResultStruct2",
>   "id":{
> "id":"8159ee38-ec29-4d9a-845a-86fe17ab6bdb",
> "$typeName$":"hive_db",
> "version":0,
> "state":"ACTIVE"
>   }
> },
> {
>   "$typeName$":"__tempQueryResultStruct2",
>   "id":{
> "id":"33016845-4b71-4d56-b131-b48ea38e5507",
> "$typeName$":"hive_db",
> "version":0,
> "state":"ACTIVE"
>   }
> },
> {
>   "$typeName$":"__tempQueryResultStruct2",
>   "id":{
> "id":"b6fb9c53-680e-4be7-b143-f8d9355c5726",
> "$typeName$":"hive_db",
> "version":0,
> "state":"ACTIVE"
>   }
> }
>   ]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (ATLAS-1379) Avoid object query overhead when report query selects class type alias

[Neeru Gupta (JIRA)]

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

Neeru Gupta updated ATLAS-1379:
---
Attachment: (was: rb54759.patch)

> Avoid object query overhead when report query selects class type alias
> --
>
> Key: ATLAS-1379
> URL: https://issues.apache.org/jira/browse/ATLAS-1379
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Neeru Gupta
>Assignee: Neeru Gupta
>  Labels: performance
> Fix For: 0.8-incubating
>
> Attachments: rb54759(1).patch
>
>
> When the DSL query is selecting the class alias, which causes Atlas to run an 
> object query. Atlas should detect this query construct and avoid the overhead 
> of full entity retrieval, when the entity ends up being serialized as an 
> structure that just contains the guid, type, and status.
> For queries like: 'from hive_db  as h select h', even though the end result 
> only contains id object, Atlas code initially loads the entire object with 
> all its properties and while serializing it ends up serializing only the id 
> part. This bug is to avoid the overhead of loading the entire object when 
> fields other than id will be discarded anyways. This added a lot of overhead 
> and was identified as hotspot in our internal testing. This is specially 
> relevant when large number of objects are retrieved as search results. 
> Note that the fixes are backward compatible. The end result remains the same. 
> Only the overwork to load unnecessary fields is avoided.
> Sample Query: 'from hive_db as h select h'
> Result:
> rows":[
> {
>   "$typeName$":"__tempQueryResultStruct2",
>   "id":{
> "id":"8159ee38-ec29-4d9a-845a-86fe17ab6bdb",
> "$typeName$":"hive_db",
> "version":0,
> "state":"ACTIVE"
>   }
> },
> {
>   "$typeName$":"__tempQueryResultStruct2",
>   "id":{
> "id":"33016845-4b71-4d56-b131-b48ea38e5507",
> "$typeName$":"hive_db",
> "version":0,
> "state":"ACTIVE"
>   }
> },
> {
>   "$typeName$":"__tempQueryResultStruct2",
>   "id":{
> "id":"b6fb9c53-680e-4be7-b143-f8d9355c5726",
> "$typeName$":"hive_db",
> "version":0,
> "state":"ACTIVE"
>   }
> }
>   ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-1379) Avoid object query overhead when report query selects class type alias

[Neeru Gupta (JIRA)]

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

Neeru Gupta updated ATLAS-1379:
---
Attachment: rb54759(1).patch

> Avoid object query overhead when report query selects class type alias
> --
>
> Key: ATLAS-1379
> URL: https://issues.apache.org/jira/browse/ATLAS-1379
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Neeru Gupta
>Assignee: Neeru Gupta
>  Labels: performance
> Fix For: 0.8-incubating
>
> Attachments: rb54759(1).patch
>
>
> When the DSL query is selecting the class alias, which causes Atlas to run an 
> object query. Atlas should detect this query construct and avoid the overhead 
> of full entity retrieval, when the entity ends up being serialized as an 
> structure that just contains the guid, type, and status.
> For queries like: 'from hive_db  as h select h', even though the end result 
> only contains id object, Atlas code initially loads the entire object with 
> all its properties and while serializing it ends up serializing only the id 
> part. This bug is to avoid the overhead of loading the entire object when 
> fields other than id will be discarded anyways. This added a lot of overhead 
> and was identified as hotspot in our internal testing. This is specially 
> relevant when large number of objects are retrieved as search results. 
> Note that the fixes are backward compatible. The end result remains the same. 
> Only the overwork to load unnecessary fields is avoided.
> Sample Query: 'from hive_db as h select h'
> Result:
> rows":[
> {
>   "$typeName$":"__tempQueryResultStruct2",
>   "id":{
> "id":"8159ee38-ec29-4d9a-845a-86fe17ab6bdb",
> "$typeName$":"hive_db",
> "version":0,
> "state":"ACTIVE"
>   }
> },
> {
>   "$typeName$":"__tempQueryResultStruct2",
>   "id":{
> "id":"33016845-4b71-4d56-b131-b48ea38e5507",
> "$typeName$":"hive_db",
> "version":0,
> "state":"ACTIVE"
>   }
> },
> {
>   "$typeName$":"__tempQueryResultStruct2",
>   "id":{
> "id":"b6fb9c53-680e-4be7-b143-f8d9355c5726",
> "$typeName$":"hive_db",
> "version":0,
> "state":"ACTIVE"
>   }
> }
>   ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-1391) Add exclusion mechanism for Atlas audit mechanism

[Neeru Gupta (JIRA)]

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

Neeru Gupta updated ATLAS-1391:
---
Attachment: (was: rb54907.patch)

> Add exclusion mechanism for Atlas audit mechanism
> -
>
> Key: ATLAS-1391
> URL: https://issues.apache.org/jira/browse/ATLAS-1391
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Neeru Gupta
>Assignee: Neeru Gupta
> Attachments: rb54907(1).patch
>
>
> As a consumer of Atlas, I want to be able to exclude certain operations, such 
> as ping, from the audit log so that it does not get filled up with noise.
> This should be a general mechanism. It should be possible to configure the 
> endpoints being excluded in the Atlas configuration file. The only 
> requirement at this time is to be able to filter based on the high level 
> operation being invoked (ie ping, version, etc). There is no need to be able 
> to filter based on the arguments to the operation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-1391) Add exclusion mechanism for Atlas audit mechanism

[Neeru Gupta (JIRA)]

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

Neeru Gupta updated ATLAS-1391:
---
Attachment: rb54907(1).patch

Rebased with trunk.

> Add exclusion mechanism for Atlas audit mechanism
> -
>
> Key: ATLAS-1391
> URL: https://issues.apache.org/jira/browse/ATLAS-1391
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Neeru Gupta
>Assignee: Neeru Gupta
> Attachments: rb54907(1).patch
>
>
> As a consumer of Atlas, I want to be able to exclude certain operations, such 
> as ping, from the audit log so that it does not get filled up with noise.
> This should be a general mechanism. It should be possible to configure the 
> endpoints being excluded in the Atlas configuration file. The only 
> requirement at this time is to be able to filter based on the high level 
> operation being invoked (ie ping, version, etc). There is no need to be able 
> to filter based on the arguments to the operation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-1391) Add exclusion mechanism for Atlas audit mechanism

[Neeru Gupta (JIRA)]

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

Neeru Gupta updated ATLAS-1391:
---
External issue URL: https://reviews.apache.org/r/54907/
   Description: 

As a consumer of Atlas, I want to be able to exclude certain operations, such 
as ping, from the audit log so that it does not get filled up with noise.

This should be a general mechanism. It should be possible to configure the 
endpoints being excluded in the Atlas configuration file. The only requirement 
at this time is to be able to filter based on the high level operation being 
invoked (ie ping, version, etc). There is no need to be able to filter based on 
the arguments to the operation.


  was:


As a consumer of Atlas, I want to be able to exclude certain operations, such 
as ping, from the audit log so that it does not get filled up with noise.

This should be a general mechanism. It should be possible to configure the 
endpoints being excluded in the Atlas configuration file. The only requirement 
at this time is to be able to filter based on the high level operation being 
invoked (ie ping, version, etc). There is no need to be able to filter based on 
the arguments to the operation.



> Add exclusion mechanism for Atlas audit mechanism
> -
>
> Key: ATLAS-1391
> URL: https://issues.apache.org/jira/browse/ATLAS-1391
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Neeru Gupta
>Assignee: Neeru Gupta
> Attachments: rb54907.patch
>
>
> As a consumer of Atlas, I want to be able to exclude certain operations, such 
> as ping, from the audit log so that it does not get filled up with noise.
> This should be a general mechanism. It should be possible to configure the 
> endpoints being excluded in the Atlas configuration file. The only 
> requirement at this time is to be able to filter based on the high level 
> operation being invoked (ie ping, version, etc). There is no need to be able 
> to filter based on the arguments to the operation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-1391) Add exclusion mechanism for Atlas audit mechanism

[Neeru Gupta (JIRA)]

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

Neeru Gupta updated ATLAS-1391:
---
Attachment: rb54907.patch

> Add exclusion mechanism for Atlas audit mechanism
> -
>
> Key: ATLAS-1391
> URL: https://issues.apache.org/jira/browse/ATLAS-1391
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Neeru Gupta
>Assignee: Neeru Gupta
> Attachments: rb54907.patch
>
>
> As a consumer of Atlas, I want to be able to exclude certain operations, such 
> as ping, from the audit log so that it does not get filled up with noise.
> This should be a general mechanism. It should be possible to configure the 
> endpoints being excluded in the Atlas configuration file. The only 
> requirement at this time is to be able to filter based on the high level 
> operation being invoked (ie ping, version, etc). There is no need to be able 
> to filter based on the arguments to the operation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (ATLAS-1393) Add Multitenancy in titan1

[Neeru Gupta (JIRA)]

Neeru Gupta created ATLAS-1393:
--

 Summary: Add Multitenancy in titan1
 Key: ATLAS-1393
 URL: https://issues.apache.org/jira/browse/ATLAS-1393
 Project: Atlas
  Issue Type: Sub-task
Reporter: Neeru Gupta
Assignee: Neeru Gupta






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (ATLAS-1391) Add exclusion mechanism for Atlas audit mechanism

[Neeru Gupta (JIRA)]

Neeru Gupta created ATLAS-1391:
--

 Summary: Add exclusion mechanism for Atlas audit mechanism
 Key: ATLAS-1391
 URL: https://issues.apache.org/jira/browse/ATLAS-1391
 Project: Atlas
  Issue Type: Improvement
Reporter: Neeru Gupta
Assignee: Neeru Gupta




As a consumer of Atlas, I want to be able to exclude certain operations, such 
as ping, from the audit log so that it does not get filled up with noise.

This should be a general mechanism. It should be possible to configure the 
endpoints being excluded in the Atlas configuration file. The only requirement 
at this time is to be able to filter based on the high level operation being 
invoked (ie ping, version, etc). There is no need to be able to filter based on 
the arguments to the operation.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-1379) Avoid object query overhead when report query selects class type alias

[Neeru Gupta (JIRA)]

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

Neeru Gupta updated ATLAS-1379:
---
Attachment: rb54759.patch

> Avoid object query overhead when report query selects class type alias
> --
>
> Key: ATLAS-1379
> URL: https://issues.apache.org/jira/browse/ATLAS-1379
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Neeru Gupta
>Assignee: Neeru Gupta
>  Labels: performance
> Fix For: 0.8-incubating
>
> Attachments: rb54759.patch
>
>
> When the DSL query is selecting the class alias, which causes Atlas to run an 
> object query. Atlas should detect this query construct and avoid the overhead 
> of full entity retrieval, when the entity ends up being serialized as an 
> structure that just contains the guid, type, and status.
> For queries like: 'from hive_db  as h select h', even though the end result 
> only contains id object, Atlas code initially loads the entire object with 
> all its properties and while serializing it ends up serializing only the id 
> part. This bug is to avoid the overhead of loading the entire object when 
> fields other than id will be discarded anyways. This added a lot of overhead 
> and was identified as hotspot in our internal testing. This is specially 
> relevant when large number of objects are retrieved as search results. 
> Note that the fixes are backward compatible. The end result remains the same. 
> Only the overwork to load unnecessary fields is avoided.
> Sample Query: 'from hive_db as h select h'
> Result:
> rows":[
> {
>   "$typeName$":"__tempQueryResultStruct2",
>   "id":{
> "id":"8159ee38-ec29-4d9a-845a-86fe17ab6bdb",
> "$typeName$":"hive_db",
> "version":0,
> "state":"ACTIVE"
>   }
> },
> {
>   "$typeName$":"__tempQueryResultStruct2",
>   "id":{
> "id":"33016845-4b71-4d56-b131-b48ea38e5507",
> "$typeName$":"hive_db",
> "version":0,
> "state":"ACTIVE"
>   }
> },
> {
>   "$typeName$":"__tempQueryResultStruct2",
>   "id":{
> "id":"b6fb9c53-680e-4be7-b143-f8d9355c5726",
> "$typeName$":"hive_db",
> "version":0,
> "state":"ACTIVE"
>   }
> }
>   ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-1379) Avoid object query overhead when report query selects class type alias

[Neeru Gupta (JIRA)]

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

Neeru Gupta updated ATLAS-1379:
---
Flags: Patch

> Avoid object query overhead when report query selects class type alias
> --
>
> Key: ATLAS-1379
> URL: https://issues.apache.org/jira/browse/ATLAS-1379
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Neeru Gupta
>Assignee: Neeru Gupta
>  Labels: performance
> Fix For: 0.8-incubating
>
> Attachments: rb54759.patch
>
>
> When the DSL query is selecting the class alias, which causes Atlas to run an 
> object query. Atlas should detect this query construct and avoid the overhead 
> of full entity retrieval, when the entity ends up being serialized as an 
> structure that just contains the guid, type, and status.
> For queries like: 'from hive_db  as h select h', even though the end result 
> only contains id object, Atlas code initially loads the entire object with 
> all its properties and while serializing it ends up serializing only the id 
> part. This bug is to avoid the overhead of loading the entire object when 
> fields other than id will be discarded anyways. This added a lot of overhead 
> and was identified as hotspot in our internal testing. This is specially 
> relevant when large number of objects are retrieved as search results. 
> Note that the fixes are backward compatible. The end result remains the same. 
> Only the overwork to load unnecessary fields is avoided.
> Sample Query: 'from hive_db as h select h'
> Result:
> rows":[
> {
>   "$typeName$":"__tempQueryResultStruct2",
>   "id":{
> "id":"8159ee38-ec29-4d9a-845a-86fe17ab6bdb",
> "$typeName$":"hive_db",
> "version":0,
> "state":"ACTIVE"
>   }
> },
> {
>   "$typeName$":"__tempQueryResultStruct2",
>   "id":{
> "id":"33016845-4b71-4d56-b131-b48ea38e5507",
> "$typeName$":"hive_db",
> "version":0,
> "state":"ACTIVE"
>   }
> },
> {
>   "$typeName$":"__tempQueryResultStruct2",
>   "id":{
> "id":"b6fb9c53-680e-4be7-b143-f8d9355c5726",
> "$typeName$":"hive_db",
> "version":0,
> "state":"ACTIVE"
>   }
> }
>   ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-1379) Avoid object query overhead when report query selects class type alias

[Neeru Gupta (JIRA)]

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

Neeru Gupta updated ATLAS-1379:
---
External issue URL: https://reviews.apache.org/r/54759/

https://reviews.apache.org/r/54759/

> Avoid object query overhead when report query selects class type alias
> --
>
> Key: ATLAS-1379
> URL: https://issues.apache.org/jira/browse/ATLAS-1379
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Neeru Gupta
>Assignee: Neeru Gupta
>  Labels: performance
> Fix For: 0.8-incubating
>
>
> When the DSL query is selecting the class alias, which causes Atlas to run an 
> object query. Atlas should detect this query construct and avoid the overhead 
> of full entity retrieval, when the entity ends up being serialized as an 
> structure that just contains the guid, type, and status.
> For queries like: 'from hive_db  as h select h', even though the end result 
> only contains id object, Atlas code initially loads the entire object with 
> all its properties and while serializing it ends up serializing only the id 
> part. This bug is to avoid the overhead of loading the entire object when 
> fields other than id will be discarded anyways. This added a lot of overhead 
> and was identified as hotspot in our internal testing. This is specially 
> relevant when large number of objects are retrieved as search results. 
> Note that the fixes are backward compatible. The end result remains the same. 
> Only the overwork to load unnecessary fields is avoided.
> Sample Query: 'from hive_db as h select h'
> Result:
> rows":[
> {
>   "$typeName$":"__tempQueryResultStruct2",
>   "id":{
> "id":"8159ee38-ec29-4d9a-845a-86fe17ab6bdb",
> "$typeName$":"hive_db",
> "version":0,
> "state":"ACTIVE"
>   }
> },
> {
>   "$typeName$":"__tempQueryResultStruct2",
>   "id":{
> "id":"33016845-4b71-4d56-b131-b48ea38e5507",
> "$typeName$":"hive_db",
> "version":0,
> "state":"ACTIVE"
>   }
> },
> {
>   "$typeName$":"__tempQueryResultStruct2",
>   "id":{
> "id":"b6fb9c53-680e-4be7-b143-f8d9355c5726",
> "$typeName$":"hive_db",
> "version":0,
> "state":"ACTIVE"
>   }
> }
>   ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (ATLAS-1379) Avoid object query overhead when report query selects class type alias

[Neeru Gupta (JIRA)]

Neeru Gupta created ATLAS-1379:
--

 Summary: Avoid object query overhead when report query selects 
class type alias
 Key: ATLAS-1379
 URL: https://issues.apache.org/jira/browse/ATLAS-1379
 Project: Atlas
  Issue Type: Improvement
Reporter: Neeru Gupta
Assignee: Neeru Gupta
 Fix For: 0.8-incubating


When the DSL query is selecting the class alias, which causes Atlas to run an 
object query. Atlas should detect this query construct and avoid the overhead 
of full entity retrieval, when the entity ends up being serialized as an 
structure that just contains the guid, type, and status.

For queries like: 'from hive_db  as h select h', even though the end result 
only contains id object, Atlas code initially loads the entire object with all 
its properties and while serializing it ends up serializing only the id part. 
This bug is to avoid the overhead of loading the entire object when fields 
other than id will be discarded anyways. This added a lot of overhead and was 
identified as hotspot in our internal testing. This is specially relevant when 
large number of objects are retrieved as search results. 

Note that the fixes are backward compatible. The end result remains the same. 
Only the overwork to load unnecessary fields is avoided.


Sample Query: 'from hive_db as h select h'

Result:

rows":[
{
  "$typeName$":"__tempQueryResultStruct2",
  "id":{
"id":"8159ee38-ec29-4d9a-845a-86fe17ab6bdb",
"$typeName$":"hive_db",
"version":0,
"state":"ACTIVE"
  }
},
{
  "$typeName$":"__tempQueryResultStruct2",
  "id":{
"id":"33016845-4b71-4d56-b131-b48ea38e5507",
"$typeName$":"hive_db",
"version":0,
"state":"ACTIVE"
  }
},
{
  "$typeName$":"__tempQueryResultStruct2",
  "id":{
"id":"b6fb9c53-680e-4be7-b143-f8d9355c5726",
"$typeName$":"hive_db",
"version":0,
"state":"ACTIVE"
  }
}
  ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-1277) Add feather use 'order by ' in the DSL search

[Neeru Gupta (JIRA)]

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

Neeru Gupta commented on ATLAS-1277:


There are some white space changes around line 66 which should be fixed. 

Other than that changes look fine. 

+1

> Add  feather use 'order by ' in the DSL search 
> ---
>
> Key: ATLAS-1277
> URL: https://issues.apache.org/jira/browse/ATLAS-1277
> Project: Atlas
>  Issue Type: New Feature
>Affects Versions: 0.8-incubating
>Reporter: Qiang Zhang
>Assignee: Qiang Zhang
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1277.patch
>
>
> in the Search using DSL,sort with 'orderby' ,but with :'order by ' is  a more 
> customary way ,so consider add the 'order by '  is more desirable.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (ATLAS-1284) Fix order by clause to be able to order on super type attributes and with alias.

[Neeru Gupta (JIRA)]

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

Neeru Gupta edited comment on ATLAS-1284 at 12/1/16 5:32 PM:
-

[~shwetaag] I double checked and found that queries like you mentioned still 
does not work.  But queries like following work. 

from src as s select s.name orderby s.name 

I debugged the scala code and found the issue. Basically we apply the order by 
clause before select clause. So orderby clause does not have information about 
select clause and alias. Please look at generated gremlin below for a similar 
query. Please let me know if you think, I should spend time on ATLAS-1007. 

  "gremlin": "import java.util.function.Function;import static 
org.apache.tinkerpop.gremlin.process.traversal.P.*;def g = 
graph.traversal();L:{def _var_0 = [] as Set;g.V().has(\"__typeName\", 
\"OMAS_OMRSAsset\").fill(_var_0);g.V().has(\"__superTypeNames\", 
\"OMAS_OMRSAsset\").fill(_var_0);(_var_0.isEmpty() ? g.V('') : g.V(_var_0 as 
Object[])).has('__is_graphdb_vertex',eq(true)).order().by({((String)property(\"OMAS_OMRSCommonObject.name\").orElse(null))}
 as Function,{ a,b -> (a.toString().toLowerCase()) <=> 
(b.toString().toLowerCase()) 
}).as(\"_src1\").select(\"_src1\").by({[((String)((it as Vertex[]) as 
List).last().property(\"OMAS_OMRSCommonObject.name\").orElse(null))]} 
as Function).toList()}",



was (Author: guptaneeru):
[~shwetaag] I double checked and found that queries like you mentioned still 
does not work.  But queries like following work. 

from src as s select s.name orderby s.name 

I debugged the scala code and found the issue. Basically we apply the order by 
clause before select clause. So orderby clause does not have information about 
select clause and alias. Please look at generate gremlin below for a similar 
query. Please let me know if you think, I should spend time on ATLAS-1007. 

  "gremlin": "import java.util.function.Function;import static 
org.apache.tinkerpop.gremlin.process.traversal.P.*;def g = 
graph.traversal();L:{def _var_0 = [] as Set;g.V().has(\"__typeName\", 
\"OMAS_OMRSAsset\").fill(_var_0);g.V().has(\"__superTypeNames\", 
\"OMAS_OMRSAsset\").fill(_var_0);(_var_0.isEmpty() ? g.V('') : g.V(_var_0 as 
Object[])).has('__is_graphdb_vertex',eq(true)).order().by({((String)property(\"OMAS_OMRSCommonObject.name\").orElse(null))}
 as Function,{ a,b -> (a.toString().toLowerCase()) <=> 
(b.toString().toLowerCase()) 
}).as(\"_src1\").select(\"_src1\").by({[((String)((it as Vertex[]) as 
List).last().property(\"OMAS_OMRSCommonObject.name\").orElse(null))]} 
as Function).toList()}",


> Fix order by clause to be able to order on super type attributes and with 
> alias.
> 
>
> Key: ATLAS-1284
> URL: https://issues.apache.org/jira/browse/ATLAS-1284
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Neeru Gupta
>Assignee: Neeru Gupta
>
> Noticed issues with order by to work with alias and while sorting on super 
> type attributes. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (ATLAS-1284) Fix order by clause to be able to order on super type attributes and with alias.

[Neeru Gupta (JIRA)]

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

Neeru Gupta edited comment on ATLAS-1284 at 12/1/16 5:31 PM:
-

[~shwetaag] I double checked and found that queries like you mentioned still 
does not work.  But queries like following work. 

from src as s select s.name orderby s.name 

I debugged the scala code and found the issue. Basically we apply the order by 
clause before select clause. So orderby clause does not have information about 
select clause and alias. Please look at generate gremlin below for a similar 
query. Please let me know if you think, I should spend time on ATLAS-1007. 

  "gremlin": "import java.util.function.Function;import static 
org.apache.tinkerpop.gremlin.process.traversal.P.*;def g = 
graph.traversal();L:{def _var_0 = [] as Set;g.V().has(\"__typeName\", 
\"OMAS_OMRSAsset\").fill(_var_0);g.V().has(\"__superTypeNames\", 
\"OMAS_OMRSAsset\").fill(_var_0);(_var_0.isEmpty() ? g.V('') : g.V(_var_0 as 
Object[])).has('__is_graphdb_vertex',eq(true)).order().by({((String)property(\"OMAS_OMRSCommonObject.name\").orElse(null))}
 as Function,{ a,b -> (a.toString().toLowerCase()) <=> 
(b.toString().toLowerCase()) 
}).as(\"_src1\").select(\"_src1\").by({[((String)((it as Vertex[]) as 
List).last().property(\"OMAS_OMRSCommonObject.name\").orElse(null))]} 
as Function).toList()}",



was (Author: guptaneeru):
[~shwetaag] I double checked and found that queries like you mentioned still 
does not work.  But queries like following works. 

from src as s select s.name orderby s.name 

I debugged the scala code and found the issue. Basically we apply the order by 
clause before select clause. So orderby clause does not have information about 
select clause and alias. Please look at generate gremlin below for a similar 
query. Please let me know if you think, I should spend time on ATLAS-1007. 

  "gremlin": "import java.util.function.Function;import static 
org.apache.tinkerpop.gremlin.process.traversal.P.*;def g = 
graph.traversal();L:{def _var_0 = [] as Set;g.V().has(\"__typeName\", 
\"OMAS_OMRSAsset\").fill(_var_0);g.V().has(\"__superTypeNames\", 
\"OMAS_OMRSAsset\").fill(_var_0);(_var_0.isEmpty() ? g.V('') : g.V(_var_0 as 
Object[])).has('__is_graphdb_vertex',eq(true)).order().by({((String)property(\"OMAS_OMRSCommonObject.name\").orElse(null))}
 as Function,{ a,b -> (a.toString().toLowerCase()) <=> 
(b.toString().toLowerCase()) 
}).as(\"_src1\").select(\"_src1\").by({[((String)((it as Vertex[]) as 
List).last().property(\"OMAS_OMRSCommonObject.name\").orElse(null))]} 
as Function).toList()}",


> Fix order by clause to be able to order on super type attributes and with 
> alias.
> 
>
> Key: ATLAS-1284
> URL: https://issues.apache.org/jira/browse/ATLAS-1284
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Neeru Gupta
>Assignee: Neeru Gupta
>
> Noticed issues with order by to work with alias and while sorting on super 
> type attributes. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (ATLAS-1284) Fix order by clause to be able to order on super type attributes and with alias.

[Neeru Gupta (JIRA)]

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

Neeru Gupta edited comment on ATLAS-1284 at 11/30/16 4:27 PM:
--

[~shwetaag] I double checked and found that queries like you mentioned still 
does not work.  But queries like following works. 

from src as s select s.name orderby s.name 

I debugged the scala code and found the issue. Basically we apply the order by 
clause before select clause. So orderby clause does not have information about 
select clause and alias. Please look at generate gremlin below for a similar 
query. Please let me know if you think, I should spend time on ATLAS-1007. 

  "gremlin": "import java.util.function.Function;import static 
org.apache.tinkerpop.gremlin.process.traversal.P.*;def g = 
graph.traversal();L:{def _var_0 = [] as Set;g.V().has(\"__typeName\", 
\"OMAS_OMRSAsset\").fill(_var_0);g.V().has(\"__superTypeNames\", 
\"OMAS_OMRSAsset\").fill(_var_0);(_var_0.isEmpty() ? g.V('') : g.V(_var_0 as 
Object[])).has('__is_graphdb_vertex',eq(true)).order().by({((String)property(\"OMAS_OMRSCommonObject.name\").orElse(null))}
 as Function,{ a,b -> (a.toString().toLowerCase()) <=> 
(b.toString().toLowerCase()) 
}).as(\"_src1\").select(\"_src1\").by({[((String)((it as Vertex[]) as 
List).last().property(\"OMAS_OMRSCommonObject.name\").orElse(null))]} 
as Function).toList()}",



was (Author: guptaneeru):
[~shwetaag] I double checked and found that queries like you mentioned still 
does not work.  But queries like following works. 

from src as s select s.name orderby s.name 

I debugged the scala code and found the issue. Basically we apply the order by 
clause before select clause. So orderby clause does not have information about 
select clause and alias. Please look at generate gremlin below. Please let me 
know if you think, I should spend time on ATLAS-1007. 

  "gremlin": "import java.util.function.Function;import static 
org.apache.tinkerpop.gremlin.process.traversal.P.*;def g = 
graph.traversal();L:{def _var_0 = [] as Set;g.V().has(\"__typeName\", 
\"OMAS_OMRSAsset\").fill(_var_0);g.V().has(\"__superTypeNames\", 
\"OMAS_OMRSAsset\").fill(_var_0);(_var_0.isEmpty() ? g.V('') : g.V(_var_0 as 
Object[])).has('__is_graphdb_vertex',eq(true)).order().by({((String)property(\"OMAS_OMRSCommonObject.name\").orElse(null))}
 as Function,{ a,b -> (a.toString().toLowerCase()) <=> 
(b.toString().toLowerCase()) 
}).as(\"_src1\").select(\"_src1\").by({[((String)((it as Vertex[]) as 
List).last().property(\"OMAS_OMRSCommonObject.name\").orElse(null))]} 
as Function).toList()}",


> Fix order by clause to be able to order on super type attributes and with 
> alias.
> 
>
> Key: ATLAS-1284
> URL: https://issues.apache.org/jira/browse/ATLAS-1284
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Neeru Gupta
>Assignee: Neeru Gupta
>
> Noticed issues with order by to work with alias and while sorting on super 
> type attributes. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-1284) Fix order by clause to be able to order on super type attributes and with alias.

[Neeru Gupta (JIRA)]

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

Neeru Gupta commented on ATLAS-1284:


[~shwetaag] I double checked and found that queries like you mentioned still 
does not work.  But queries like following works. 

from src as s select s.name orderby s.name 

I debugged the scala code and found the issue. Basically we apply the order by 
clause before select clause. So orderby clause does not have information about 
select clause and alias. Please look at generate gremlin below. Please let me 
know if you think, I should spend time on ATLAS-1007. 

  "gremlin": "import java.util.function.Function;import static 
org.apache.tinkerpop.gremlin.process.traversal.P.*;def g = 
graph.traversal();L:{def _var_0 = [] as Set;g.V().has(\"__typeName\", 
\"OMAS_OMRSAsset\").fill(_var_0);g.V().has(\"__superTypeNames\", 
\"OMAS_OMRSAsset\").fill(_var_0);(_var_0.isEmpty() ? g.V('') : g.V(_var_0 as 
Object[])).has('__is_graphdb_vertex',eq(true)).order().by({((String)property(\"OMAS_OMRSCommonObject.name\").orElse(null))}
 as Function,{ a,b -> (a.toString().toLowerCase()) <=> 
(b.toString().toLowerCase()) 
}).as(\"_src1\").select(\"_src1\").by({[((String)((it as Vertex[]) as 
List).last().property(\"OMAS_OMRSCommonObject.name\").orElse(null))]} 
as Function).toList()}",


> Fix order by clause to be able to order on super type attributes and with 
> alias.
> 
>
> Key: ATLAS-1284
> URL: https://issues.apache.org/jira/browse/ATLAS-1284
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Neeru Gupta
>Assignee: Neeru Gupta
>
> Noticed issues with order by to work with alias and while sorting on super 
> type attributes. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-737) Add support for Sum, Max, Min and count operations with and without group by.

[Neeru Gupta (JIRA)]

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

Neeru Gupta updated ATLAS-737:
--
Description: 
This can be implemented analogously to a "select count *"  in SQL and is more 
relevant given the added ability to paginate a search result.

This also covers adding support for aggregate methods like max, min, count and 
sum with and without group by.

  was:
This can be implemented analogously to a "select count *"  in SQL and is more 
relevant given the added ability to paginate a search result.

Also add support for group by clause with aggregate methods like max, min, 
count and sum.

Summary: Add support for Sum, Max, Min and count operations with and 
without group by.  (was: Ability to retrieve the size of the result of a DSL 
search without having to retrieve the result)

> Add support for Sum, Max, Min and count operations with and without group by.
> -
>
> Key: ATLAS-737
> URL: https://issues.apache.org/jira/browse/ATLAS-737
> Project: Atlas
>  Issue Type: New Feature
>Reporter: CASSIO DOS SANTOS
>Assignee: Neeru Gupta
>
> This can be implemented analogously to a "select count *"  in SQL and is more 
> relevant given the added ability to paginate a search result.
> This also covers adding support for aggregate methods like max, min, count 
> and sum with and without group by.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-737) Add support for Sum, Max, Min and count operations with and without group by.

[Neeru Gupta (JIRA)]

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

Neeru Gupta commented on ATLAS-737:
---

The review request included changes for Atlas-1284 as well.

> Add support for Sum, Max, Min and count operations with and without group by.
> -
>
> Key: ATLAS-737
> URL: https://issues.apache.org/jira/browse/ATLAS-737
> Project: Atlas
>  Issue Type: New Feature
>Reporter: CASSIO DOS SANTOS
>Assignee: Neeru Gupta
>
> This can be implemented analogously to a "select count *"  in SQL and is more 
> relevant given the added ability to paginate a search result.
> This also covers adding support for aggregate methods like max, min, count 
> and sum with and without group by.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-737) Ability to retrieve the size of the result of a DSL search without having to retrieve the result

[Neeru Gupta (JIRA)]

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

Neeru Gupta updated ATLAS-737:
--
External issue URL:   (was: https://reviews.apache.org/r/53653/)

> Ability to retrieve the size of the result of a DSL search without having to 
> retrieve the result
> 
>
> Key: ATLAS-737
> URL: https://issues.apache.org/jira/browse/ATLAS-737
> Project: Atlas
>  Issue Type: New Feature
>Reporter: CASSIO DOS SANTOS
>Assignee: Neeru Gupta
>
> This can be implemented analogously to a "select count *"  in SQL and is more 
> relevant given the added ability to paginate a search result.
> Also add support for group by clause with aggregate methods like max, min, 
> count and sum.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-737) Ability to retrieve the size of the result of a DSL search without having to retrieve the result

[Neeru Gupta (JIRA)]

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

Neeru Gupta updated ATLAS-737:
--
External issue URL: https://reviews.apache.org/r/53653/

https://reviews.apache.org/r/53653/ review request contains additional changes 
for group by support with sum, max, min and count functions.

> Ability to retrieve the size of the result of a DSL search without having to 
> retrieve the result
> 
>
> Key: ATLAS-737
> URL: https://issues.apache.org/jira/browse/ATLAS-737
> Project: Atlas
>  Issue Type: New Feature
>Reporter: CASSIO DOS SANTOS
>Assignee: Neeru Gupta
>
> This can be implemented analogously to a "select count *"  in SQL and is more 
> relevant given the added ability to paginate a search result.
> Also add support for group by clause with aggregate methods like max, min, 
> count and sum.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-737) Ability to retrieve the size of the result of a DSL search without having to retrieve the result

[Neeru Gupta (JIRA)]

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

Neeru Gupta updated ATLAS-737:
--
Attachment: (was: rb50311.patch)

> Ability to retrieve the size of the result of a DSL search without having to 
> retrieve the result
> 
>
> Key: ATLAS-737
> URL: https://issues.apache.org/jira/browse/ATLAS-737
> Project: Atlas
>  Issue Type: New Feature
>Reporter: CASSIO DOS SANTOS
>Assignee: Neeru Gupta
>
> This can be implemented analogously to a "select count *"  in SQL and is more 
> relevant given the added ability to paginate a search result.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-727) Enhance Atlas client to add support for offset while searching.

[Neeru Gupta (JIRA)]

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

Neeru Gupta commented on ATLAS-727:
---

[~shwethags] I apologize, I had missed your message. I think this issue can be 
resolved as you have added support in query params in rest client. Please 
either resolve it or let me know if it still needs to be addressed.

> Enhance Atlas client to add support for offset while searching.
> ---
>
> Key: ATLAS-727
> URL: https://issues.apache.org/jira/browse/ATLAS-727
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Neeru Gupta
>Assignee: Neeru Gupta
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (ATLAS-1284) Fix order by clause to be able to order on super type attributes and with alias.

[Neeru Gupta (JIRA)]

Neeru Gupta created ATLAS-1284:
--

 Summary: Fix order by clause to be able to order on super type 
attributes and with alias.
 Key: ATLAS-1284
 URL: https://issues.apache.org/jira/browse/ATLAS-1284
 Project: Atlas
  Issue Type: Bug
Affects Versions: 0.7-incubating
Reporter: Neeru Gupta
Assignee: Neeru Gupta


Noticed issues with order by to work with alias and while sorting on super type 
attributes. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (ATLAS-1109) Add ability to search on Map and Array properties for an entity

[Neeru Gupta (JIRA)]

Neeru Gupta created ATLAS-1109:
--

 Summary: Add ability to search on Map and Array properties for an 
entity
 Key: ATLAS-1109
 URL: https://issues.apache.org/jira/browse/ATLAS-1109
 Project: Atlas
  Issue Type: Bug
Reporter: Neeru Gupta






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-1085) With more than 15K classes defined in the types system - Atlas startup fails with "org.apache.atlas.typesystem.exception.TypeExistsException" when restoring type system

[Neeru Gupta (JIRA)]

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

Neeru Gupta commented on ATLAS-1085:


Atlas tries to load all the data from store on startup. This can definitely 
pose a problem. Atlas should leverage the StoreBackedCache implemented by 
[~dkantor] and lazily load types. 
In addition to that, all the loading happens during initialization of services. 
Which is a wrong design. There is another enhancement request related to it:

https://issues.apache.org/jira/browse/ATLAS-1037

> With more than 15K classes defined in the types system - Atlas startup fails 
> with "org.apache.atlas.typesystem.exception.TypeExistsException" when 
> restoring type system - same type is stored more than one time in the store.
> ---
>
> Key: ATLAS-1085
> URL: https://issues.apache.org/jira/browse/ATLAS-1085
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Ayub Khan
> Attachments: application.log
>
>
> Steps to reproduce:
> * Create around 15K classes in the type system.
> * Restart atlas to make sure all the classes are loaded properly
> *Build: HDP-2.5.0.0-1114*
> Attaching application log.
> *Expected behavior: Atlas should make sure all the class types are unique 
> before writing to backend store.*
> Exception snapshot from the logs:
> {noformat}
> 2016-08-03 09:49:47,979 WARN  - [main:] ~ Failed startup of context 
> o.e.j.w.WebAppContext@a47b029{/,file:/grid/0/hdp/2.5.0.0-1114/atlas/server/webapp/atlas/,STARTING}{/usr/hdp/current/atlas-server/server/webapp/atlas}
>  (WebAppContext:514)
> com.google.inject.CreationException: Unable to create injector, see the 
> following errors:
> 1) Error injecting constructor, 
> org.apache.atlas.typesystem.exception.TypeExistsException: Cannot redefine 
> type className_update_rand_090750377
>   at 
> org.apache.atlas.services.DefaultMetadataService.(DefaultMetadataService.java:117)
>   at 
> org.apache.atlas.services.DefaultMetadataService.class(DefaultMetadataService.java:93)
>   while locating org.apache.atlas.services.DefaultMetadataService
>   at 
> org.apache.atlas.RepositoryMetadataModule.configure(RepositoryMetadataModule.java:83)
>   while locating org.apache.atlas.services.MetadataService
> 1 error
>   at 
> com.google.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.java:466)
>   at 
> com.google.inject.internal.InternalInjectorCreator.injectDynamically(InternalInjectorCreator.java:184)
>   at 
> com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:110)
>   at com.google.inject.Guice.createInjector(Guice.java:96)
>   at com.google.inject.Guice.createInjector(Guice.java:73)
>   at com.google.inject.Guice.createInjector(Guice.java:62)
>   at 
> org.apache.atlas.web.listeners.GuiceServletConfig.getInjector(GuiceServletConfig.java:78)
>   at 
> com.google.inject.servlet.GuiceServletContextListener.contextInitialized(GuiceServletContextListener.java:47)
>   at 
> org.apache.atlas.web.listeners.GuiceServletConfig.contextInitialized(GuiceServletConfig.java:132)
>   at 
> org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:800)
>   at 
> org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:444)
>   at 
> org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:791)
>   at 
> org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:294)
>   at 
> org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1349)
>   at 
> org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1342)
>   at 
> org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:741)
>   at 
> org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:505)
>   at 
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
>   at 
> org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
>   at org.eclipse.jetty.server.Server.start(Server.java:387)
>   at 
> org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
>   at 
> org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
>   at org.eclipse.jetty.server.Server.doStart(Server.java:354)
>   at 
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
>   at 
> 

[jira] [Commented] (ATLAS-737) Ability to retrieve the size of the result of a DSL search without having to retrieve the result

[Neeru Gupta (JIRA)]

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

Neeru Gupta commented on ATLAS-737:
---

No, it wont work.  It will throw invalid expression error.  as the query parser 
syntax is  fromsrc ~ select count()

I  will also update the search.twiki with additional syntax.

> Ability to retrieve the size of the result of a DSL search without having to 
> retrieve the result
> 
>
> Key: ATLAS-737
> URL: https://issues.apache.org/jira/browse/ATLAS-737
> Project: Atlas
>  Issue Type: New Feature
>Reporter: CASSIO DOS SANTOS
>Assignee: Neeru Gupta
> Attachments: rb50311.patch
>
>
> This can be implemented analogously to a "select count *"  in SQL and is more 
> relevant given the added ability to paginate a search result.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-737) Ability to retrieve the size of the result of a DSL search without having to retrieve the result

[Neeru Gupta (JIRA)]

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

Neeru Gupta commented on ATLAS-737:
---

[~shwethags] comment on review board: Whats the motivation for adding count - 
since the search API supports offset and limit, should the API return count of 
total results available for the query or should the count be exposed in the DSL 
directly? My preference is to expose the count in the search API

 
@guptaneeru: Counts will be used for reporting purpose such that different 
counts can be precalculated and  displayed for queries. Users can then drill 
down and get the actual results. 

[~cassiodossantos] Would you like to explain other scenarios and why it makes 
sense to add count in DSL query.

> Ability to retrieve the size of the result of a DSL search without having to 
> retrieve the result
> 
>
> Key: ATLAS-737
> URL: https://issues.apache.org/jira/browse/ATLAS-737
> Project: Atlas
>  Issue Type: New Feature
>Reporter: CASSIO DOS SANTOS
>Assignee: Neeru Gupta
> Attachments: rb50311.patch
>
>
> This can be implemented analogously to a "select count *"  in SQL and is more 
> relevant given the added ability to paginate a search result.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-737) Ability to retrieve the size of the result of a DSL search without having to retrieve the result

[Neeru Gupta (JIRA)]

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

Neeru Gupta updated ATLAS-737:
--
Attachment: rb50311.patch

> Ability to retrieve the size of the result of a DSL search without having to 
> retrieve the result
> 
>
> Key: ATLAS-737
> URL: https://issues.apache.org/jira/browse/ATLAS-737
> Project: Atlas
>  Issue Type: New Feature
>Reporter: CASSIO DOS SANTOS
> Attachments: rb50311.patch
>
>
> This can be implemented analogously to a "select count *"  in SQL and is more 
> relevant given the added ability to paginate a search result.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (ATLAS-993) If condition in DSL order by clause is not defined then dsl query fails.

[Neeru Gupta (JIRA)]

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

Neeru Gupta edited comment on ATLAS-993 at 7/6/16 6:36 PM:
---

https://reviews.apache.org/r/49717/

Related to last comment by Shwetha in 
https://issues.apache.org/jira/browse/ATLAS-435


was (Author: guptaneeru):
https://reviews.apache.org/r/49717/

> If condition in DSL order by clause is not defined then dsl query fails.
> 
>
> Key: ATLAS-993
> URL: https://issues.apache.org/jira/browse/ATLAS-993
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Neeru Gupta
>Assignee: Neeru Gupta
> Fix For: 0.8-incubating
>
>
> If order by clause query is not defined then DSL query fails saying invalid 
> expression. Query should succeed, results can come back as unsorted.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (ATLAS-435) Add ORDER BY and Limit to search DSL

[Neeru Gupta (JIRA)]

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

Neeru Gupta edited comment on ATLAS-435 at 7/6/16 6:36 PM:
---

I have added a fix to check for null value in order by closure. It is tracked 
in https://issues.apache.org/jira/browse/ATLAS-993 




was (Author: guptaneeru):
I have added a fix to check for null value in order by closure. 

https://reviews.apache.org/r/49717/

> Add ORDER BY and Limit  to search DSL 
> --
>
> Key: ATLAS-435
> URL: https://issues.apache.org/jira/browse/ATLAS-435
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.7-incubating
>Reporter: David Kantor
>Assignee: Neeru Gupta
> Fix For: 0.7-incubating
>
> Attachments: rb45499(2).patch, rb45499(3).patch
>
>
> Add support for Limit and ORDER BY to Atlas search DSL. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-993) If condition in DSL order by clause is not defined then dsl query fails.

[Neeru Gupta (JIRA)]

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

Neeru Gupta commented on ATLAS-993:
---

https://reviews.apache.org/r/49717/

> If condition in DSL order by clause is not defined then dsl query fails.
> 
>
> Key: ATLAS-993
> URL: https://issues.apache.org/jira/browse/ATLAS-993
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Neeru Gupta
>Assignee: Neeru Gupta
> Fix For: 0.8-incubating
>
>
> If order by clause query is not defined then DSL query fails saying invalid 
> expression. Query should succeed, results can come back as unsorted.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (ATLAS-993) If condition in DSL order by clause is not defined then dsl query fails.

[Neeru Gupta (JIRA)]

Neeru Gupta created ATLAS-993:
-

 Summary: If condition in DSL order by clause is not defined then 
dsl query fails.
 Key: ATLAS-993
 URL: https://issues.apache.org/jira/browse/ATLAS-993
 Project: Atlas
  Issue Type: Bug
Affects Versions: 0.7-incubating
Reporter: Neeru Gupta
Assignee: Neeru Gupta
 Fix For: 0.8-incubating


If order by clause query is not defined then DSL query fails saying invalid 
expression. Query should succeed, results can come back as unsorted.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-435) Add ORDER BY and Limit to search DSL

[Neeru Gupta (JIRA)]

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

Neeru Gupta commented on ATLAS-435:
---

I have added a fix to check for null value in order by closure. 

https://reviews.apache.org/r/49717/

> Add ORDER BY and Limit  to search DSL 
> --
>
> Key: ATLAS-435
> URL: https://issues.apache.org/jira/browse/ATLAS-435
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.7-incubating
>Reporter: David Kantor
>Assignee: Neeru Gupta
> Fix For: 0.7-incubating
>
> Attachments: rb45499(2).patch, rb45499(3).patch
>
>
> Add support for Limit and ORDER BY to Atlas search DSL. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-435) Add ORDER BY and Limit to search DSL

[Neeru Gupta (JIRA)]

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

Neeru Gupta commented on ATLAS-435:
---

[~shwethags] Hi Shwetha, Can you please create a jira issue describing the 
issue with .toLowerCase so that I can add fix and provide patch for it.


Thanks
Neeru

> Add ORDER BY and Limit  to search DSL 
> --
>
> Key: ATLAS-435
> URL: https://issues.apache.org/jira/browse/ATLAS-435
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.7-incubating
>Reporter: David Kantor
>Assignee: Neeru Gupta
> Fix For: 0.7-incubating
>
> Attachments: rb45499(2).patch, rb45499(3).patch
>
>
> Add support for Limit and ORDER BY to Atlas search DSL. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (ATLAS-872) Add Multitenancy support to Atlas

[Neeru Gupta (JIRA)]

Neeru Gupta created ATLAS-872:
-

 Summary: Add Multitenancy support to Atlas
 Key: ATLAS-872
 URL: https://issues.apache.org/jira/browse/ATLAS-872
 Project: Atlas
  Issue Type: Improvement
Affects Versions: 0.7-incubating
Reporter: Neeru Gupta
Assignee: Neeru Gupta
 Fix For: trunk


Atlas currently does not support multi tenancy.  As part of this feature, will 
add support to honor requests coming from multiple tenants. Individual Tenant 
data should remain isolated from one another. 

All the unique constraints should be applied per tenant and not globally. 




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-435) Add ORDER BY and Limit to search DSL

[Neeru Gupta (JIRA)]

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

Neeru Gupta commented on ATLAS-435:
---

[~suma.shivaprasad] As part of submitted patch search.twiki was updated to show 
DSL related changes. Noticed that http://atlas.incubator.apache.org/Search.html 
does not reflect the same. What are the additional steps to update the public 
facing wiki. 

> Add ORDER BY and Limit  to search DSL 
> --
>
> Key: ATLAS-435
> URL: https://issues.apache.org/jira/browse/ATLAS-435
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.7-incubating
>Reporter: David Kantor
>Assignee: Neeru Gupta
> Fix For: 0.7-incubating
>
> Attachments: rb45499(2).patch, rb45499(3).patch
>
>
> Add support for Limit and ORDER BY to Atlas search DSL. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-723) JSON deserialization regression

[Neeru Gupta (JIRA)]

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

Neeru Gupta updated ATLAS-723:
--
Attachment: rb46849.patch

Attaching patch from review board https://reviews.apache.org/r/46849/

> JSON deserialization regression
> ---
>
> Key: ATLAS-723
> URL: https://issues.apache.org/jira/browse/ATLAS-723
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Jeffrey Hagelberg
>Assignee: Neeru Gupta
>Priority: Blocker
> Attachments: InstanceSerializationTest.scala, rb46849.patch
>
>
> Some json that could be deserialized prior to the implementation of soft 
> delete can no longer be deserialized.  This seems to be related to the 
> addition of the "state" field in the id.  Furthermore, it seems to be 
> restricted to cases where the object has an array reference.
> Here's an example of a JSON object whose deserialization now fails:
> {noformat}
>  {
> "jsonClass": 
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
> "id": {
> "jsonClass": 
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "id": "6765f7c6-cc11-4575-8c13-8bab9b3d86a2",
> "version": 0,
> "typeName": "LoadProcess"
> },
> "typeName": "LoadProcess",
> "values": {
> "inputTables": [{
> "jsonClass": 
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "id": "bacfa996-e88e-4d7e-9630-68c9829b10b4",
> "version": 0,
> "typeName": "Table"
> }, {
> "jsonClass": 
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "id": "6da06805-3f56-446f-8831-672a65ac2199",
> "version": 0,
> "typeName": "Table"
> }
> ],
> "outputTable": {
> "jsonClass": 
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "id": "d5c3d6d0-aa10-44c1-b05d-ed9400d2a5ac",
> "version": 0,
> "typeName": "Table"
> },
> "name": "loadSalesDaily"
> },
> "traitNames": [
> "ETL"
> ],
> "traits": {
> "ETL": {
> "jsonClass": 
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct",
> "typeName": "ETL",
> "values": {
> }
> }
> }
> }
> {noformat}
> (Note that this depends on the referenced Table objects having been 
> previously saved into Atlas)
> I spent some time debugging this today, it seems to be a regression in the 
> InstanceSerialization class.  It seems to be related to 
> InstanceJavaConversion.state and InstanceJavaConversion.convertId



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Issue Comment Deleted] (ATLAS-723) JSON deserialization regression

[Neeru Gupta (JIRA)]

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

Neeru Gupta updated ATLAS-723:
--
Comment: was deleted

(was: org.apache.atlas.typesystem.types.ValueConversionException: Cannot 
convert value 'org.apache.atlas.typesystem.Struct@71ae6bd6' to datatype PII
at 
org.apache.atlas.typesystem.types.TypedStructHandler.convert(TypedStructHandler.java:57)
at 
org.apache.atlas.typesystem.types.TraitType.convert(TraitType.java:58)
at 
org.apache.atlas.typesystem.types.ClassType.createInstanceWithTraits(ClassType.java:184)
at 
org.apache.atlas.typesystem.types.ClassType.convert(ClassType.java:124)
at 
org.apache.atlas.services.DefaultMetadataService.deserializeClassInstances(DefaultMetadataService.java:339)
at 
org.apache.atlas.services.DefaultMetadataService.createEntities(DefaultMetadataService.java:313)
at 
org.apache.atlas.service.DefaultMetadataServiceTest.createInstance(DefaultMetadataServiceTest.java:200))

> JSON deserialization regression
> ---
>
> Key: ATLAS-723
> URL: https://issues.apache.org/jira/browse/ATLAS-723
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Jeffrey Hagelberg
>Assignee: Neeru Gupta
>Priority: Blocker
>
> Some json that could be deserialized prior to the implementation of soft 
> delete can no longer be deserialized.  This seems to be related to the 
> addition of the "state" field in the id.  Furthermore, it seems to be 
> restricted to cases where the object has an array reference.
> Here's an example of a JSON object whose deserialization now fails:
> {noformat}
>  {
> "jsonClass": 
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
> "id": {
> "jsonClass": 
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "id": "6765f7c6-cc11-4575-8c13-8bab9b3d86a2",
> "version": 0,
> "typeName": "LoadProcess"
> },
> "typeName": "LoadProcess",
> "values": {
> "inputTables": [{
> "jsonClass": 
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "id": "bacfa996-e88e-4d7e-9630-68c9829b10b4",
> "version": 0,
> "typeName": "Table"
> }, {
> "jsonClass": 
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "id": "6da06805-3f56-446f-8831-672a65ac2199",
> "version": 0,
> "typeName": "Table"
> }
> ],
> "outputTable": {
> "jsonClass": 
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "id": "d5c3d6d0-aa10-44c1-b05d-ed9400d2a5ac",
> "version": 0,
> "typeName": "Table"
> },
> "name": "loadSalesDaily"
> },
> "traitNames": [
> "ETL"
> ],
> "traits": {
> "ETL": {
> "jsonClass": 
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct",
> "typeName": "ETL",
> "values": {
> }
> }
> }
> }
> {noformat}
> (Note that this depends on the referenced Table objects having been 
> previously saved into Atlas)
> I spent some time debugging this today, it seems to be a regression in the 
> InstanceSerialization class.  It seems to be related to 
> InstanceJavaConversion.state and InstanceJavaConversion.convertId



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-723) JSON deserialization regression

[Neeru Gupta (JIRA)]

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

Neeru Gupta commented on ATLAS-723:
---

org.apache.atlas.typesystem.types.ValueConversionException: Cannot convert 
value 'org.apache.atlas.typesystem.Struct@71ae6bd6' to datatype PII
at 
org.apache.atlas.typesystem.types.TypedStructHandler.convert(TypedStructHandler.java:57)
at 
org.apache.atlas.typesystem.types.TraitType.convert(TraitType.java:58)
at 
org.apache.atlas.typesystem.types.ClassType.createInstanceWithTraits(ClassType.java:184)
at 
org.apache.atlas.typesystem.types.ClassType.convert(ClassType.java:124)
at 
org.apache.atlas.services.DefaultMetadataService.deserializeClassInstances(DefaultMetadataService.java:339)
at 
org.apache.atlas.services.DefaultMetadataService.createEntities(DefaultMetadataService.java:313)
at 
org.apache.atlas.service.DefaultMetadataServiceTest.createInstance(DefaultMetadataServiceTest.java:200)

> JSON deserialization regression
> ---
>
> Key: ATLAS-723
> URL: https://issues.apache.org/jira/browse/ATLAS-723
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Jeffrey Hagelberg
>Assignee: Neeru Gupta
>Priority: Blocker
>
> Some json that could be deserialized prior to the implementation of soft 
> delete can no longer be deserialized.  This seems to be related to the 
> addition of the "state" field in the id.  Furthermore, it seems to be 
> restricted to cases where the object has an array reference.
> Here's an example of a JSON object whose deserialization now fails:
> {noformat}
>  {
> "jsonClass": 
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
> "id": {
> "jsonClass": 
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "id": "6765f7c6-cc11-4575-8c13-8bab9b3d86a2",
> "version": 0,
> "typeName": "LoadProcess"
> },
> "typeName": "LoadProcess",
> "values": {
> "inputTables": [{
> "jsonClass": 
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "id": "bacfa996-e88e-4d7e-9630-68c9829b10b4",
> "version": 0,
> "typeName": "Table"
> }, {
> "jsonClass": 
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "id": "6da06805-3f56-446f-8831-672a65ac2199",
> "version": 0,
> "typeName": "Table"
> }
> ],
> "outputTable": {
> "jsonClass": 
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "id": "d5c3d6d0-aa10-44c1-b05d-ed9400d2a5ac",
> "version": 0,
> "typeName": "Table"
> },
> "name": "loadSalesDaily"
> },
> "traitNames": [
> "ETL"
> ],
> "traits": {
> "ETL": {
> "jsonClass": 
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct",
> "typeName": "ETL",
> "values": {
> }
> }
> }
> }
> {noformat}
> (Note that this depends on the referenced Table objects having been 
> previously saved into Atlas)
> I spent some time debugging this today, it seems to be a regression in the 
> InstanceSerialization class.  It seems to be related to 
> InstanceJavaConversion.state and InstanceJavaConversion.convertId



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-727) Enhance Atlas client to add support for offset while searching.

[Neeru Gupta (JIRA)]

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

Neeru Gupta updated ATLAS-727:
--
External issue URL:   (was: https://issues.apache.org/jira/browse/ATLAS-435)

> Enhance Atlas client to add support for offset while searching.
> ---
>
> Key: ATLAS-727
> URL: https://issues.apache.org/jira/browse/ATLAS-727
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Neeru Gupta
>Assignee: Neeru Gupta
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (ATLAS-727) Enhance Atlas client to add support for offset while searching.

[Neeru Gupta (JIRA)]

Neeru Gupta created ATLAS-727:
-

 Summary: Enhance Atlas client to add support for offset while 
searching.
 Key: ATLAS-727
 URL: https://issues.apache.org/jira/browse/ATLAS-727
 Project: Atlas
  Issue Type: Improvement
Reporter: Neeru Gupta
Assignee: Neeru Gupta






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-435) Add ORDER BY and Limit to search DSL

[Neeru Gupta (JIRA)]

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

Neeru Gupta commented on ATLAS-435:
---

[~suma.shivaprasad] I have attached the latest patch after rebasing with 
master. 


> Add ORDER BY and Limit  to search DSL 
> --
>
> Key: ATLAS-435
> URL: https://issues.apache.org/jira/browse/ATLAS-435
> Project: Atlas
>  Issue Type: Improvement
>Reporter: David Kantor
>Assignee: Neeru Gupta
> Attachments: rb45499(2).patch, rb45499(3).patch
>
>
> Add support for Limit and ORDER BY to Atlas search DSL. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-435) Add ORDER BY and Limit to search DSL

[Neeru Gupta (JIRA)]

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

Neeru Gupta updated ATLAS-435:
--
Attachment: rb45499(3).patch

Latest patch after merging with trunk.

> Add ORDER BY and Limit  to search DSL 
> --
>
> Key: ATLAS-435
> URL: https://issues.apache.org/jira/browse/ATLAS-435
> Project: Atlas
>  Issue Type: Improvement
>Reporter: David Kantor
>Assignee: Neeru Gupta
> Attachments: rb45499(2).patch, rb45499(3).patch
>
>
> Add support for Limit and ORDER BY to Atlas search DSL. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-659) atlas_start fails on Windows

[Neeru Gupta (JIRA)]

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

Neeru Gupta commented on ATLAS-659:
---

Below are additional errors while trying to start the atlas server on windows 
related to hbase:


4:52 AM Created latest i.e 26th April atlas payload but it fails with below 
Error: 2016-04-26 04:22:02,077 INFO  - [main:] ~ Initiating client 
connection, connectString=localhost:2181 sessionTimeout=9 
watcher=hconnection-0x8c178dbc0x0, quorum=localhost:2181, baseZNode=/hbase 
(ZooKeeper:438)
2016-04-26 04:22:02,157 INFO  - [main-SendThread(localhost:2181):] ~ Opening 
socket connection to server localhost/127.0.0.1:2181. Will not attempt to 
authenticate using SASL (unknown error) (ClientCnxn:975)
2016-04-26 04:22:02,170 INFO  - [main-SendThread(localhost:2181):] ~ Socket 
connection established to localhost/127.0.0.1:2181, initiating session 
(ClientCnxn:852)

> atlas_start fails on Windows
> 
>
> Key: ATLAS-659
> URL: https://issues.apache.org/jira/browse/ATLAS-659
> Project: Atlas
>  Issue Type: Bug
>Reporter: David Kantor
>Assignee: David Kantor
>Priority: Blocker
>
> Recent changes for using HBase as the default storage backend has broken 
> Atlas startup on Windows, which now fails with:
> {noformat}
> Exception: [Error 193] %1 is not a valid Win32 application
> Traceback (most recent call last):
>   File "atlas_start.py", line 113, in 
> returncode = main()
>   File "atlas_start.py", line 68, in main
> mc.run_hbase(mc.hbaseBinDir(atlas_home), "start", hbase_conf_dir, 
> logdir)
>   File 
> "C:\OMS_main1\oms\atlas\distro\target\atlas\distro\target\apache-atlas-0.7-incubating-SNAPSHOT-bin\apache-atlas-0.7-incubating-SNAPSHOT\bin\atlas_config.py",
>  
> line 365, in run_hbase
> return runProcess(cmd, logdir, False, wait)
>   File 
> "C:\OMS_main1\oms\atlas\distro\target\atlas\distro\target\apache-atlas-0.7-incubating-SNAPSHOT-bin\apache-atlas-0.7-incubating-SNAPSHOT\bin\atlas_config.py",
>  line 194, in runProcess
> p = subprocess.Popen(commandline, stdout=stdoutFile, stderr=stderrFile, 
> shell=shell)
>   File "C:\Python27\lib\subprocess.py", line 710, in __init__
> errread, errwrite)
>   File "C:\Python27\lib\subprocess.py", line 958, in _execute_child
> startupinfo)
> WindowsError: [Error 193] %1 is not a valid Win32 application
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-435) Add ORDER BY and Limit to search DSL

[Neeru Gupta (JIRA)]

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

Neeru Gupta updated ATLAS-435:
--
Attachment: (was: rb45499(1).patch)

> Add ORDER BY and Limit  to search DSL 
> --
>
> Key: ATLAS-435
> URL: https://issues.apache.org/jira/browse/ATLAS-435
> Project: Atlas
>  Issue Type: Improvement
>Reporter: David Kantor
>Assignee: Neeru Gupta
> Attachments: rb45499(2).patch
>
>
> Add support for Limit and ORDER BY to Atlas search DSL. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-661) REST API Authentication

[Neeru Gupta (JIRA)]

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

Neeru Gupta commented on ATLAS-661:
---

I have noticed that as part of recent changes for Ui authentication, Atlas Ui 
sends password as plain text. Passwords should atleast be Base 64 encrypted. 

> REST API Authentication
> ---
>
> Key: ATLAS-661
> URL: https://issues.apache.org/jira/browse/ATLAS-661
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.7-incubating
>Reporter: Erik Bergenholtz
>Assignee: Nixon Rodrigues
>Priority: Critical
> Fix For: 0.7-incubating
>
>
> Atlas needs to authorize the REST API invocations; as necessary requests will 
> be forced to authenticate.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-435) Add ORDER BY and Limit to search DSL

[Neeru Gupta (JIRA)]

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

Neeru Gupta commented on ATLAS-435:
---

[~suma.shivaprasad] Have addressed your comments in review board. 

> Add ORDER BY and Limit  to search DSL 
> --
>
> Key: ATLAS-435
> URL: https://issues.apache.org/jira/browse/ATLAS-435
> Project: Atlas
>  Issue Type: Improvement
>Reporter: David Kantor
>Assignee: Neeru Gupta
> Attachments: rb45499(1).patch, rb45499(2).patch
>
>
> Add support for Limit and ORDER BY to Atlas search DSL. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-435) Add ORDER BY and Limit to search DSL

[Neeru Gupta (JIRA)]

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

Neeru Gupta updated ATLAS-435:
--
Attachment: rb45499(2).patch

> Add ORDER BY and Limit  to search DSL 
> --
>
> Key: ATLAS-435
> URL: https://issues.apache.org/jira/browse/ATLAS-435
> Project: Atlas
>  Issue Type: Improvement
>Reporter: David Kantor
>Assignee: Neeru Gupta
> Attachments: rb45499(1).patch, rb45499(2).patch
>
>
> Add support for Limit and ORDER BY to Atlas search DSL. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-435) Add ORDER BY and Limit to search DSL

[Neeru Gupta (JIRA)]

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

Neeru Gupta commented on ATLAS-435:
---

[~suma.shivaprasad] I have addressed review board comments and have uploaded 
the patch. Please review and commit if it is good to go. 

Thanks
Neeru

> Add ORDER BY and Limit  to search DSL 
> --
>
> Key: ATLAS-435
> URL: https://issues.apache.org/jira/browse/ATLAS-435
> Project: Atlas
>  Issue Type: Improvement
>Reporter: David Kantor
>Assignee: Neeru Gupta
> Attachments: rb45499(1).patch
>
>
> Add support for Limit and ORDER BY to Atlas search DSL. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-435) Add ORDER BY and Limit to search DSL

[Neeru Gupta (JIRA)]

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

Neeru Gupta updated ATLAS-435:
--
Attachment: rb45499(1).patch

Patch is available for review at https://reviews.apache.org/r/45499/

> Add ORDER BY and Limit  to search DSL 
> --
>
> Key: ATLAS-435
> URL: https://issues.apache.org/jira/browse/ATLAS-435
> Project: Atlas
>  Issue Type: Improvement
>Reporter: David Kantor
>Assignee: Neeru Gupta
> Attachments: rb45499(1).patch
>
>
> Add support for Limit and ORDER BY to Atlas search DSL. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-435) Add ORDER BY and Limit to search DSL

[Neeru Gupta (JIRA)]

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

Neeru Gupta commented on ATLAS-435:
---

Sample query:
 "hive_db where hive_db has name orderby 'hive_db.owner' limit 2 offset 1"
"from hive_table select owner orderby 'hive_table.owner' desc limit 5"
"hive_db where (name = \"Reporting\") select name as _col_0, (createTime + 1) 
as _col_1 orderby '_col_1'"

> Add ORDER BY and Limit  to search DSL 
> --
>
> Key: ATLAS-435
> URL: https://issues.apache.org/jira/browse/ATLAS-435
> Project: Atlas
>  Issue Type: Improvement
>Reporter: David Kantor
>Assignee: Neeru Gupta
>
> Add support for Limit and ORDER BY to Atlas search DSL. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (ATLAS-559) Atlas should allow JSONs to be submitted that don't have optional attributes.

[Neeru Gupta (JIRA)]

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

Neeru Gupta reassigned ATLAS-559:
-

Assignee: Neeru Gupta

> Atlas should allow JSONs to be submitted that don't have optional attributes.
> -
>
> Key: ATLAS-559
> URL: https://issues.apache.org/jira/browse/ATLAS-559
> Project: Atlas
>  Issue Type: Bug
>Reporter: Hemanth Yamijala
>Assignee: Neeru Gupta
> Fix For: 0.7-incubating
>
>
> Currently, attributes which are in principle optional should still be 
> submitted using a null value if one is using the REST API directly. The Java 
> client libraries handle this case for the user, but there are non Java folks 
> using Atlas as well. For them, any optional addition to the types implies 
> they will need to change their code which is super inconvenient. Hence, 
> handling optional attributes is required.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (ATLAS-436) Add LIMIT to search DSL

[Neeru Gupta (JIRA)]

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

Neeru Gupta resolved ATLAS-436.
---
Resolution: Duplicate

Duplicate of ATLAS-435

> Add LIMIT to search DSL
> ---
>
> Key: ATLAS-436
> URL: https://issues.apache.org/jira/browse/ATLAS-436
> Project: Atlas
>  Issue Type: Improvement
>Reporter: David Kantor
>Assignee: Neeru Gupta
>
> Add LIMIT to Atlas search DSL



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-435) Add ORDER BY to search DSL

[Neeru Gupta (JIRA)]

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

Neeru Gupta commented on ATLAS-435:
---

[~suma.shivaprasad] Please review the changes for ATLAS-435 and ATLAS-436 at 
https://reviews.apache.org/r/45499/ . [~dkantor] has mentioned that you are 
familiar with DSL parsing code. Thanks Neeru

> Add ORDER BY to search DSL 
> ---
>
> Key: ATLAS-435
> URL: https://issues.apache.org/jira/browse/ATLAS-435
> Project: Atlas
>  Issue Type: Improvement
>Reporter: David Kantor
>Assignee: Neeru Gupta
>
> Add support for ORDER BY to Atlas search DSL.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-645) FieldMapping.output() results in stack overflow when instances reference each other

[Neeru Gupta (JIRA)]

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

Neeru Gupta commented on ATLAS-645:
---

+1

> FieldMapping.output() results in stack overflow when instances reference each 
> other
> ---
>
> Key: ATLAS-645
> URL: https://issues.apache.org/jira/browse/ATLAS-645
> Project: Atlas
>  Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: David Kantor
> Attachments: rb45948.patch
>
>
> FieldMapping.output() results in a stack overflow due to infinite recursion 
> when two IReferenceableInstance or IStruct objects reference each other.  
> This issue was first exposed by 
> GraphBackedMetadataRepositoryDeleteEntitiesTest.testDisconnectMapReferenceFromClassType().
> {noformat}
> SLF4J: Failed toString() invocation on an object of type 
> [org.apache.atlas.typesystem.persistence.ReferenceableInstance]
> java.lang.StackOverflowError
>   at java.util.regex.Pattern$GroupHead.match(Pattern.java:4556)
>   at java.util.regex.Pattern$Branch.match(Pattern.java:4502)
>   at java.util.regex.Pattern$BranchConn.match(Pattern.java:4466)
>   at java.util.regex.Pattern$GroupTail.match(Pattern.java:4615)
>   at java.util.regex.Pattern$Curly.match0(Pattern.java:4177)
>   at java.util.regex.Pattern$Curly.match(Pattern.java:4132)
>   at java.util.regex.Pattern$GroupHead.match(Pattern.java:4556)
>   at java.util.regex.Pattern$Branch.match(Pattern.java:4502)
>   at java.util.regex.Pattern$Branch.match(Pattern.java:4500)
>   at java.util.regex.Pattern$BmpCharProperty.match(Pattern.java:3715)
>   at java.util.regex.Pattern$Start.match(Pattern.java:3408)
>   at java.util.regex.Matcher.search(Matcher.java:1199)
>   at java.util.regex.Matcher.find(Matcher.java:618)
>   at java.util.Formatter.parse(Formatter.java:2517)
>   at java.util.Formatter.format(Formatter.java:2469)
>   at java.util.Formatter.format(Formatter.java:2423)
>   at java.lang.String.format(String.java:2792)
>   at org.apache.atlas.typesystem.persistence.Id.toString(Id.java:98)
>   at 
> org.apache.atlas.typesystem.types.FieldMapping.output(FieldMapping.java:114)
>   at 
> org.apache.atlas.typesystem.persistence.ReferenceableInstance.toString(ReferenceableInstance.java:92)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (ATLAS-470) update types create a new index with same typename

[Neeru Gupta (JIRA)]

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

Neeru Gupta resolved ATLAS-470.
---
Resolution: Duplicate

Resolved with ATLAS-511

> update types create a new index with same typename
> --
>
> Key: ATLAS-470
> URL: https://issues.apache.org/jira/browse/ATLAS-470
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
> Environment: Sandbox
>Reporter: Chethana
>Assignee: Neeru Gupta
>Priority: Critical
> Attachments: applicationLog_op.txt, rb45043.patch
>
>
> Create a type - 
> POST -  http://localhost:21000/api/atlas/types
>   "enumTypes":[
> 
>   ],
>   "structTypes":[
> 
>   ],
>   "traitTypes":[
> 
>   ],
>   "classTypes":[
> {
>   "superTypes":[
> 
>   ],
>   
> "hierarchicalMetaTypeName":"org.apache.atlas.typesystem.types.ClassType",
>   "typeName":"TypeDefString1",
>   "attributeDefinitions":[
> {
>   "name":"isCompositeFalse",
>   "dataTypeName":"string",
>   "multiplicity":"optional",
>   "isComposite":false,
>   "isUnique":false,
>   "isIndexable":false,
>   "reverseAttributeName":null
> }
>   ]
> }
>   ]
> }
> Update this type
> PUT-
> http://localhost:21000/api/atlas/types
>   "enumTypes":[
> 
>   ],
>   "structTypes":[
> 
>   ],
>   "traitTypes":[
> 
>   ],
>   "classTypes":[
> {
>   "superTypes":[
> 
>   ],
>   
> "hierarchicalMetaTypeName":"org.apache.atlas.typesystem.types.ClassType",
>   "typeName":"TypeDefString1",
>   "attributeDefinitions":[
> {
>   "name":"isCompositeFalse",
>   "dataTypeName":"string",
>   "multiplicity":"optional",
>   "isComposite":false,
>   "isUnique":false,
>   "isIndexable":false,
>   "reverseAttributeName":null
> },
> {
>   "name":"isTestable",
>   "dataTypeName":"boolean",
>   "multiplicity":"optional",
>   "isComposite":false,
>   "isUnique":false,
>   "isIndexable":false,
>   "reverseAttributeName":null
> }
>   ]
> }
>   ]
> }
> actual-
> http://localhost:21000/api/atlas/types?type=CLASS
> {
> "results": [
> "TypeDefString1",
> "TypeDefString1"
> ],
> "count": 60,
> "requestId": "qtp1879648991-299 - 8581163e-cb86-4ef3-af71-ff4495884cb0"
> }
> actual-
> http://localhost:21000/api/atlas/types?type=CLASS
> expected
> {
> "results": [
> "TypeDefString1"
> ],
> "count": 60,
> "requestId": "qtp1879648991-299 - 8581163e-cb86-4ef3-af71-ff4495884cb0"
> }



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-586) While updating the multiple attributes, Atlas returns the response with escape characters.

[Neeru Gupta (JIRA)]

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

Neeru Gupta commented on ATLAS-586:
---

+1

> While updating the multiple attributes, Atlas returns the response with 
> escape characters.
> --
>
> Key: ATLAS-586
> URL: https://issues.apache.org/jira/browse/ATLAS-586
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Ankur Verma
>Assignee: David Kantor
> Fix For: 0.7-incubating
>
> Attachments: rb45542.patch, updateInstances.json
>
>
> When updating an Atlas entity using the PUT operation on the entities 
> resource, Atlas returns the response entity with escape characters in the 
> definition property value, which causes a JsonSyntaxException when using GSON 
> to convert the entity string to a Java object.
> $ curl -X PUT -H "Accept: application/json" -H "Content-Type: 
> application/json" -d @updateInstances.json 
> http://localhost:21000/api/atlas/entities
> {"requestId":"qtp-897180322-29 - 
> 764c42a3-6b94-47dc-825f-85ebb12fa9ea","GUID":["a8101113-52e3-445d-b30f-96b8cfd99c8d"],"definition":"{\n
>  
> \"jsonClass\":\"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference\",\n
>  \"id\":{\n 
> \"jsonClass\":\"org.apache.atlas.typesystem.json.InstanceSerialization$_Id\",\n
>  \"id\":\"a8101113-52e3-445d-b30f-96b8cfd99c8d\",\n \"version\":0,\n 
> \"typeName\":\"UpdateInstancesPackage_Account\"\n },\n 
> \"typeName\":\"UpdateInstancesPackage_Account\",\n \"values\":{\n 
> \"signators\":null,\n \"number\":\"acc1\",\n \"omContainerId\":null,\n 
> \"omDeleted\":false,\n \"omCreatedByUser\":\"oms\",\n 
> \"lastModified\":null,\n \"balance\":5000.0,\n 
> \"omModificationTimestamp\":\"2016-03-22T19:45:05.445Z\",\n 
> \"omOptimisticLockId\":0,\n \"omModifiedByUser\":\"oms\",\n 
> \"omCreationTimestamp\":\"2016-03-22T19:45:05.445Z\",\n \"props\":null,\n 
> \"recentDeposits\":null,\n \"recentDepositAmounts\":null\n },\n 
> \"traitNames\":[\n \n ],\n \"traits\":{\n \n }\n}"}
>  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (ATLAS-435) Add ORDER BY to search DSL

[Neeru Gupta (JIRA)]

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

Neeru Gupta reassigned ATLAS-435:
-

Assignee: Neeru Gupta

> Add ORDER BY to search DSL 
> ---
>
> Key: ATLAS-435
> URL: https://issues.apache.org/jira/browse/ATLAS-435
> Project: Atlas
>  Issue Type: Improvement
>Reporter: David Kantor
>Assignee: Neeru Gupta
>
> Add support for ORDER BY to Atlas search DSL.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-470) update types create a new index with same typename

[Neeru Gupta (JIRA)]

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

Neeru Gupta commented on ATLAS-470:
---

I was able to reproduce the issue and data fixes itself on server restart. 
Because the issue was only in cached data. Please review the changes 
https://reviews.apache.org/r/45043

> update types create a new index with same typename
> --
>
> Key: ATLAS-470
> URL: https://issues.apache.org/jira/browse/ATLAS-470
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
> Environment: Sandbox
>Reporter: Chethana
>Assignee: Neeru Gupta
>Priority: Critical
> Attachments: applicationLog_op.txt, rb45043.patch
>
>
> Create a type - 
> POST -  http://localhost:21000/api/atlas/types
>   "enumTypes":[
> 
>   ],
>   "structTypes":[
> 
>   ],
>   "traitTypes":[
> 
>   ],
>   "classTypes":[
> {
>   "superTypes":[
> 
>   ],
>   
> "hierarchicalMetaTypeName":"org.apache.atlas.typesystem.types.ClassType",
>   "typeName":"TypeDefString1",
>   "attributeDefinitions":[
> {
>   "name":"isCompositeFalse",
>   "dataTypeName":"string",
>   "multiplicity":"optional",
>   "isComposite":false,
>   "isUnique":false,
>   "isIndexable":false,
>   "reverseAttributeName":null
> }
>   ]
> }
>   ]
> }
> Update this type
> PUT-
> http://localhost:21000/api/atlas/types
>   "enumTypes":[
> 
>   ],
>   "structTypes":[
> 
>   ],
>   "traitTypes":[
> 
>   ],
>   "classTypes":[
> {
>   "superTypes":[
> 
>   ],
>   
> "hierarchicalMetaTypeName":"org.apache.atlas.typesystem.types.ClassType",
>   "typeName":"TypeDefString1",
>   "attributeDefinitions":[
> {
>   "name":"isCompositeFalse",
>   "dataTypeName":"string",
>   "multiplicity":"optional",
>   "isComposite":false,
>   "isUnique":false,
>   "isIndexable":false,
>   "reverseAttributeName":null
> },
> {
>   "name":"isTestable",
>   "dataTypeName":"boolean",
>   "multiplicity":"optional",
>   "isComposite":false,
>   "isUnique":false,
>   "isIndexable":false,
>   "reverseAttributeName":null
> }
>   ]
> }
>   ]
> }
> actual-
> http://localhost:21000/api/atlas/types?type=CLASS
> {
> "results": [
> "TypeDefString1",
> "TypeDefString1"
> ],
> "count": 60,
> "requestId": "qtp1879648991-299 - 8581163e-cb86-4ef3-af71-ff4495884cb0"
> }
> actual-
> http://localhost:21000/api/atlas/types?type=CLASS
> expected
> {
> "results": [
> "TypeDefString1"
> ],
> "count": 60,
> "requestId": "qtp1879648991-299 - 8581163e-cb86-4ef3-af71-ff4495884cb0"
> }



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-470) update types create a new index with same typename

[Neeru Gupta (JIRA)]

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

Neeru Gupta updated ATLAS-470:
--
Attachment: rb45043.patch

Attaching the patch from 
https://reviews.apache.org/r/45043

> update types create a new index with same typename
> --
>
> Key: ATLAS-470
> URL: https://issues.apache.org/jira/browse/ATLAS-470
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
> Environment: Sandbox
>Reporter: Chethana
>Assignee: Neeru Gupta
>Priority: Critical
> Attachments: applicationLog_op.txt, rb45043.patch
>
>
> Create a type - 
> POST -  http://localhost:21000/api/atlas/types
>   "enumTypes":[
> 
>   ],
>   "structTypes":[
> 
>   ],
>   "traitTypes":[
> 
>   ],
>   "classTypes":[
> {
>   "superTypes":[
> 
>   ],
>   
> "hierarchicalMetaTypeName":"org.apache.atlas.typesystem.types.ClassType",
>   "typeName":"TypeDefString1",
>   "attributeDefinitions":[
> {
>   "name":"isCompositeFalse",
>   "dataTypeName":"string",
>   "multiplicity":"optional",
>   "isComposite":false,
>   "isUnique":false,
>   "isIndexable":false,
>   "reverseAttributeName":null
> }
>   ]
> }
>   ]
> }
> Update this type
> PUT-
> http://localhost:21000/api/atlas/types
>   "enumTypes":[
> 
>   ],
>   "structTypes":[
> 
>   ],
>   "traitTypes":[
> 
>   ],
>   "classTypes":[
> {
>   "superTypes":[
> 
>   ],
>   
> "hierarchicalMetaTypeName":"org.apache.atlas.typesystem.types.ClassType",
>   "typeName":"TypeDefString1",
>   "attributeDefinitions":[
> {
>   "name":"isCompositeFalse",
>   "dataTypeName":"string",
>   "multiplicity":"optional",
>   "isComposite":false,
>   "isUnique":false,
>   "isIndexable":false,
>   "reverseAttributeName":null
> },
> {
>   "name":"isTestable",
>   "dataTypeName":"boolean",
>   "multiplicity":"optional",
>   "isComposite":false,
>   "isUnique":false,
>   "isIndexable":false,
>   "reverseAttributeName":null
> }
>   ]
> }
>   ]
> }
> actual-
> http://localhost:21000/api/atlas/types?type=CLASS
> {
> "results": [
> "TypeDefString1",
> "TypeDefString1"
> ],
> "count": 60,
> "requestId": "qtp1879648991-299 - 8581163e-cb86-4ef3-af71-ff4495884cb0"
> }
> actual-
> http://localhost:21000/api/atlas/types?type=CLASS
> expected
> {
> "results": [
> "TypeDefString1"
> ],
> "count": 60,
> "requestId": "qtp1879648991-299 - 8581163e-cb86-4ef3-af71-ff4495884cb0"
> }



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (ATLAS-470) update types create a new index with same typename

[Neeru Gupta (JIRA)]

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

Neeru Gupta reassigned ATLAS-470:
-

Assignee: Neeru Gupta

> update types create a new index with same typename
> --
>
> Key: ATLAS-470
> URL: https://issues.apache.org/jira/browse/ATLAS-470
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
> Environment: Sandbox
>Reporter: Chethana
>Assignee: Neeru Gupta
>Priority: Critical
> Attachments: applicationLog_op.txt
>
>
> Create a type - 
> POST -  http://localhost:21000/api/atlas/types
>   "enumTypes":[
> 
>   ],
>   "structTypes":[
> 
>   ],
>   "traitTypes":[
> 
>   ],
>   "classTypes":[
> {
>   "superTypes":[
> 
>   ],
>   
> "hierarchicalMetaTypeName":"org.apache.atlas.typesystem.types.ClassType",
>   "typeName":"TypeDefString1",
>   "attributeDefinitions":[
> {
>   "name":"isCompositeFalse",
>   "dataTypeName":"string",
>   "multiplicity":"optional",
>   "isComposite":false,
>   "isUnique":false,
>   "isIndexable":false,
>   "reverseAttributeName":null
> }
>   ]
> }
>   ]
> }
> Update this type
> PUT-
> http://localhost:21000/api/atlas/types
>   "enumTypes":[
> 
>   ],
>   "structTypes":[
> 
>   ],
>   "traitTypes":[
> 
>   ],
>   "classTypes":[
> {
>   "superTypes":[
> 
>   ],
>   
> "hierarchicalMetaTypeName":"org.apache.atlas.typesystem.types.ClassType",
>   "typeName":"TypeDefString1",
>   "attributeDefinitions":[
> {
>   "name":"isCompositeFalse",
>   "dataTypeName":"string",
>   "multiplicity":"optional",
>   "isComposite":false,
>   "isUnique":false,
>   "isIndexable":false,
>   "reverseAttributeName":null
> },
> {
>   "name":"isTestable",
>   "dataTypeName":"boolean",
>   "multiplicity":"optional",
>   "isComposite":false,
>   "isUnique":false,
>   "isIndexable":false,
>   "reverseAttributeName":null
> }
>   ]
> }
>   ]
> }
> actual-
> http://localhost:21000/api/atlas/types?type=CLASS
> {
> "results": [
> "TypeDefString1",
> "TypeDefString1"
> ],
> "count": 60,
> "requestId": "qtp1879648991-299 - 8581163e-cb86-4ef3-af71-ff4495884cb0"
> }
> actual-
> http://localhost:21000/api/atlas/types?type=CLASS
> expected
> {
> "results": [
> "TypeDefString1"
> ],
> "count": 60,
> "requestId": "qtp1879648991-299 - 8581163e-cb86-4ef3-af71-ff4495884cb0"
> }



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-555) Tag creation from UI fails due to missing description attribute

[Neeru Gupta (JIRA)]

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

Neeru Gupta updated ATLAS-555:
--
Attachment: rb44588.patch

Patch contains fixes for UI to create tag.

> Tag creation from UI fails due to missing description attribute
> ---
>
> Key: ATLAS-555
> URL: https://issues.apache.org/jira/browse/ATLAS-555
> Project: Atlas
>  Issue Type: Bug
>Reporter: Hemanth Yamijala
>Assignee: Neeru Gupta
>Priority: Blocker
> Attachments: application.log, rb44588.patch
>
>
> I compiled Atlas from the master branch (git id: 
> 5b748aa47b970298a3c6b0c03495b3299079cd3e) and deployed. Ran hive-import 
> (which worked fine). Then tried to create a trait from the UI. This failed. 
> Relevant part of the stack trace: 
> {code} 
> Caused by: org.json4s.package$MappingException: No usable value for 
> typeDescription Did not find value which can be converted into 
> java.lang.String at org.json4s.reflect.package$.fail(package.scala:96) at 
> org.json4s.Extraction$ClassInstanceBuilder.org$json4s$Extraction$ClassInstanceBuilder$$buildCtorArg(Extraction.scala:462)
>  at 
> org.json4s.Extraction$ClassInstanceBuilder$$anonfun$14.apply(Extraction.scala:482)
>  at 
> org.json4s.Extraction$ClassInstanceBuilder$$anonfun$14.apply(Extraction.scala:482)
>  at 
> scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:244)
>  at 
> scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:244)
>  at 
> scala.collection.mutable.ResizableArray$class.foreach(ResizableArray.scala:59)
>  at scala.collection.mutable.ArrayBuffer.foreach(ArrayBuffer.scala:47) at 
> scala.collection.TraversableLike$class.map(TraversableLike.scala:244) at 
> scala.collection.AbstractTraversable.map(Traversable.scala:105) at 
> org.json4s.Extraction$ClassInstanceBuilder.org$json4s$Extraction$ClassInstanceBuilder$$instantiate(Extraction.scala:470)
>  at 
> org.json4s.Extraction$ClassInstanceBuilder$$anonfun$result$6.apply(Extraction.scala:515)
>  at 
> org.json4s.Extraction$ClassInstanceBuilder$$anonfun$result$6.apply(Extraction.scala:512)
>  at 
> org.json4s.Extraction$.org$json4s$Extraction$$customOrElse(Extraction.scala:524)
>  at org.json4s.Extraction$ClassInstanceBuilder.result(Extraction.scala:512) 
> at org.json4s.Extraction$.extract(Extraction.scala:351) at 
> org.json4s.Extraction$CollectionBuilder$$anonfun$6.apply(Extraction.scala:360)
>  at 
> org.json4s.Extraction$CollectionBuilder$$anonfun$6.apply(Extraction.scala:360)
>  at 
> scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:244)
>  at 
> scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:244)
>  at scala.collection.immutable.List.foreach(List.scala:318) at 
> scala.collection.TraversableLike$class.map(TraversableLike.scala:244) at 
> scala.collection.AbstractTraversable.map(Traversable.scala:105) at 
> org.json4s.Extraction$CollectionBuilder.mkCollection(Extraction.scala:360) at 
> org.json4s.Extraction$CollectionBuilder.result(Extraction.scala:384) at 
> org.json4s.Extraction$.extract(Extraction.scala:339) at 
> org.json4s.Extraction$ClassInstanceBuilder.org$json4s$Extraction$ClassInstanceBuilder$$buildCtorArg(Extraction.scala:450)
>  ... 72 more Caused by: org.json4s.package$MappingException: Did not find 
> value which can be converted into java.lang.String at 
> org.json4s.Extraction$.convert(Extraction.scala:603) at 
> org.json4s.Extraction$.extract(Extraction.scala:350) at 
> org.json4s.Extraction$ClassInstanceBuilder.org$json4s$Extraction$ClassInstanceBuilder$$buildCtorArg(Extraction.scala:450)
>  ... 97 more 
> {code} 
> (Will attach entire stack trace separately)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-555) Tag creation from UI fails due to missing description attribute

[Neeru Gupta (JIRA)]

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

Neeru Gupta commented on ATLAS-555:
---

I completely agree with you [~yhemanth]. It is important to have backward 
compatibility for publicly exposed APIs. but unfortunately, I could not find a 
good solution either. If you notice that description is actually optional in 
server side. We do have tests to create types without description. For that it 
needs to go through serialization APIs. UI optional attributes issue need to be 
addressed separately. 





> Tag creation from UI fails due to missing description attribute
> ---
>
> Key: ATLAS-555
> URL: https://issues.apache.org/jira/browse/ATLAS-555
> Project: Atlas
>  Issue Type: Bug
>Reporter: Hemanth Yamijala
>Assignee: Neeru Gupta
>Priority: Blocker
> Attachments: application.log
>
>
> I compiled Atlas from the master branch (git id: 
> 5b748aa47b970298a3c6b0c03495b3299079cd3e) and deployed. Ran hive-import 
> (which worked fine). Then tried to create a trait from the UI. This failed. 
> Relevant part of the stack trace: 
> {code} 
> Caused by: org.json4s.package$MappingException: No usable value for 
> typeDescription Did not find value which can be converted into 
> java.lang.String at org.json4s.reflect.package$.fail(package.scala:96) at 
> org.json4s.Extraction$ClassInstanceBuilder.org$json4s$Extraction$ClassInstanceBuilder$$buildCtorArg(Extraction.scala:462)
>  at 
> org.json4s.Extraction$ClassInstanceBuilder$$anonfun$14.apply(Extraction.scala:482)
>  at 
> org.json4s.Extraction$ClassInstanceBuilder$$anonfun$14.apply(Extraction.scala:482)
>  at 
> scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:244)
>  at 
> scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:244)
>  at 
> scala.collection.mutable.ResizableArray$class.foreach(ResizableArray.scala:59)
>  at scala.collection.mutable.ArrayBuffer.foreach(ArrayBuffer.scala:47) at 
> scala.collection.TraversableLike$class.map(TraversableLike.scala:244) at 
> scala.collection.AbstractTraversable.map(Traversable.scala:105) at 
> org.json4s.Extraction$ClassInstanceBuilder.org$json4s$Extraction$ClassInstanceBuilder$$instantiate(Extraction.scala:470)
>  at 
> org.json4s.Extraction$ClassInstanceBuilder$$anonfun$result$6.apply(Extraction.scala:515)
>  at 
> org.json4s.Extraction$ClassInstanceBuilder$$anonfun$result$6.apply(Extraction.scala:512)
>  at 
> org.json4s.Extraction$.org$json4s$Extraction$$customOrElse(Extraction.scala:524)
>  at org.json4s.Extraction$ClassInstanceBuilder.result(Extraction.scala:512) 
> at org.json4s.Extraction$.extract(Extraction.scala:351) at 
> org.json4s.Extraction$CollectionBuilder$$anonfun$6.apply(Extraction.scala:360)
>  at 
> org.json4s.Extraction$CollectionBuilder$$anonfun$6.apply(Extraction.scala:360)
>  at 
> scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:244)
>  at 
> scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:244)
>  at scala.collection.immutable.List.foreach(List.scala:318) at 
> scala.collection.TraversableLike$class.map(TraversableLike.scala:244) at 
> scala.collection.AbstractTraversable.map(Traversable.scala:105) at 
> org.json4s.Extraction$CollectionBuilder.mkCollection(Extraction.scala:360) at 
> org.json4s.Extraction$CollectionBuilder.result(Extraction.scala:384) at 
> org.json4s.Extraction$.extract(Extraction.scala:339) at 
> org.json4s.Extraction$ClassInstanceBuilder.org$json4s$Extraction$ClassInstanceBuilder$$buildCtorArg(Extraction.scala:450)
>  ... 72 more Caused by: org.json4s.package$MappingException: Did not find 
> value which can be converted into java.lang.String at 
> org.json4s.Extraction$.convert(Extraction.scala:603) at 
> org.json4s.Extraction$.extract(Extraction.scala:350) at 
> org.json4s.Extraction$ClassInstanceBuilder.org$json4s$Extraction$ClassInstanceBuilder$$buildCtorArg(Extraction.scala:450)
>  ... 97 more 
> {code} 
> (Will attach entire stack trace separately)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-555) Tag creation from UI fails due to missing description attribute

[Neeru Gupta (JIRA)]

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

Neeru Gupta commented on ATLAS-555:
---

Please review the code in 
https://reviews.apache.org/r/44588/

This fix fixes the UI to create tags.

> Tag creation from UI fails due to missing description attribute
> ---
>
> Key: ATLAS-555
> URL: https://issues.apache.org/jira/browse/ATLAS-555
> Project: Atlas
>  Issue Type: Bug
>Reporter: Hemanth Yamijala
>Assignee: Neeru Gupta
>Priority: Blocker
> Attachments: application.log
>
>
> I compiled Atlas from the master branch (git id: 
> 5b748aa47b970298a3c6b0c03495b3299079cd3e) and deployed. Ran hive-import 
> (which worked fine). Then tried to create a trait from the UI. This failed. 
> Relevant part of the stack trace: 
> {code} 
> Caused by: org.json4s.package$MappingException: No usable value for 
> typeDescription Did not find value which can be converted into 
> java.lang.String at org.json4s.reflect.package$.fail(package.scala:96) at 
> org.json4s.Extraction$ClassInstanceBuilder.org$json4s$Extraction$ClassInstanceBuilder$$buildCtorArg(Extraction.scala:462)
>  at 
> org.json4s.Extraction$ClassInstanceBuilder$$anonfun$14.apply(Extraction.scala:482)
>  at 
> org.json4s.Extraction$ClassInstanceBuilder$$anonfun$14.apply(Extraction.scala:482)
>  at 
> scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:244)
>  at 
> scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:244)
>  at 
> scala.collection.mutable.ResizableArray$class.foreach(ResizableArray.scala:59)
>  at scala.collection.mutable.ArrayBuffer.foreach(ArrayBuffer.scala:47) at 
> scala.collection.TraversableLike$class.map(TraversableLike.scala:244) at 
> scala.collection.AbstractTraversable.map(Traversable.scala:105) at 
> org.json4s.Extraction$ClassInstanceBuilder.org$json4s$Extraction$ClassInstanceBuilder$$instantiate(Extraction.scala:470)
>  at 
> org.json4s.Extraction$ClassInstanceBuilder$$anonfun$result$6.apply(Extraction.scala:515)
>  at 
> org.json4s.Extraction$ClassInstanceBuilder$$anonfun$result$6.apply(Extraction.scala:512)
>  at 
> org.json4s.Extraction$.org$json4s$Extraction$$customOrElse(Extraction.scala:524)
>  at org.json4s.Extraction$ClassInstanceBuilder.result(Extraction.scala:512) 
> at org.json4s.Extraction$.extract(Extraction.scala:351) at 
> org.json4s.Extraction$CollectionBuilder$$anonfun$6.apply(Extraction.scala:360)
>  at 
> org.json4s.Extraction$CollectionBuilder$$anonfun$6.apply(Extraction.scala:360)
>  at 
> scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:244)
>  at 
> scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:244)
>  at scala.collection.immutable.List.foreach(List.scala:318) at 
> scala.collection.TraversableLike$class.map(TraversableLike.scala:244) at 
> scala.collection.AbstractTraversable.map(Traversable.scala:105) at 
> org.json4s.Extraction$CollectionBuilder.mkCollection(Extraction.scala:360) at 
> org.json4s.Extraction$CollectionBuilder.result(Extraction.scala:384) at 
> org.json4s.Extraction$.extract(Extraction.scala:339) at 
> org.json4s.Extraction$ClassInstanceBuilder.org$json4s$Extraction$ClassInstanceBuilder$$buildCtorArg(Extraction.scala:450)
>  ... 72 more Caused by: org.json4s.package$MappingException: Did not find 
> value which can be converted into java.lang.String at 
> org.json4s.Extraction$.convert(Extraction.scala:603) at 
> org.json4s.Extraction$.extract(Extraction.scala:350) at 
> org.json4s.Extraction$ClassInstanceBuilder.org$json4s$Extraction$ClassInstanceBuilder$$buildCtorArg(Extraction.scala:450)
>  ... 97 more 
> {code} 
> (Will attach entire stack trace separately)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (ATLAS-555) Tag creation from UI fails due to missing description attribute

[Neeru Gupta (JIRA)]

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

Neeru Gupta reassigned ATLAS-555:
-

Assignee: Neeru Gupta

> Tag creation from UI fails due to missing description attribute
> ---
>
> Key: ATLAS-555
> URL: https://issues.apache.org/jira/browse/ATLAS-555
> Project: Atlas
>  Issue Type: Bug
>Reporter: Hemanth Yamijala
>Assignee: Neeru Gupta
>Priority: Blocker
> Attachments: application.log
>
>
> I compiled Atlas from the master branch (git id: 
> 5b748aa47b970298a3c6b0c03495b3299079cd3e) and deployed. Ran hive-import 
> (which worked fine). Then tried to create a trait from the UI. This failed. 
> Relevant part of the stack trace: 
> {code} 
> Caused by: org.json4s.package$MappingException: No usable value for 
> typeDescription Did not find value which can be converted into 
> java.lang.String at org.json4s.reflect.package$.fail(package.scala:96) at 
> org.json4s.Extraction$ClassInstanceBuilder.org$json4s$Extraction$ClassInstanceBuilder$$buildCtorArg(Extraction.scala:462)
>  at 
> org.json4s.Extraction$ClassInstanceBuilder$$anonfun$14.apply(Extraction.scala:482)
>  at 
> org.json4s.Extraction$ClassInstanceBuilder$$anonfun$14.apply(Extraction.scala:482)
>  at 
> scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:244)
>  at 
> scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:244)
>  at 
> scala.collection.mutable.ResizableArray$class.foreach(ResizableArray.scala:59)
>  at scala.collection.mutable.ArrayBuffer.foreach(ArrayBuffer.scala:47) at 
> scala.collection.TraversableLike$class.map(TraversableLike.scala:244) at 
> scala.collection.AbstractTraversable.map(Traversable.scala:105) at 
> org.json4s.Extraction$ClassInstanceBuilder.org$json4s$Extraction$ClassInstanceBuilder$$instantiate(Extraction.scala:470)
>  at 
> org.json4s.Extraction$ClassInstanceBuilder$$anonfun$result$6.apply(Extraction.scala:515)
>  at 
> org.json4s.Extraction$ClassInstanceBuilder$$anonfun$result$6.apply(Extraction.scala:512)
>  at 
> org.json4s.Extraction$.org$json4s$Extraction$$customOrElse(Extraction.scala:524)
>  at org.json4s.Extraction$ClassInstanceBuilder.result(Extraction.scala:512) 
> at org.json4s.Extraction$.extract(Extraction.scala:351) at 
> org.json4s.Extraction$CollectionBuilder$$anonfun$6.apply(Extraction.scala:360)
>  at 
> org.json4s.Extraction$CollectionBuilder$$anonfun$6.apply(Extraction.scala:360)
>  at 
> scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:244)
>  at 
> scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:244)
>  at scala.collection.immutable.List.foreach(List.scala:318) at 
> scala.collection.TraversableLike$class.map(TraversableLike.scala:244) at 
> scala.collection.AbstractTraversable.map(Traversable.scala:105) at 
> org.json4s.Extraction$CollectionBuilder.mkCollection(Extraction.scala:360) at 
> org.json4s.Extraction$CollectionBuilder.result(Extraction.scala:384) at 
> org.json4s.Extraction$.extract(Extraction.scala:339) at 
> org.json4s.Extraction$ClassInstanceBuilder.org$json4s$Extraction$ClassInstanceBuilder$$buildCtorArg(Extraction.scala:450)
>  ... 72 more Caused by: org.json4s.package$MappingException: Did not find 
> value which can be converted into java.lang.String at 
> org.json4s.Extraction$.convert(Extraction.scala:603) at 
> org.json4s.Extraction$.extract(Extraction.scala:350) at 
> org.json4s.Extraction$ClassInstanceBuilder.org$json4s$Extraction$ClassInstanceBuilder$$buildCtorArg(Extraction.scala:450)
>  ... 97 more 
> {code} 
> (Will attach entire stack trace separately)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-479) Add description for different types during create time

[Neeru Gupta (JIRA)]

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

Neeru Gupta updated ATLAS-479:
--
Attachment: (was: rb43531(7).patch)

> Add description for different types during create time
> --
>
> Key: ATLAS-479
> URL: https://issues.apache.org/jira/browse/ATLAS-479
> Project: Atlas
>  Issue Type: Sub-task
>Affects Versions: 0.6-incubating
>Reporter: Neeru Gupta
>Assignee: Neeru Gupta
> Fix For: 0.7-incubating
>
> Attachments: graycol.gif
>
>
> Ability to specify description while creating different types like Struct, 
> Enum, Class and Trait type.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (ATLAS-479) Add description for different types during create time

[Neeru Gupta (JIRA)]

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

Neeru Gupta edited comment on ATLAS-479 at 3/4/16 12:34 AM:


Fixed the test failure issues caused by constructor overloading.

[~shwethags] Please review and commit.


was (Author: guptaneeru):
Fixed the test failure issues caused by constructor overloading.

> Add description for different types during create time
> --
>
> Key: ATLAS-479
> URL: https://issues.apache.org/jira/browse/ATLAS-479
> Project: Atlas
>  Issue Type: Sub-task
>Affects Versions: 0.6-incubating
>Reporter: Neeru Gupta
>Assignee: Neeru Gupta
> Fix For: 0.7-incubating
>
> Attachments: graycol.gif, rb43531(7).patch
>
>
> Ability to specify description while creating different types like Struct, 
> Enum, Class and Trait type.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-479) Add description for different types during create time

[Neeru Gupta (JIRA)]

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

Neeru Gupta updated ATLAS-479:
--
Attachment: rb43531(7).patch

Fixed the test failure issues caused by constructor overloading.

> Add description for different types during create time
> --
>
> Key: ATLAS-479
> URL: https://issues.apache.org/jira/browse/ATLAS-479
> Project: Atlas
>  Issue Type: Sub-task
>Affects Versions: 0.6-incubating
>Reporter: Neeru Gupta
>Assignee: Neeru Gupta
> Fix For: 0.7-incubating
>
> Attachments: graycol.gif, rb43531(7).patch
>
>
> Ability to specify description while creating different types like Struct, 
> Enum, Class and Trait type.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-479) Add description for different types during create time

[Neeru Gupta (JIRA)]

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

Neeru Gupta updated ATLAS-479:
--
Attachment: (was: rb43531(6).patch)

> Add description for different types during create time
> --
>
> Key: ATLAS-479
> URL: https://issues.apache.org/jira/browse/ATLAS-479
> Project: Atlas
>  Issue Type: Sub-task
>Affects Versions: 0.6-incubating
>Reporter: Neeru Gupta
>Assignee: Neeru Gupta
> Fix For: 0.7-incubating
>
> Attachments: graycol.gif
>
>
> Ability to specify description while creating different types like Struct, 
> Enum, Class and Trait type.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-474) Server does not start if the type is updated with same super type class information

[Neeru Gupta (JIRA)]

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

Neeru Gupta commented on ATLAS-474:
---

+1 . Have reviewed the code and looks good to me.

> Server does not start if the type is updated with same super type class 
> information
> ---
>
> Key: ATLAS-474
> URL: https://issues.apache.org/jira/browse/ATLAS-474
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: trunk
> Environment: sandbox
>Reporter: Chethana
>Assignee: David Kantor
>Priority: Blocker
>
> Create a class with a superType class.
> Use update API and do not change the request used.
> Restart atlas server 
> Fails with exception
> K":1},"pattern":"static","timestamp":"1454921806183"} stored data: 
> {"version":1,"subscription":{"ATLAS_HOOK":1},"pattern":"static","timestamp":"1454921372384"}
>  (ZkUtils$:68)
> 2016-02-09 00:00:02,149 INFO  - [ZkClient-EventThread-91-localhost:9026:] ~ I 
> wrote this conflicted ephemeral node 
> [{"version":1,"subscription":{"ATLAS_HOOK":1},"pattern":"static","timestamp":"1454921806183"}]
>  at /consumers/atlas/ids/atlas_Chethanas-MBP.local-1454412213224-de1ce8e6 a 
> while back in a different session, hence I will backoff for this node to be 
> deleted by Zookeeper and retry (ZkUtils$:68)
> 2016-02-09 00:00:02,554 INFO  - [ProcessThread(sid:0 cport:-1)::] ~ Got 
> user-level KeeperException when processing sessionid:0x152a1b9238e0051 
> type:create cxid:0x3f0bf zxid:0x1c0ec txntype:-1 reqpath:n/a Error 
> Path:/consumers/atlas/ids/atlas_Chethanas-MBP.local-1454412213224-de1ce8e6 
> Error:KeeperErrorCode = NodeExists for 
> /consumers/atlas/ids/atlas_Chethanas-MBP.local-1454412213224-de1ce8e6 
> (PrepRequest...skipping...
> at 
> org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
> at org.eclipse.jetty.server.Server.doStart(Server.java:354)
> at 
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at 
> org.apache.atlas.web.service.EmbeddedServer.start(EmbeddedServer.java:88)
> at org.apache.atlas.Atlas.main(Atlas.java:107)
> Caused by: java.lang.RuntimeException: org.apache.atlas.AtlasException: Type 
> classa3ozcd7yra extends superType superClassa3ozcd7yra multiple times
> at 
> org.apache.atlas.services.DefaultMetadataService.restoreTypeSystem(DefaultMetadataService.java:113)
> at 
> org.apache.atlas.services.DefaultMetadataService.(DefaultMetadataService.java:100)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native 
> Method)
> at 
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
> at 
> com.google.inject.internal.DefaultConstructionProxyFactory$2.newInstance(DefaultConstructionProxyFactory.java:86)
> at 
> com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:105)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-479) Add description for different types during create time

[Neeru Gupta (JIRA)]

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

Neeru Gupta updated ATLAS-479:
--
Attachment: rb43531(6).patch

> Add description for different types during create time
> --
>
> Key: ATLAS-479
> URL: https://issues.apache.org/jira/browse/ATLAS-479
> Project: Atlas
>  Issue Type: Sub-task
>Affects Versions: 0.6-incubating
>Reporter: Neeru Gupta
>Assignee: Neeru Gupta
> Fix For: 0.7-incubating
>
> Attachments: graycol.gif, rb43531(6).patch
>
>
> Ability to specify description while creating different types like Struct, 
> Enum, Class and Trait type.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-479) Add description for different types during create time

[Neeru Gupta (JIRA)]

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

Neeru Gupta updated ATLAS-479:
--
Attachment: (was: rb43531(5).patch)

> Add description for different types during create time
> --
>
> Key: ATLAS-479
> URL: https://issues.apache.org/jira/browse/ATLAS-479
> Project: Atlas
>  Issue Type: Sub-task
>Affects Versions: 0.6-incubating
>Reporter: Neeru Gupta
>Assignee: Neeru Gupta
> Fix For: 0.7-incubating
>
> Attachments: graycol.gif
>
>
> Ability to specify description while creating different types like Struct, 
> Enum, Class and Trait type.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-479) Add description for different types during create time

[Neeru Gupta (JIRA)]

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

Neeru Gupta updated ATLAS-479:
--
Attachment: graycol.gif


Hi Shwetha,

Thanks for reviewing the code. I have seen the test failures in ATLS-QA
builds. I am unable to reproduce these issues in my environment. Can you
please let me know if you ran tests on QA build or on separate server. How
are you running the tests. I ran mvn clean install from root folder.

-Neeru



From:   "Shwetha G S (JIRA)" 
To: Fnu Neerju/Boston/IBM@IBMUS
Date:   03/01/2016 01:17 AM
Subject:[jira] [Commented] (ATLAS-479) Add description for different
types during create time




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

Shwetha G S commented on ATLAS-479:
---

Tests failed for me with the latest patch. Updated review board. Can you
check?

Struct, Enum, Class and Trait type.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)




> Add description for different types during create time
> --
>
> Key: ATLAS-479
> URL: https://issues.apache.org/jira/browse/ATLAS-479
> Project: Atlas
>  Issue Type: Sub-task
>Affects Versions: 0.6-incubating
>Reporter: Neeru Gupta
>Assignee: Neeru Gupta
> Fix For: 0.7-incubating
>
> Attachments: graycol.gif, rb43531(5).patch
>
>
> Ability to specify description while creating different types like Struct, 
> Enum, Class and Trait type.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-479) Add description for different types during create time

[Neeru Gupta (JIRA)]

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

Neeru Gupta updated ATLAS-479:
--
Attachment: rb43531(5).patch

Updated patch attached after addressing RB comments from Shwetha GS.

Thank You  [~shwethags]

> Add description for different types during create time
> --
>
> Key: ATLAS-479
> URL: https://issues.apache.org/jira/browse/ATLAS-479
> Project: Atlas
>  Issue Type: Sub-task
>Affects Versions: 0.6-incubating
>Reporter: Neeru Gupta
>Assignee: Neeru Gupta
> Fix For: 0.7-incubating
>
> Attachments: rb43531(5).patch
>
>
> Ability to specify description while creating different types like Struct, 
> Enum, Class and Trait type.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-479) Add description for different types during create time

[Neeru Gupta (JIRA)]

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

Neeru Gupta updated ATLAS-479:
--
Attachment: (was: rb43531(4).patch)

> Add description for different types during create time
> --
>
> Key: ATLAS-479
> URL: https://issues.apache.org/jira/browse/ATLAS-479
> Project: Atlas
>  Issue Type: Sub-task
>Affects Versions: 0.6-incubating
>Reporter: Neeru Gupta
>Assignee: Neeru Gupta
> Fix For: 0.7-incubating
>
>
> Ability to specify description while creating different types like Struct, 
> Enum, Class and Trait type.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-479) Add description for different types during create time

[Neeru Gupta (JIRA)]

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

Neeru Gupta updated ATLAS-479:
--
Attachment: rb43531(4).patch

latest patch.

> Add description for different types during create time
> --
>
> Key: ATLAS-479
> URL: https://issues.apache.org/jira/browse/ATLAS-479
> Project: Atlas
>  Issue Type: Sub-task
>Affects Versions: 0.6-incubating
>Reporter: Neeru Gupta
>Assignee: Neeru Gupta
> Fix For: 0.7-incubating
>
> Attachments: rb43531(4).patch
>
>
> Ability to specify description while creating different types like Struct, 
> Enum, Class and Trait type.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-479) Add description for different types during create time

[Neeru Gupta (JIRA)]

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

Neeru Gupta updated ATLAS-479:
--
Attachment: (was: rb43531(3).patch)

> Add description for different types during create time
> --
>
> Key: ATLAS-479
> URL: https://issues.apache.org/jira/browse/ATLAS-479
> Project: Atlas
>  Issue Type: Sub-task
>Affects Versions: 0.6-incubating
>Reporter: Neeru Gupta
>Assignee: Neeru Gupta
> Fix For: 0.7-incubating
>
> Attachments: rb43531(4).patch
>
>
> Ability to specify description while creating different types like Struct, 
> Enum, Class and Trait type.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-479) Add description for different types during create time

[Neeru Gupta (JIRA)]

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

Neeru Gupta updated ATLAS-479:
--
Attachment: (was: rb43531(2).patch)

> Add description for different types during create time
> --
>
> Key: ATLAS-479
> URL: https://issues.apache.org/jira/browse/ATLAS-479
> Project: Atlas
>  Issue Type: Sub-task
>Affects Versions: 0.6-incubating
>Reporter: Neeru Gupta
>Assignee: Neeru Gupta
> Fix For: 0.7-incubating
>
> Attachments: rb43531(3).patch
>
>
> Ability to specify description while creating different types like Struct, 
> Enum, Class and Trait type.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-479) Add description for different types during create time

[Neeru Gupta (JIRA)]

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

Neeru Gupta updated ATLAS-479:
--
Attachment: (was: rb43531.patch)

> Add description for different types during create time
> --
>
> Key: ATLAS-479
> URL: https://issues.apache.org/jira/browse/ATLAS-479
> Project: Atlas
>  Issue Type: Sub-task
>Affects Versions: 0.6-incubating
>Reporter: Neeru Gupta
>Assignee: Neeru Gupta
> Fix For: 0.7-incubating
>
> Attachments: rb43531(2).patch
>
>
> Ability to specify description while creating different types like Struct, 
> Enum, Class and Trait type.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-479) Add description for different types during create time

[Neeru Gupta (JIRA)]

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

Neeru Gupta updated ATLAS-479:
--
Attachment: rb43531(2).patch

Attached is the patch with fixes which should fix the test failures and also 
additional test cases. Note that we were not able to reproduce the failures 
here.

> Add description for different types during create time
> --
>
> Key: ATLAS-479
> URL: https://issues.apache.org/jira/browse/ATLAS-479
> Project: Atlas
>  Issue Type: Sub-task
>Affects Versions: 0.6-incubating
>Reporter: Neeru Gupta
>Assignee: Neeru Gupta
> Fix For: 0.7-incubating
>
> Attachments: rb43531(2).patch
>
>
> Ability to specify description while creating different types like Struct, 
> Enum, Class and Trait type.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-479) Add description for different types during create time

[Neeru Gupta (JIRA)]

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

Neeru Gupta commented on ATLAS-479:
---

TestSerialization tests run successfully on my environment. Is there any 
specific way to reproduce the test failures?

> Add description for different types during create time
> --
>
> Key: ATLAS-479
> URL: https://issues.apache.org/jira/browse/ATLAS-479
> Project: Atlas
>  Issue Type: Sub-task
>Affects Versions: 0.6-incubating
>Reporter: Neeru Gupta
>Assignee: Neeru Gupta
> Fix For: 0.7-incubating
>
> Attachments: rb43531.patch
>
>
> Ability to specify description while creating different types like Struct, 
> Enum, Class and Trait type.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-479) Add description for different types during create time

[Neeru Gupta (JIRA)]

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

Neeru Gupta updated ATLAS-479:
--
Attachment: rb43531.patch

patch updated

> Add description for different types during create time
> --
>
> Key: ATLAS-479
> URL: https://issues.apache.org/jira/browse/ATLAS-479
> Project: Atlas
>  Issue Type: Sub-task
>Affects Versions: 0.6-incubating
>Reporter: Neeru Gupta
>Assignee: Neeru Gupta
> Fix For: 0.7-incubating
>
> Attachments: rb43531.patch
>
>
> Ability to specify description while creating different types like Struct, 
> Enum, Class and Trait type.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-396) Creating an entity with non-existing type results in "Unable to deserialize json" error

[Neeru Gupta (JIRA)]

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

Neeru Gupta updated ATLAS-396:
--
Attachment: (was: atlas-396-patch)

> Creating an entity with non-existing type results in "Unable to deserialize 
> json" error
> ---
>
> Key: ATLAS-396
> URL: https://issues.apache.org/jira/browse/ATLAS-396
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.6-incubating
>Reporter: Ayub Khan
>Assignee: Neeru Gupta
>Priority: Minor
>  Labels: regression
> Fix For: trunk
>
> Attachments: atlas-396-patch-v4, rb42967.patch
>
>
> Creating an entity with non-existing type results in "Unable to deserialize 
> json" error. This error message should have been "Unknown datatype: ".  
> This is a regression issue..
> Logs
> {noformat}
> Configuring TestNG with: TestNG652Configurator
> 2015-12-17 14:21:59,381 INFO  - [main:] ~ Request Url: 
> http://os-r6-atlas-erie-tp-testing-2.novalocal:21000/api/atlas/types?user.name=apathan
>  (BaseRequest:164)
> 2015-12-17 14:21:59,383 INFO  - [main:] ~ Request Method: POST 
> (BaseRequest:165)
> 2015-12-17 14:21:59,384 INFO  - [main:] ~ Request Header: Name=Content-Type 
> Value=application/json; charset=UTF-8 (BaseRequest:168)
> 2015-12-17 14:22:00,238 INFO  - [main:] ~ Response Status: HTTP/1.1 201 
> Created (BaseRequest:195)
> 2015-12-17 14:22:00,238 INFO  - [main:] ~ Response Header: Name=Date 
> Value=Thu, 17 Dec 2015 08:51:59 GMT (BaseRequest:197)
> 2015-12-17 14:22:00,238 INFO  - [main:] ~ Response Header: Name=Content-Type 
> Value=application/json; charset=UTF-8 (BaseRequest:197)
> 2015-12-17 14:22:00,238 INFO  - [main:] ~ Response Header: 
> Name=Transfer-Encoding Value=chunked (BaseRequest:197)
> 2015-12-17 14:22:00,238 INFO  - [main:] ~ Response Header: Name=Server 
> Value=Jetty(9.2.12.v20150709) (BaseRequest:197)
> 2015-12-17 14:22:00,254 INFO  - [main:] ~ 
> 
>  (TestNGListener:36)
> 2015-12-17 14:22:00,254 INFO  - [main:] ~ Testing going to start for: 
> org.apache.atlas.regression.tests.EntityResourceTest.createEntityForNonExistantType([])
>  (TestNGListener:37)
> 2015-12-17 14:22:00,678 INFO  - [main:createEntityForNonExistantType] ~ 
> Request body is :{
>   
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
>   "id":{
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "id":"-145034232025579",
> "version":0,
> "typeName":"createEntityForNonExistantTypeo88sflmm7k"
>   },
>   "typeName":"createEntityForNonExistantTypeo88sflmm7k",
>   "values":{
> 
>   },
>   "traitNames":[
> 
>   ],
>   "traits":{
> 
>   }
> } (EntityResourceTest:394)
> 2015-12-17 14:22:00,680 INFO  - [main:createEntityForNonExistantType] ~ 
> Request Url: 
> http://os-r6-atlas-erie-tp-testing-2.novalocal:21000/api/atlas/entities?user.name=apathan
>  (BaseRequest:164)
> 2015-12-17 14:22:00,681 INFO  - [main:createEntityForNonExistantType] ~ 
> Request Method: POST (BaseRequest:165)
> 2015-12-17 14:22:00,681 INFO  - [main:createEntityForNonExistantType] ~ 
> Request Header: Name=Content-Type Value=application/json; charset=UTF-8 
> (BaseRequest:168)
> 2015-12-17 14:22:01,309 INFO  - [main:createEntityForNonExistantType] ~ 
> Response Status: HTTP/1.1 400 Bad Request (BaseRequest:195)
> 2015-12-17 14:22:01,310 INFO  - [main:createEntityForNonExistantType] ~ 
> Response Header: Name=Date Value=Thu, 17 Dec 2015 08:52:01 GMT 
> (BaseRequest:197)
> 2015-12-17 14:22:01,312 INFO  - [main:createEntityForNonExistantType] ~ 
> Response Header: Name=Content-Type Value=application/json; charset=UTF-8 
> (BaseRequest:197)
> 2015-12-17 14:22:01,312 INFO  - [main:createEntityForNonExistantType] ~ 
> Response Header: Name=Transfer-Encoding Value=chunked (BaseRequest:197)
> 2015-12-17 14:22:01,312 INFO  - [main:createEntityForNonExistantType] ~ 
> Response Header: Name=Server Value=Jetty(9.2.12.v20150709) (BaseRequest:197)
> 2015-12-17 14:22:01,314 INFO  - [main:createEntityForNonExistantType] ~ 
> Response is: {"error":"Unable to deserialize 
> json","stackTrace":"java.lang.IllegalArgumentException: Unable to deserialize 
> json\n\tat 
> org.apache.atlas.services.DefaultMetadataService.deserializeClassInstances(DefaultMetadataService.java:315)\n\tat
>  
> org.apache.atlas.services.DefaultMetadataService.createEntities(DefaultMetadataService.java:280)\n\tat
>  
> org.apache.atlas.web.resources.EntityResource.submit(EntityResource.java:114)\n\tat
>  sun.reflect.GeneratedMethodAccessor29.invoke(Unknown Source)\n\tat 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat
>  

[jira] [Issue Comment Deleted] (ATLAS-396) Creating an entity with non-existing type results in "Unable to deserialize json" error

[Neeru Gupta (JIRA)]

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

Neeru Gupta updated ATLAS-396:
--
Comment: was deleted

(was: Attaching latest patch)

> Creating an entity with non-existing type results in "Unable to deserialize 
> json" error
> ---
>
> Key: ATLAS-396
> URL: https://issues.apache.org/jira/browse/ATLAS-396
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.6-incubating
>Reporter: Ayub Khan
>Assignee: Neeru Gupta
>Priority: Minor
>  Labels: regression
> Fix For: trunk
>
> Attachments: rb42967.patch
>
>
> Creating an entity with non-existing type results in "Unable to deserialize 
> json" error. This error message should have been "Unknown datatype: ".  
> This is a regression issue..
> Logs
> {noformat}
> Configuring TestNG with: TestNG652Configurator
> 2015-12-17 14:21:59,381 INFO  - [main:] ~ Request Url: 
> http://os-r6-atlas-erie-tp-testing-2.novalocal:21000/api/atlas/types?user.name=apathan
>  (BaseRequest:164)
> 2015-12-17 14:21:59,383 INFO  - [main:] ~ Request Method: POST 
> (BaseRequest:165)
> 2015-12-17 14:21:59,384 INFO  - [main:] ~ Request Header: Name=Content-Type 
> Value=application/json; charset=UTF-8 (BaseRequest:168)
> 2015-12-17 14:22:00,238 INFO  - [main:] ~ Response Status: HTTP/1.1 201 
> Created (BaseRequest:195)
> 2015-12-17 14:22:00,238 INFO  - [main:] ~ Response Header: Name=Date 
> Value=Thu, 17 Dec 2015 08:51:59 GMT (BaseRequest:197)
> 2015-12-17 14:22:00,238 INFO  - [main:] ~ Response Header: Name=Content-Type 
> Value=application/json; charset=UTF-8 (BaseRequest:197)
> 2015-12-17 14:22:00,238 INFO  - [main:] ~ Response Header: 
> Name=Transfer-Encoding Value=chunked (BaseRequest:197)
> 2015-12-17 14:22:00,238 INFO  - [main:] ~ Response Header: Name=Server 
> Value=Jetty(9.2.12.v20150709) (BaseRequest:197)
> 2015-12-17 14:22:00,254 INFO  - [main:] ~ 
> 
>  (TestNGListener:36)
> 2015-12-17 14:22:00,254 INFO  - [main:] ~ Testing going to start for: 
> org.apache.atlas.regression.tests.EntityResourceTest.createEntityForNonExistantType([])
>  (TestNGListener:37)
> 2015-12-17 14:22:00,678 INFO  - [main:createEntityForNonExistantType] ~ 
> Request body is :{
>   
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
>   "id":{
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "id":"-145034232025579",
> "version":0,
> "typeName":"createEntityForNonExistantTypeo88sflmm7k"
>   },
>   "typeName":"createEntityForNonExistantTypeo88sflmm7k",
>   "values":{
> 
>   },
>   "traitNames":[
> 
>   ],
>   "traits":{
> 
>   }
> } (EntityResourceTest:394)
> 2015-12-17 14:22:00,680 INFO  - [main:createEntityForNonExistantType] ~ 
> Request Url: 
> http://os-r6-atlas-erie-tp-testing-2.novalocal:21000/api/atlas/entities?user.name=apathan
>  (BaseRequest:164)
> 2015-12-17 14:22:00,681 INFO  - [main:createEntityForNonExistantType] ~ 
> Request Method: POST (BaseRequest:165)
> 2015-12-17 14:22:00,681 INFO  - [main:createEntityForNonExistantType] ~ 
> Request Header: Name=Content-Type Value=application/json; charset=UTF-8 
> (BaseRequest:168)
> 2015-12-17 14:22:01,309 INFO  - [main:createEntityForNonExistantType] ~ 
> Response Status: HTTP/1.1 400 Bad Request (BaseRequest:195)
> 2015-12-17 14:22:01,310 INFO  - [main:createEntityForNonExistantType] ~ 
> Response Header: Name=Date Value=Thu, 17 Dec 2015 08:52:01 GMT 
> (BaseRequest:197)
> 2015-12-17 14:22:01,312 INFO  - [main:createEntityForNonExistantType] ~ 
> Response Header: Name=Content-Type Value=application/json; charset=UTF-8 
> (BaseRequest:197)
> 2015-12-17 14:22:01,312 INFO  - [main:createEntityForNonExistantType] ~ 
> Response Header: Name=Transfer-Encoding Value=chunked (BaseRequest:197)
> 2015-12-17 14:22:01,312 INFO  - [main:createEntityForNonExistantType] ~ 
> Response Header: Name=Server Value=Jetty(9.2.12.v20150709) (BaseRequest:197)
> 2015-12-17 14:22:01,314 INFO  - [main:createEntityForNonExistantType] ~ 
> Response is: {"error":"Unable to deserialize 
> json","stackTrace":"java.lang.IllegalArgumentException: Unable to deserialize 
> json\n\tat 
> org.apache.atlas.services.DefaultMetadataService.deserializeClassInstances(DefaultMetadataService.java:315)\n\tat
>  
> org.apache.atlas.services.DefaultMetadataService.createEntities(DefaultMetadataService.java:280)\n\tat
>  
> org.apache.atlas.web.resources.EntityResource.submit(EntityResource.java:114)\n\tat
>  sun.reflect.GeneratedMethodAccessor29.invoke(Unknown Source)\n\tat 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat
>  

[jira] [Assigned] (ATLAS-436) Add LIMIT to search DSL

[Neeru Gupta (JIRA)]

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

Neeru Gupta reassigned ATLAS-436:
-

Assignee: Neeru Gupta

> Add LIMIT to search DSL
> ---
>
> Key: ATLAS-436
> URL: https://issues.apache.org/jira/browse/ATLAS-436
> Project: Atlas
>  Issue Type: Improvement
>Reporter: David Kantor
>Assignee: Neeru Gupta
>
> Add LIMIT to Atlas search DSL



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-479) Add description for different types during create time

[Neeru Gupta (JIRA)]

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

Neeru Gupta commented on ATLAS-479:
---

https://reviews.apache.org/r/43531

> Add description for different types during create time
> --
>
> Key: ATLAS-479
> URL: https://issues.apache.org/jira/browse/ATLAS-479
> Project: Atlas
>  Issue Type: Sub-task
>Affects Versions: 0.6-incubating
>Reporter: Neeru Gupta
>Assignee: Neeru Gupta
> Fix For: 0.7-incubating
>
>
> Ability to specify description while creating different types like Struct, 
> Enum, Class and Trait type.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-480) Ability to update description after create

[Neeru Gupta (JIRA)]

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

Neeru Gupta updated ATLAS-480:
--
Description: Add ability to update description after creating a type.  
(was: Add ability to update description.)

> Ability to update description after create
> --
>
> Key: ATLAS-480
> URL: https://issues.apache.org/jira/browse/ATLAS-480
> Project: Atlas
>  Issue Type: Sub-task
>Affects Versions: 0.6-incubating
>Reporter: Neeru Gupta
>Assignee: Neeru Gupta
> Fix For: 0.7-incubating
>
>
> Add ability to update description after creating a type.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (ATLAS-480) Ability to update description after create

[Neeru Gupta (JIRA)]

Neeru Gupta created ATLAS-480:
-

 Summary: Ability to update description after create
 Key: ATLAS-480
 URL: https://issues.apache.org/jira/browse/ATLAS-480
 Project: Atlas
  Issue Type: Sub-task
Affects Versions: 0.6-incubating
Reporter: Neeru Gupta
Assignee: Neeru Gupta
 Fix For: 0.7-incubating


Add ability to update description.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)