[jira] [Commented] (ATLAS-1612) Regression: DSL search using a non-unique attribute of user-defined types results in empty response
[
https://issues.apache.org/jira/browse/ATLAS-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15897026#comment-15897026
]
Vimal Sharma commented on ATLAS-1612:
-
[~ayubkhan]
The issue is that the DSL query is not correct. The correct DSL query should be
"sample where name = \"simple_column\"" and not
"sample where name = \"sample_column\"". The first query produces the expected
results.
Please verify with the correct query. Marking the issue as resolved
> Regression: DSL search using a non-unique attribute of user-defined types
> results in empty response
> ---
>
> Key: ATLAS-1612
> URL: https://issues.apache.org/jira/browse/ATLAS-1612
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: trunk, 0.8-incubating
>Reporter: Ayub Khan
>Assignee: Vimal Sharma
>Priority: Blocker
> Fix For: trunk, 0.8-incubating
>
>
> Steps to repro:
> 1. Create a user defined type like below
> {noformat}
> {
> "enumTypes":[
> ],
> "structTypes":[
> ],
> "traitTypes":[
> ],
> "classTypes":[
> {
> "superTypes":[
> ],
>
> "hierarchicalMetaTypeName":"org.apache.atlas.typesystem.types.ClassType",
> "typeName":"sample",
> "typeDescription":null,
> "typeVersion":"1.0",
> "attributeDefinitions":[
> {
> "name":"name",
> "dataTypeName":"string",
> "multiplicity":"required",
> "isComposite":false,
> "isUnique":false,
> "isIndexable":false,
> "reverseAttributeName":null
> }
> ]
> }
> ]
> }
> {noformat}
> 2. create an entity of above type
> {noformat}
> {
>
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
> "id":{
>
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "id":"-16993187400044476",
> "version":0,
> "typeName":"sample",
> "state":"ACTIVE"
> },
> "typeName":"sample",
> "values":{
> "name":"simple_column"
> },
> "traitNames":[
> ],
> "traits":{
> },
> "systemAttributes":{
> "createdBy":null,
> "modifiedBy":null,
> "createdTime":null,
> "modifiedTime":null
> }
> }
> {noformat}
> 3. Now perform a dsl search using below query - "query": "sample where name =
> \"sample_column\"",
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (ATLAS-1612) Regression: DSL search using a non-unique attribute of user-defined types results in empty response
[
https://issues.apache.org/jira/browse/ATLAS-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vimal Sharma resolved ATLAS-1612.
-
Resolution: Fixed
> Regression: DSL search using a non-unique attribute of user-defined types
> results in empty response
> ---
>
> Key: ATLAS-1612
> URL: https://issues.apache.org/jira/browse/ATLAS-1612
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: trunk, 0.8-incubating
>Reporter: Ayub Khan
>Assignee: Vimal Sharma
>Priority: Blocker
> Fix For: trunk, 0.8-incubating
>
>
> Steps to repro:
> 1. Create a user defined type like below
> {noformat}
> {
> "enumTypes":[
> ],
> "structTypes":[
> ],
> "traitTypes":[
> ],
> "classTypes":[
> {
> "superTypes":[
> ],
>
> "hierarchicalMetaTypeName":"org.apache.atlas.typesystem.types.ClassType",
> "typeName":"sample",
> "typeDescription":null,
> "typeVersion":"1.0",
> "attributeDefinitions":[
> {
> "name":"name",
> "dataTypeName":"string",
> "multiplicity":"required",
> "isComposite":false,
> "isUnique":false,
> "isIndexable":false,
> "reverseAttributeName":null
> }
> ]
> }
> ]
> }
> {noformat}
> 2. create an entity of above type
> {noformat}
> {
>
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
> "id":{
>
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "id":"-16993187400044476",
> "version":0,
> "typeName":"sample",
> "state":"ACTIVE"
> },
> "typeName":"sample",
> "values":{
> "name":"simple_column"
> },
> "traitNames":[
> ],
> "traits":{
> },
> "systemAttributes":{
> "createdBy":null,
> "modifiedBy":null,
> "createdTime":null,
> "modifiedTime":null
> }
> }
> {noformat}
> 3. Now perform a dsl search using below query - "query": "sample where name =
> \"sample_column\"",
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (ATLAS-1612) Regression: DSL search using a non-unique attribute of user-defined types results in empty response
[
https://issues.apache.org/jira/browse/ATLAS-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vimal Sharma reassigned ATLAS-1612:
---
Assignee: Vimal Sharma
> Regression: DSL search using a non-unique attribute of user-defined types
> results in empty response
> ---
>
> Key: ATLAS-1612
> URL: https://issues.apache.org/jira/browse/ATLAS-1612
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: trunk, 0.8-incubating
>Reporter: Ayub Khan
>Assignee: Vimal Sharma
>Priority: Blocker
> Fix For: trunk, 0.8-incubating
>
>
> Steps to repro:
> 1. Create a user defined type like below
> {noformat}
> {
> "enumTypes":[
> ],
> "structTypes":[
> ],
> "traitTypes":[
> ],
> "classTypes":[
> {
> "superTypes":[
> ],
>
> "hierarchicalMetaTypeName":"org.apache.atlas.typesystem.types.ClassType",
> "typeName":"sample",
> "typeDescription":null,
> "typeVersion":"1.0",
> "attributeDefinitions":[
> {
> "name":"name",
> "dataTypeName":"string",
> "multiplicity":"required",
> "isComposite":false,
> "isUnique":false,
> "isIndexable":false,
> "reverseAttributeName":null
> }
> ]
> }
> ]
> }
> {noformat}
> 2. create an entity of above type
> {noformat}
> {
>
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
> "id":{
>
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "id":"-16993187400044476",
> "version":0,
> "typeName":"sample",
> "state":"ACTIVE"
> },
> "typeName":"sample",
> "values":{
> "name":"simple_column"
> },
> "traitNames":[
> ],
> "traits":{
> },
> "systemAttributes":{
> "createdBy":null,
> "modifiedBy":null,
> "createdTime":null,
> "modifiedTime":null
> }
> }
> {noformat}
> 3. Now perform a dsl search using below query - "query": "sample where name =
> \"sample_column\"",
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (ATLAS-1572) sqoop metadata ingest fails with "org.apache.atlas.exception.AtlasBaseException: expected type List or Set; found org.apache.atlas.typesystem.Referenceable"
[
https://issues.apache.org/jira/browse/ATLAS-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vimal Sharma updated ATLAS-1572:
Attachment: ATLAS-1572.1.patch
Updating the patch to handle the issue on the server side. When an Object is
supplied to V1 to V2 Array converter, it handles the case where the given
Object is not a Collection.
> sqoop metadata ingest fails with
> "org.apache.atlas.exception.AtlasBaseException: expected type List or Set;
> found org.apache.atlas.typesystem.Referenceable"
>
>
> Key: ATLAS-1572
> URL: https://issues.apache.org/jira/browse/ATLAS-1572
> Project: Atlas
> Issue Type: Bug
> Components: atlas-intg
>Affects Versions: trunk, 0.8-incubating
>Reporter: Ayub Khan
>Assignee: Vimal Sharma
>Priority: Blocker
> Fix For: trunk, 0.8-incubating
>
> Attachments: ATLAS-1572.1.patch, ATLAS-1572.patch
>
>
> Sqoop import succeeds but the metadata ingest fails with below error
> {noformat}
> 2017-02-20 11:20:43,179 WARN - [NotificationHookConsumer thread-0:] ~ Max
> retries exceeded for message [{Id='(type: sqoop_dbdatastore, id:
> )', traits=[], values={owner=hrt_qa,
> storeUri=jdbc:mysql://ctr-e129-1487033772569-11862-01-02.hwx.site/sqoopTests?zeroDateTimeBehavior=convertToNull,
> dbStoreType=mysql, qualifiedName=mysql --url
> jdbc:mysql://ctr-e129-1487033772569-11862-01-02.hwx.site/sqoopTests?zeroDateTimeBehavior=convertToNull
> --table createSqoopTablejmnwwf8rji, name=mysql --url
> jdbc:mysql://ctr-e129-1487033772569-11862-01-02.hwx.site/sqoopTests?zeroDateTimeBehavior=convertToNull
> --table createSqoopTablejmnwwf8rji, description=,
> source=createSqoopTablejmnwwf8rji, storeUse=TABLE}}, {Id='(type: hive_db, id:
> )', traits=[], values={name=default, qualifiedName=default@cl1,
> clusterName=cl1}}, {Id='(type: hive_table, id: )', traits=[],
> values={name=createsqooptablejmnwwf8rji,
> qualifiedName=default.createsqooptablejmnwwf8rji@cl1, db={Id='(type: hive_db,
> id: )', traits=[], values={name=default,
> qualifiedName=default@cl1, clusterName=cl1, {Id='(type: sqoop_process,
> id: )', traits=[], values={outputs={Id='(type: hive_table, id:
> )', traits=[], values={name=createsqooptablejmnwwf8rji,
> qualifiedName=default.createsqooptablejmnwwf8rji@cl1, db={Id='(type: hive_db,
> id: )', traits=[], values={name=default,
> qualifiedName=default@cl1, clusterName=cl1,
> commandlineOpts={db.clear.staging.table=false, hive.import=true,
> db.require.password=true, codegen.output.delimiters.enclose=0,
> codegen.input.delimiters.field=0, customtool.options.jsonmap={},
> hive.compute.stats.table=false,
> db.connect.string=jdbc:mysql://ctr-e129-1487033772569-11862-01-02.hwx.site/sqoopTests?zeroDateTimeBehavior=convertToNull,
> incremental.mode=None, db.table=createSqoopTablejmnwwf8rji, verbose=false,
> codegen.output.delimiters.enclose.required=false, mapreduce.num.mappers=4,
> hdfs.append.dir=false, direct.import=false, hive.drop.delims=false,
> hive.overwrite.table=false, hbase.bulk.load.enabled=false,
> hive.fail.table.exists=false, relaxed.isolation=false,
> hdfs.delete-target.dir=false, split.limit=null, db.username=sqoop,
> codegen.input.delimiters.enclose.required=false, codegen.output.dir=.,
> import.direct.split.size=0, reset.onemapper=false,
> codegen.output.delimiters.record=10, temporary.dirRoot=_sqoop,
> hcatalog.create.table=false, db.batch=false, import.fetch.size=-2147483648,
> accumulo.max.latency=5000, hdfs.file.format=TextFile,
> codegen.output.delimiters.field=1, mainframe.input.dataset.type=p,
> codegen.output.delimiters.escape=0, hcatalog.drop.and.create.table=false,
> import.max.inline.lob.size=16777216, hbase.create.table=false,
> codegen.auto.compile.dir=true,
> codegen.compile.dir=/tmp/sqoop-hrt_qa/compile/f7c5181710812973a20a3e4776c5a6ef,
> codegen.input.delimiters.enclose=0, export.new.update=UpdateOnly,
> enable.compression=false, skip.dist.cache=false,
> accumulo.batch.size=1024, hdfs.warehouse.dir=/user/hrt_qa,
> codegen.input.delimiters.record=0, codegen.input.delimiters.escape=0,
> accumulo.create.table=false}, inputs={Id='(type: sqoop_dbdatastore, id:
> )', traits=[], values={owner=hrt_qa,
> storeUri=jdbc:mysql://ctr-e129-1487033772569-11862-01-02.hwx.site/sqoopTests?zeroDateTimeBehavior=convertToNull,
> dbStoreType=mysql, qualifiedName=mysql --url
> jdbc:mysql://ctr-e129-1487033772569-11862-01-02.hwx.site/sqoopTests?zeroDateTimeBehavior=convertToNull
> --table createSqoopTablejmnwwf8rji, name=mysql --url
> jdbc:mysql://ctr-e129-1487033772569-11862-01-02.hwx.site/sqoopTests?zeroDateTimeBehavior=convertToNull
> --table
[jira] [Created] (ATLAS-1599) Unit test failure in AuditRepositoryTestBase
Vimal Sharma created ATLAS-1599: --- Summary: Unit test failure in AuditRepositoryTestBase Key: ATLAS-1599 URL: https://issues.apache.org/jira/browse/ATLAS-1599 Project: Atlas Issue Type: Bug Reporter: Vimal Sharma Assignee: Vimal Sharma Unit tests in AuditRepositoryTestBase are failing. The reason being that although variable of interface EntityAuditRepository is declared but it is not initialized. This results in NullPointerException in all the UTs in this file -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ATLAS-1572) sqoop metadata ingest fails with "org.apache.atlas.exception.AtlasBaseException: expected type List or Set; found org.apache.atlas.typesystem.Referenceable"
[
https://issues.apache.org/jira/browse/ATLAS-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15885396#comment-15885396
]
Vimal Sharma commented on ATLAS-1572:
-
Function deserializeClassInstances in GraphHelper.java is the culprit. Added a
couple of LOG statements to debug the issue:
{code}
LOG.info("Deserialized JSON {}", entityInstance.toString());
ITypedReferenceableInstance typedInstrance =
getTypedReferenceableInstance(typeSystem, entityInstance);
LOG.info("ITypedReferenceable instance {}",
((ReferenceableInstance)typedInstrance).toString());
{code}
Got the below logs
{code}
2017-02-27 08:24:11,731 INFO - [NotificationHookConsumer thread-0:] ~
Deserialized JSON {Id='(type: sqoop_process, id: )', traits=[],
values={outputs={Id='(type: hive_table, id: )', traits=[],
values={name=sqoopregression,
qualifiedName=default.sqoopregression@Sqoop_Regression, db={Id='(type: hive_db,
id: )', traits=[], values={name=default,
qualifiedName=default@Sqoop_Regression, clusterName=Sqoop_Regression,
commandlineOpts={db.clear.staging.table=false, hive.import=true,
db.require.password=true, codegen.output.delimiters.enclose=0,
codegen.input.delimiters.field=0, customtool.options.jsonmap={},
hive.compute.stats.table=false,
db.connect.string=jdbc:mysql://sqoop-regression-1.openstacklocal/sqoopTest,
incremental.mode=None, db.table=sqoopRegression, verbose=false,
codegen.output.delimiters.enclose.required=false, mapreduce.num.mappers=1,
hdfs.append.dir=false, direct.import=false, hive.drop.delims=false,
hive.overwrite.table=false, hbase.bulk.load.enabled=false,
hive.fail.table.exists=false, relaxed.isolation=false,
hdfs.delete-target.dir=false, jdbc.driver.class=com.mysql.jdbc.Driver,
split.limit=null, db.username=sqoop,
codegen.input.delimiters.enclose.required=false, codegen.output.dir=.,
import.direct.split.size=0, reset.onemapper=false,
codegen.output.delimiters.record=10, temporary.dirRoot=_sqoop,
hcatalog.create.table=false, db.batch=false, import.fetch.size=1000,
accumulo.max.latency=5000, hdfs.file.format=TextFile,
codegen.output.delimiters.field=1, mainframe.input.dataset.type=p,
codegen.output.delimiters.escape=0, hcatalog.drop.and.create.table=false,
import.max.inline.lob.size=16777216, hbase.create.table=false,
codegen.auto.compile.dir=true,
codegen.compile.dir=/tmp/sqoop-hdfs/compile/ad793204f04ae1977f4abd2fc0715113,
codegen.input.delimiters.enclose=0, export.new.update=UpdateOnly,
enable.compression=false, skip.dist.cache=false, accumulo.batch.size=1024,
hdfs.warehouse.dir=/apps/hive/warehouse/, codegen.input.delimiters.record=0,
codegen.input.delimiters.escape=0, accumulo.create.table=false},
inputs={Id='(type: sqoop_dbdatastore, id: )', traits=[],
values={owner=hdfs,
storeUri=jdbc:mysql://sqoop-regression-1.openstacklocal/sqoopTest,
dbStoreType=mysql, qualifiedName=mysql --url
jdbc:mysql://sqoop-regression-1.openstacklocal/sqoopTest --table
sqoopRegression, name=mysql --url
jdbc:mysql://sqoop-regression-1.openstacklocal/sqoopTest --table
sqoopRegression, description=, source=sqoopRegression, storeUse=TABLE}},
qualifiedName=sqoop import --connect
jdbc:mysql://sqoop-regression-1.openstacklocal/sqoopTest --table
sqoopRegression --hive-import --hive-database default --hive-table
sqoopregression --hive-cluster Sqoop_Regression, name=sqoop import --connect
jdbc:mysql://sqoop-regression-1.openstacklocal/sqoopTest --table
sqoopRegression --hive-import --hive-database default --hive-table
sqoopregression --hive-cluster Sqoop_Regression,
startTime=2017-02-27T08:23:23.538Z, endTime=2017-02-27T08:24:07.007Z,
userName=hdfs, operation=import}} (GraphHelper:948)
2017-02-27 08:24:12,086 INFO - [NotificationHookConsumer thread-0:] ~
ITypedReferenceable instance {
id : (type: sqoop_process, id: )
operation : import
commandlineOpts : {accumulo.batch.size=1024,
accumulo.create.table=false, accumulo.max.latency=5000,
codegen.auto.compile.dir=true,
codegen.compile.dir=/tmp/sqoop-hdfs/compile/ad793204f04ae1977f4abd2fc0715113,
codegen.input.delimiters.enclose=0,
codegen.input.delimiters.enclose.required=false,
codegen.input.delimiters.escape=0, codegen.input.delimiters.field=0,
codegen.input.delimiters.record=0, codegen.output.delimiters.enclose=0,
codegen.output.delimiters.enclose.required=false,
codegen.output.delimiters.escape=0, codegen.output.delimiters.field=1,
codegen.output.delimiters.record=10, codegen.output.dir=.,
customtool.options.jsonmap={}, db.batch=false, db.clear.staging.table=false,
db.connect.string=jdbc:mysql://sqoop-regression-1.openstacklocal/sqoopTest,
db.require.password=true, db.table=sqoopRegression, db.username=sqoop,
direct.import=false, enable.compression=false, export.new.update=UpdateOnly,
hbase.bulk.load.enabled=false, hbase.create.table=false,
[jira] [Commented] (ATLAS-1572) sqoop metadata ingest fails with "org.apache.atlas.exception.AtlasBaseException: expected type List or Set; found org.apache.atlas.typesystem.Referenceable"
[
https://issues.apache.org/jira/browse/ATLAS-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15877525#comment-15877525
]
Vimal Sharma commented on ATLAS-1572:
-
[~madhan.neethiraj] The issue will be there only for the builds after the patch
for Hook notification rewiring https://issues.apache.org/jira/browse/ATLAS-1499.
It seems like the earlier Atlas server used to accept single value even though
the attribute was marked as list/set. I suspect that proper validation was not
present in the InstanceSerialization code where we convert Referenceable
objects to JSON string.
> sqoop metadata ingest fails with
> "org.apache.atlas.exception.AtlasBaseException: expected type List or Set;
> found org.apache.atlas.typesystem.Referenceable"
>
>
> Key: ATLAS-1572
> URL: https://issues.apache.org/jira/browse/ATLAS-1572
> Project: Atlas
> Issue Type: Bug
> Components: atlas-intg
>Affects Versions: trunk, 0.8-incubating
>Reporter: Ayub Khan
>Assignee: Vimal Sharma
>Priority: Blocker
> Fix For: trunk, 0.8-incubating
>
> Attachments: ATLAS-1572.patch
>
>
> Sqoop import succeeds but the metadata ingest fails with below error
> {noformat}
> 2017-02-20 11:20:43,179 WARN - [NotificationHookConsumer thread-0:] ~ Max
> retries exceeded for message [{Id='(type: sqoop_dbdatastore, id:
> )', traits=[], values={owner=hrt_qa,
> storeUri=jdbc:mysql://ctr-e129-1487033772569-11862-01-02.hwx.site/sqoopTests?zeroDateTimeBehavior=convertToNull,
> dbStoreType=mysql, qualifiedName=mysql --url
> jdbc:mysql://ctr-e129-1487033772569-11862-01-02.hwx.site/sqoopTests?zeroDateTimeBehavior=convertToNull
> --table createSqoopTablejmnwwf8rji, name=mysql --url
> jdbc:mysql://ctr-e129-1487033772569-11862-01-02.hwx.site/sqoopTests?zeroDateTimeBehavior=convertToNull
> --table createSqoopTablejmnwwf8rji, description=,
> source=createSqoopTablejmnwwf8rji, storeUse=TABLE}}, {Id='(type: hive_db, id:
> )', traits=[], values={name=default, qualifiedName=default@cl1,
> clusterName=cl1}}, {Id='(type: hive_table, id: )', traits=[],
> values={name=createsqooptablejmnwwf8rji,
> qualifiedName=default.createsqooptablejmnwwf8rji@cl1, db={Id='(type: hive_db,
> id: )', traits=[], values={name=default,
> qualifiedName=default@cl1, clusterName=cl1, {Id='(type: sqoop_process,
> id: )', traits=[], values={outputs={Id='(type: hive_table, id:
> )', traits=[], values={name=createsqooptablejmnwwf8rji,
> qualifiedName=default.createsqooptablejmnwwf8rji@cl1, db={Id='(type: hive_db,
> id: )', traits=[], values={name=default,
> qualifiedName=default@cl1, clusterName=cl1,
> commandlineOpts={db.clear.staging.table=false, hive.import=true,
> db.require.password=true, codegen.output.delimiters.enclose=0,
> codegen.input.delimiters.field=0, customtool.options.jsonmap={},
> hive.compute.stats.table=false,
> db.connect.string=jdbc:mysql://ctr-e129-1487033772569-11862-01-02.hwx.site/sqoopTests?zeroDateTimeBehavior=convertToNull,
> incremental.mode=None, db.table=createSqoopTablejmnwwf8rji, verbose=false,
> codegen.output.delimiters.enclose.required=false, mapreduce.num.mappers=4,
> hdfs.append.dir=false, direct.import=false, hive.drop.delims=false,
> hive.overwrite.table=false, hbase.bulk.load.enabled=false,
> hive.fail.table.exists=false, relaxed.isolation=false,
> hdfs.delete-target.dir=false, split.limit=null, db.username=sqoop,
> codegen.input.delimiters.enclose.required=false, codegen.output.dir=.,
> import.direct.split.size=0, reset.onemapper=false,
> codegen.output.delimiters.record=10, temporary.dirRoot=_sqoop,
> hcatalog.create.table=false, db.batch=false, import.fetch.size=-2147483648,
> accumulo.max.latency=5000, hdfs.file.format=TextFile,
> codegen.output.delimiters.field=1, mainframe.input.dataset.type=p,
> codegen.output.delimiters.escape=0, hcatalog.drop.and.create.table=false,
> import.max.inline.lob.size=16777216, hbase.create.table=false,
> codegen.auto.compile.dir=true,
> codegen.compile.dir=/tmp/sqoop-hrt_qa/compile/f7c5181710812973a20a3e4776c5a6ef,
> codegen.input.delimiters.enclose=0, export.new.update=UpdateOnly,
> enable.compression=false, skip.dist.cache=false,
> accumulo.batch.size=1024, hdfs.warehouse.dir=/user/hrt_qa,
> codegen.input.delimiters.record=0, codegen.input.delimiters.escape=0,
> accumulo.create.table=false}, inputs={Id='(type: sqoop_dbdatastore, id:
> )', traits=[], values={owner=hrt_qa,
> storeUri=jdbc:mysql://ctr-e129-1487033772569-11862-01-02.hwx.site/sqoopTests?zeroDateTimeBehavior=convertToNull,
> dbStoreType=mysql, qualifiedName=mysql --url
>
[jira] [Assigned] (ATLAS-1572) sqoop metadata ingest fails with "org.apache.atlas.exception.AtlasBaseException: expected type List or Set; found org.apache.atlas.typesystem.Referenceable"
[
https://issues.apache.org/jira/browse/ATLAS-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vimal Sharma reassigned ATLAS-1572:
---
Assignee: Vimal Sharma
> sqoop metadata ingest fails with
> "org.apache.atlas.exception.AtlasBaseException: expected type List or Set;
> found org.apache.atlas.typesystem.Referenceable"
>
>
> Key: ATLAS-1572
> URL: https://issues.apache.org/jira/browse/ATLAS-1572
> Project: Atlas
> Issue Type: Bug
> Components: atlas-intg
>Affects Versions: trunk, 0.8-incubating
>Reporter: Ayub Khan
>Assignee: Vimal Sharma
>Priority: Blocker
> Fix For: trunk, 0.8-incubating
>
> Attachments: ATLAS-1572.patch
>
>
> Sqoop import succeeds but the metadata ingest fails with below error
> {noformat}
> 2017-02-20 11:20:43,179 WARN - [NotificationHookConsumer thread-0:] ~ Max
> retries exceeded for message [{Id='(type: sqoop_dbdatastore, id:
> )', traits=[], values={owner=hrt_qa,
> storeUri=jdbc:mysql://ctr-e129-1487033772569-11862-01-02.hwx.site/sqoopTests?zeroDateTimeBehavior=convertToNull,
> dbStoreType=mysql, qualifiedName=mysql --url
> jdbc:mysql://ctr-e129-1487033772569-11862-01-02.hwx.site/sqoopTests?zeroDateTimeBehavior=convertToNull
> --table createSqoopTablejmnwwf8rji, name=mysql --url
> jdbc:mysql://ctr-e129-1487033772569-11862-01-02.hwx.site/sqoopTests?zeroDateTimeBehavior=convertToNull
> --table createSqoopTablejmnwwf8rji, description=,
> source=createSqoopTablejmnwwf8rji, storeUse=TABLE}}, {Id='(type: hive_db, id:
> )', traits=[], values={name=default, qualifiedName=default@cl1,
> clusterName=cl1}}, {Id='(type: hive_table, id: )', traits=[],
> values={name=createsqooptablejmnwwf8rji,
> qualifiedName=default.createsqooptablejmnwwf8rji@cl1, db={Id='(type: hive_db,
> id: )', traits=[], values={name=default,
> qualifiedName=default@cl1, clusterName=cl1, {Id='(type: sqoop_process,
> id: )', traits=[], values={outputs={Id='(type: hive_table, id:
> )', traits=[], values={name=createsqooptablejmnwwf8rji,
> qualifiedName=default.createsqooptablejmnwwf8rji@cl1, db={Id='(type: hive_db,
> id: )', traits=[], values={name=default,
> qualifiedName=default@cl1, clusterName=cl1,
> commandlineOpts={db.clear.staging.table=false, hive.import=true,
> db.require.password=true, codegen.output.delimiters.enclose=0,
> codegen.input.delimiters.field=0, customtool.options.jsonmap={},
> hive.compute.stats.table=false,
> db.connect.string=jdbc:mysql://ctr-e129-1487033772569-11862-01-02.hwx.site/sqoopTests?zeroDateTimeBehavior=convertToNull,
> incremental.mode=None, db.table=createSqoopTablejmnwwf8rji, verbose=false,
> codegen.output.delimiters.enclose.required=false, mapreduce.num.mappers=4,
> hdfs.append.dir=false, direct.import=false, hive.drop.delims=false,
> hive.overwrite.table=false, hbase.bulk.load.enabled=false,
> hive.fail.table.exists=false, relaxed.isolation=false,
> hdfs.delete-target.dir=false, split.limit=null, db.username=sqoop,
> codegen.input.delimiters.enclose.required=false, codegen.output.dir=.,
> import.direct.split.size=0, reset.onemapper=false,
> codegen.output.delimiters.record=10, temporary.dirRoot=_sqoop,
> hcatalog.create.table=false, db.batch=false, import.fetch.size=-2147483648,
> accumulo.max.latency=5000, hdfs.file.format=TextFile,
> codegen.output.delimiters.field=1, mainframe.input.dataset.type=p,
> codegen.output.delimiters.escape=0, hcatalog.drop.and.create.table=false,
> import.max.inline.lob.size=16777216, hbase.create.table=false,
> codegen.auto.compile.dir=true,
> codegen.compile.dir=/tmp/sqoop-hrt_qa/compile/f7c5181710812973a20a3e4776c5a6ef,
> codegen.input.delimiters.enclose=0, export.new.update=UpdateOnly,
> enable.compression=false, skip.dist.cache=false,
> accumulo.batch.size=1024, hdfs.warehouse.dir=/user/hrt_qa,
> codegen.input.delimiters.record=0, codegen.input.delimiters.escape=0,
> accumulo.create.table=false}, inputs={Id='(type: sqoop_dbdatastore, id:
> )', traits=[], values={owner=hrt_qa,
> storeUri=jdbc:mysql://ctr-e129-1487033772569-11862-01-02.hwx.site/sqoopTests?zeroDateTimeBehavior=convertToNull,
> dbStoreType=mysql, qualifiedName=mysql --url
> jdbc:mysql://ctr-e129-1487033772569-11862-01-02.hwx.site/sqoopTests?zeroDateTimeBehavior=convertToNull
> --table createSqoopTablejmnwwf8rji, name=mysql --url
> jdbc:mysql://ctr-e129-1487033772569-11862-01-02.hwx.site/sqoopTests?zeroDateTimeBehavior=convertToNull
> --table createSqoopTablejmnwwf8rji, description=,
> source=createSqoopTablejmnwwf8rji, storeUse=TABLE}}, qualifiedName=sqoop
> import --connect
>
[jira] [Updated] (ATLAS-1566) Use Jackson ObjectMapper for serialization and deserailization
[ https://issues.apache.org/jira/browse/ATLAS-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vimal Sharma updated ATLAS-1566: Attachment: ATLAS-1566.1.patch Attaching the patch. No additional test failures were observed with the patch > Use Jackson ObjectMapper for serialization and deserailization > -- > > Key: ATLAS-1566 > URL: https://issues.apache.org/jira/browse/ATLAS-1566 > Project: Atlas > Issue Type: Improvement >Reporter: Vimal Sharma >Assignee: Vimal Sharma > Fix For: 0.8-incubating > > Attachments: ATLAS-1566.1.patch > > > Currently, GSON is used for serialization and deserialization of AtlasType > POJOs at REST layer. ObjectMapper from Jackson library is used at other > places in the Atlas code. Use ObjectMapper in AtlasType to make the > serialization/deserialization consistent across Atlas code. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ATLAS-1565) Create EntityREST endpoints for delete operations
[ https://issues.apache.org/jira/browse/ATLAS-1565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15871656#comment-15871656 ] Vimal Sharma commented on ATLAS-1565: - Committed to master https://github.com/apache/incubator-atlas/commit/e4cc16ac7bd133964bf02eda360fe660d9225484 Thanks Sarath > Create EntityREST endpoints for delete operations > - > > Key: ATLAS-1565 > URL: https://issues.apache.org/jira/browse/ATLAS-1565 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 0.8-incubating >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian > Attachments: ATLAS-1565.1.patch > > > EntityREST delete endpoints need to hook to the v2 delete methods in v2 > entitiesStore. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1566) Use Jackson ObjectMapper for serialization and deserailization
[ https://issues.apache.org/jira/browse/ATLAS-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vimal Sharma updated ATLAS-1566: Issue Type: Improvement (was: Bug) > Use Jackson ObjectMapper for serialization and deserailization > -- > > Key: ATLAS-1566 > URL: https://issues.apache.org/jira/browse/ATLAS-1566 > Project: Atlas > Issue Type: Improvement >Reporter: Vimal Sharma >Assignee: Vimal Sharma > Fix For: 0.8-incubating > > > Currently, GSON is used for serialization and deserialization of AtlasType > POJOs at REST layer. ObjectMapper from Jackson library is used at other > places in the Atlas code. Use ObjectMapper in AtlasType to make the > serialization/deserialization consistent across Atlas code. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ATLAS-1566) Use Jackson ObjectMapper for serialization and deserailization
Vimal Sharma created ATLAS-1566: --- Summary: Use Jackson ObjectMapper for serialization and deserailization Key: ATLAS-1566 URL: https://issues.apache.org/jira/browse/ATLAS-1566 Project: Atlas Issue Type: Bug Reporter: Vimal Sharma Assignee: Vimal Sharma Fix For: 0.8-incubating Currently, GSON is used for serialization and deserialization of AtlasType POJOs at REST layer. ObjectMapper from Jackson library is used at other places in the Atlas code. Use ObjectMapper in AtlasType to make the serialization/deserialization consistent across Atlas code. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (ATLAS-1555) Move classification endpoint from Entities API to Entity API and remove Entities API
[ https://issues.apache.org/jira/browse/ATLAS-1555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vimal Sharma resolved ATLAS-1555. - Resolution: Fixed Committed to master https://github.com/apache/incubator-atlas/commit/2a93a6aa4090612c5c013037b40dfd687fc7f399 Thanks Madhan for review > Move classification endpoint from Entities API to Entity API and remove > Entities API > > > Key: ATLAS-1555 > URL: https://issues.apache.org/jira/browse/ATLAS-1555 > Project: Atlas > Issue Type: Improvement >Reporter: Vimal Sharma >Assignee: Vimal Sharma > Attachments: ATLAS-1555.patch > > > Entities API has a single method(API endpoint) to associate a classification > to multiple entities. > Move this classification endpoint from Entities API to Entity API and remove > Entities API -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1555) Move classification endpoint from Entities API to Entity API and remove Entities API
[ https://issues.apache.org/jira/browse/ATLAS-1555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vimal Sharma updated ATLAS-1555: Attachment: ATLAS-1555.patch > Move classification endpoint from Entities API to Entity API and remove > Entities API > > > Key: ATLAS-1555 > URL: https://issues.apache.org/jira/browse/ATLAS-1555 > Project: Atlas > Issue Type: Improvement >Reporter: Vimal Sharma >Assignee: Vimal Sharma > Attachments: ATLAS-1555.patch > > > Entities API has a single method(API endpoint) to associate a classification > to multiple entities. > Move this classification endpoint from Entities API to Entity API and remove > Entities API -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ATLAS-1555) Move classification endpoint from Entities API to Entity API and remove Entities API
Vimal Sharma created ATLAS-1555: --- Summary: Move classification endpoint from Entities API to Entity API and remove Entities API Key: ATLAS-1555 URL: https://issues.apache.org/jira/browse/ATLAS-1555 Project: Atlas Issue Type: Improvement Reporter: Vimal Sharma Assignee: Vimal Sharma Entities API has a single method(API endpoint) to associate a classification to multiple entities. Move this classification endpoint from Entities API to Entity API and remove Entities API -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1542) Atlas server fails to start if duplicate types are found during Typesystem bootstrap
[ https://issues.apache.org/jira/browse/ATLAS-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vimal Sharma updated ATLAS-1542: Affects Version/s: 0.8-incubating 0.7-incubating > Atlas server fails to start if duplicate types are found during Typesystem > bootstrap > > > Key: ATLAS-1542 > URL: https://issues.apache.org/jira/browse/ATLAS-1542 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.7-incubating, 0.8-incubating >Reporter: Vimal Sharma >Assignee: Vimal Sharma > Fix For: 0.8-incubating > > Attachments: ATLAS-1542.1.patch, ATLAS-1542.patch > > > When Atlas server is restarted, types in the existing typesystem are > bootstrapped from the underlying graph. When a duplicate type is > found(probably due to a stray vertex in the graph), Atlas server throws an > exception and server refuses to start. > Atlas server should log a warning when a duplicate type is encountered. The > server should come up normally without throwing an exception -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1542) Atlas server fails to start if duplicate types are found during Typesystem bootstrap
[ https://issues.apache.org/jira/browse/ATLAS-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vimal Sharma updated ATLAS-1542: Attachment: ATLAS-1542.1.patch > Atlas server fails to start if duplicate types are found during Typesystem > bootstrap > > > Key: ATLAS-1542 > URL: https://issues.apache.org/jira/browse/ATLAS-1542 > Project: Atlas > Issue Type: Bug >Reporter: Vimal Sharma >Assignee: Vimal Sharma > Fix For: 0.8-incubating > > Attachments: ATLAS-1542.1.patch, ATLAS-1542.patch > > > When Atlas server is restarted, types in the existing typesystem are > bootstrapped from the underlying graph. When a duplicate type is > found(probably due to a stray vertex in the graph), Atlas server throws an > exception and server refuses to start. > Atlas server should log a warning when a duplicate type is encountered. The > server should come up normally without throwing an exception -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1542) Atlas server fails to start if duplicate types are found during Typesystem bootstrap
[ https://issues.apache.org/jira/browse/ATLAS-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vimal Sharma updated ATLAS-1542: Attachment: ATLAS-1542.patch > Atlas server fails to start if duplicate types are found during Typesystem > bootstrap > > > Key: ATLAS-1542 > URL: https://issues.apache.org/jira/browse/ATLAS-1542 > Project: Atlas > Issue Type: Bug >Reporter: Vimal Sharma >Assignee: Vimal Sharma > Fix For: 0.8-incubating > > Attachments: ATLAS-1542.patch > > > When Atlas server is restarted, types in the existing typesystem are > bootstrapped from the underlying graph. When a duplicate type is > found(probably due to a stray vertex in the graph), Atlas server throws an > exception and server refuses to start. > Atlas server should log a warning when a duplicate type is encountered. The > server should come up normally without throwing an exception -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ATLAS-1542) Atlas server fails to start if duplicate types are found during Typesystem bootstrap
Vimal Sharma created ATLAS-1542: --- Summary: Atlas server fails to start if duplicate types are found during Typesystem bootstrap Key: ATLAS-1542 URL: https://issues.apache.org/jira/browse/ATLAS-1542 Project: Atlas Issue Type: Bug Reporter: Vimal Sharma Assignee: Vimal Sharma Fix For: 0.8-incubating When Atlas server is restarted, types in the existing typesystem are bootstrapped from the underlying graph. When a duplicate type is found(probably due to a stray vertex in the graph), Atlas server throws an exception and server refuses to start. Atlas server should log a warning when a duplicate type is encountered. The server should come up normally without throwing an exception -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ATLAS-1499) notification processing to use new instance API for create and full-update
Vimal Sharma created ATLAS-1499: --- Summary: notification processing to use new instance API for create and full-update Key: ATLAS-1499 URL: https://issues.apache.org/jira/browse/ATLAS-1499 Project: Atlas Issue Type: Bug Reporter: Vimal Sharma Assignee: Vimal Sharma Fix For: 0.8-incubating Atlas Server notifies the entity change listeners(NotificationEntityChangeListener, EntityAuditListener) after any create/update operation on entities. The create/update routines have been changed in ATLAS-1467. The corresponding changes are required in notification processing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-1499) Notification processing to use new instance API for create and full-update
[ https://issues.apache.org/jira/browse/ATLAS-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vimal Sharma updated ATLAS-1499: Summary: Notification processing to use new instance API for create and full-update (was: notification processing to use new instance API for create and full-update) > Notification processing to use new instance API for create and full-update > -- > > Key: ATLAS-1499 > URL: https://issues.apache.org/jira/browse/ATLAS-1499 > Project: Atlas > Issue Type: Bug >Reporter: Vimal Sharma >Assignee: Vimal Sharma > Fix For: 0.8-incubating > > > Atlas Server notifies the entity change > listeners(NotificationEntityChangeListener, EntityAuditListener) after any > create/update operation on entities. > The create/update routines have been changed in ATLAS-1467. The corresponding > changes are required in notification processing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1494) Data models of types inheriting Process have Inputs,Outputs which are of very generic type.
[ https://issues.apache.org/jira/browse/ATLAS-1494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15834206#comment-15834206 ] Vimal Sharma commented on ATLAS-1494: - [~ssainath] I think this is by design. Types inheriting from type Process can connect cross component entities. For example, type "storm_topology" inherits from "Process" and its inputs/outputs can be entities of type "hive_table", "kafka_spout", "hdfs_path". Imposing constraints on "inputs" and "outputs" of types derived from "Process" sounds reasonable and needs discussion. As you mentioned, we can consider imposing additional constraints on derived types like "falcon_process" to allow specific types in "inputs/outputs". > Data models of types inheriting Process have Inputs,Outputs which are of very > generic type. > > > Key: ATLAS-1494 > URL: https://issues.apache.org/jira/browse/ATLAS-1494 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Sharmadha Sainath > > Types which are inheriting from Process have Inputs,Outputs as attributes of > datatype array which is very generic. For example, falcon_process' > input and output should be falcon_feed. In case of generic DataSet , input > and output can be any DataSet like hive_table, hbase_column_family , > jms_topic etc., which is faulty when associated to the falcon_process. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-1478) REST API endpoint to support adding a tag to multiple entities
[ https://issues.apache.org/jira/browse/ATLAS-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vimal Sharma updated ATLAS-1478: Attachment: ATLAS-1478-v2.patch Fixed review comments > REST API endpoint to support adding a tag to multiple entities > -- > > Key: ATLAS-1478 > URL: https://issues.apache.org/jira/browse/ATLAS-1478 > Project: Atlas > Issue Type: Bug >Reporter: Vimal Sharma >Assignee: Vimal Sharma > Fix For: 0.8-incubating > > Attachments: ATLAS-1478.patch, ATLAS-1478-v2.patch > > > Currently, there is no REST endpoint to add a tag to multiple entities. Add a > REST endpoint in V2 APIs to support adding a tag to multiple entities in a > single call. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-1478) REST API endpoint to support adding a tag to multiple entities
[ https://issues.apache.org/jira/browse/ATLAS-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vimal Sharma updated ATLAS-1478: Attachment: ATLAS-1478.patch > REST API endpoint to support adding a tag to multiple entities > -- > > Key: ATLAS-1478 > URL: https://issues.apache.org/jira/browse/ATLAS-1478 > Project: Atlas > Issue Type: Bug >Reporter: Vimal Sharma >Assignee: Vimal Sharma > Fix For: 0.8-incubating > > Attachments: ATLAS-1478.patch > > > Currently, there is no REST endpoint to add a tag to multiple entities. Add a > REST endpoint in V2 APIs to support adding a tag to multiple entities in a > single call. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-1478) REST API endpoint to support adding a tag to multiple entities
Vimal Sharma created ATLAS-1478: --- Summary: REST API endpoint to support adding a tag to multiple entities Key: ATLAS-1478 URL: https://issues.apache.org/jira/browse/ATLAS-1478 Project: Atlas Issue Type: Bug Reporter: Vimal Sharma Assignee: Vimal Sharma Fix For: 0.8-incubating Currently, there is no REST endpoint to add a tag to multiple entities. Add a REST endpoint in V2 APIs to support adding a tag to multiple entities in a single call. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1472) Atlas went into irrecoverable state after creating 2 tags with same name accidentally.
[ https://issues.apache.org/jira/browse/ATLAS-1472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15827607#comment-15827607 ] Vimal Sharma commented on ATLAS-1472: - [~ssainath] Is it an old build. If yes, can you please try with a fresh build > Atlas went into irrecoverable state after creating 2 tags with same name > accidentally. > -- > > Key: ATLAS-1472 > URL: https://issues.apache.org/jira/browse/ATLAS-1472 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Sharmadha Sainath >Priority: Critical > Attachments: redefine_tag_exception.txt > > > Atlas was slow and while creating a tag , I clicked "create" button twice > which created the same tag twice. From then on , no queries are working. > Attaching the exception stack trace. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1472) Atlas went into irrecoverable state after creating 2 tags with same name accidentally.
[
https://issues.apache.org/jira/browse/ATLAS-1472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15827602#comment-15827602
]
Vimal Sharma commented on ATLAS-1472:
-
[~ssainath] I tried to reproduce the error but Atlas doesn't go into
irrecoverable state. I get the below exception when trying to create second tag
with the same name :
{code}
2017-01-18 13:46:26,763 ERROR - [qtp785451259-27 -
16574858-7c51-496f-8874-5750cd4810c8:] ~ graph rollback due to exception
(GraphTransactionInterceptor:58)
org.apache.atlas.exception.AtlasBaseException: Given type Sample already exists
at
org.apache.atlas.repository.store.graph.v1.AtlasClassificationDefStoreV1.preCreate(AtlasClassificationDefStoreV1.java:71)
at
org.apache.atlas.repository.store.graph.v1.AtlasClassificationDefStoreV1.create(AtlasClassificationDefStoreV1.java:95)
at
org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore.createClassificationDef(AtlasTypeDefGraphStore.java:335)
at
org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:51)
at
org.apache.atlas.web.rest.TypesREST.createClassificationDef(TypesREST.java:228)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
at
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185)
at
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
at
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
at
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
at
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
at
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
at
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
at
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
at
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
at
com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
at
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
at
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at
com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:286)
at
com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:276)
at
com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:181)
at
com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)
at
com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:85)
at
org.apache.atlas.web.filters.AuditFilter.doFilter(AuditFilter.java:77)
at
com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)
at
com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:120)
at com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:135)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
at
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330)
at
org.apache.atlas.web.filters.AtlasAuthorizationFilter.doFilter(AtlasAuthorizationFilter.java:154)
at
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
at
org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:118)
at
org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:84)
at
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
[jira] [Updated] (ATLAS-1460) V2 Search API results don't contain attributes like name, description, owner and Traitslist
[ https://issues.apache.org/jira/browse/ATLAS-1460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vimal Sharma updated ATLAS-1460: Attachment: ATLAS-1460.v2.patch Thanks [~sarath.ku...@gmail.com] for the review. Updated the patch to address the review comments > V2 Search API results don't contain attributes like name, description, owner > and Traitslist > --- > > Key: ATLAS-1460 > URL: https://issues.apache.org/jira/browse/ATLAS-1460 > Project: Atlas > Issue Type: Bug >Reporter: Vimal Sharma >Assignee: Vimal Sharma > Fix For: 0.8-incubating > > Attachments: ATLAS-1460.patch, ATLAS-1460.v2.patch > > > DSL and FullText Search results don't contain attributes specific to an > entity like name, description, owner and list of associated traits -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1391) Add exclusion mechanism for Atlas audit mechanism
[ https://issues.apache.org/jira/browse/ATLAS-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15820327#comment-15820327 ] Vimal Sharma commented on ATLAS-1391: - +1 for the new 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 > Fix For: 0.8-incubating > > Attachments: rb54907(1).patch, rb55227.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] [Commented] (ATLAS-1280) Atlas changes to support Hive hook for Hive2
[ https://issues.apache.org/jira/browse/ATLAS-1280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15820293#comment-15820293 ] Vimal Sharma commented on ATLAS-1280: - +1 for the patch > Atlas changes to support Hive hook for Hive2 > > > Key: ATLAS-1280 > URL: https://issues.apache.org/jira/browse/ATLAS-1280 > Project: Atlas > Issue Type: Bug >Reporter: Vimal Sharma >Assignee: Vimal Sharma > Attachments: ATLAS-1280-v1.patch, ATLAS-1280.patch > > > Atlas is currently built with Hive version 1.2 > Due to significant changes in Hive2(LLAP), some changes are required in Atlas > Hive Hook code to ensure that hook works correctly -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-1280) Atlas changes to support Hive hook for Hive2
[ https://issues.apache.org/jira/browse/ATLAS-1280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vimal Sharma updated ATLAS-1280: Attachment: ATLAS-1280-v1.patch Attaching patch from [~madhan.neethiraj] > Atlas changes to support Hive hook for Hive2 > > > Key: ATLAS-1280 > URL: https://issues.apache.org/jira/browse/ATLAS-1280 > Project: Atlas > Issue Type: Bug >Reporter: Vimal Sharma >Assignee: Vimal Sharma > Attachments: ATLAS-1280-v1.patch, ATLAS-1280.patch > > > Atlas is currently built with Hive version 1.2 > Due to significant changes in Hive2(LLAP), some changes are required in Atlas > Hive Hook code to ensure that hook works correctly -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-1280) Atlas changes to support Hive hook for Hive2
[ https://issues.apache.org/jira/browse/ATLAS-1280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vimal Sharma updated ATLAS-1280: Description: Atlas is currently built with Hive version 1.2 Due to significant changes in Hive2(LLAP), some changes are required in Atlas Hive Hook code to ensure that hook works correctly was: Atlas is currently built with Hive version 1.2 Due to significant changes in Hive2(LLAP), it might be useful to build Atlas using the Hive 2.1.0 release. > Atlas changes to support Hive hook for Hive2 > > > Key: ATLAS-1280 > URL: https://issues.apache.org/jira/browse/ATLAS-1280 > Project: Atlas > Issue Type: Bug >Reporter: Vimal Sharma >Assignee: Vimal Sharma > Attachments: ATLAS-1280.patch > > > Atlas is currently built with Hive version 1.2 > Due to significant changes in Hive2(LLAP), some changes are required in Atlas > Hive Hook code to ensure that hook works correctly -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-1280) Atlas changes to support Hive hook for Hive2
[ https://issues.apache.org/jira/browse/ATLAS-1280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vimal Sharma updated ATLAS-1280: Summary: Atlas changes to support Hive hook for Hive2 (was: Build Atlas with Hive2) > Atlas changes to support Hive hook for Hive2 > > > Key: ATLAS-1280 > URL: https://issues.apache.org/jira/browse/ATLAS-1280 > Project: Atlas > Issue Type: Bug >Reporter: Vimal Sharma >Assignee: Vimal Sharma > Attachments: ATLAS-1280.patch > > > Atlas is currently built with Hive version 1.2 > Due to significant changes in Hive2(LLAP), it might be useful to build Atlas > using the Hive 2.1.0 release. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1442) Update pom.xml to change version number to 0.7.1-incubating
[ https://issues.apache.org/jira/browse/ATLAS-1442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15817656#comment-15817656 ] Vimal Sharma commented on ATLAS-1442: - +1 for patch > Update pom.xml to change version number to 0.7.1-incubating > --- > > Key: ATLAS-1442 > URL: https://issues.apache.org/jira/browse/ATLAS-1442 > Project: Atlas > Issue Type: Sub-task > Components: atlas-core >Affects Versions: 0.7.1-incubating >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj > Fix For: 0.7.1-incubating > > Attachments: ATLAS-1442.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-1396) [V2 API] GET v2/types/{type}/guid/{guid} not working
[
https://issues.apache.org/jira/browse/ATLAS-1396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vimal Sharma updated ATLAS-1396:
Summary: [V2 API] GET v2/types/{type}/guid/{guid} not working (was: [V2
API] GET v2/types/enumdef/guid/{guid} not working as expected)
> [V2 API] GET v2/types/{type}/guid/{guid} not working
>
>
> Key: ATLAS-1396
> URL: https://issues.apache.org/jira/browse/ATLAS-1396
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: Vimal Sharma
>Assignee: Vimal Sharma
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1396.patch
>
>
> POST v2/types/enumdef
> {
> "name" : "creation_order1",
> "typeVersion" : "1.1",
> "elementDefs" : [
> {
> "ordinal" : 1,
> "value" : "PRE"
> },
> {
> "ordinal" : 2,
> "value" : "POST"
> },
> {
> "ordinal" : 3,
> "value" : "UNKNOWN"
> }
> ]
> }
> returns the response
> {
> "category": "ENUM",
> "guid": "c5642d55-9f8e-45b1-b4a9-709c97b46233",
> "createTime": 1481885315377,
> "updateTime": 1481885315377,
> "version": 1,
> "name": "creation_order1",
> "description": "creation_order1",
> "typeVersion": "1.1",
> "elementDefs": [
> {
> "value": "PRE",
> "ordinal": 1
> },
> {
> "value": "POST",
> "ordinal": 2
> },
> {
> "value": "UNKNOWN",
> "ordinal": 3
> }
> ]
> }
> But GET v2/types/enumdef/guid/c5642d55-9f8e-45b1-b4a9-709c97b46233 returns
> {
> "errorCode": "ATLAS4042E",
> "errorMessage": "Given type guid c5642d55-9f8e-45b1-b4a9-709c97b46233 was
> invalid"
> }
> GET v2/types/enumdef/name/creation_order1 returns
> {
> "category": "ENUM",
> "guid": "c5642d55-9f8e-45b1-b4a9-709c97b46233",
> "createTime": 1481885315377,
> "updateTime": 1481885315377,
> "version": 1,
> "name": "creation_order1",
> "typeVersion": "1.1",
> "elementDefs": [
> {
> "value": "PRE",
> "ordinal": 1
> },
> {
> "value": "POST",
> "ordinal": 2
> },
> {
> "value": "UNKNOWN",
> "ordinal": 3
> }
> ]
> }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-1396) [V2 API] GET v2/types/enumdef/guid/{guid} not working as expected
[
https://issues.apache.org/jira/browse/ATLAS-1396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vimal Sharma updated ATLAS-1396:
Attachment: ATLAS-1396.patch
> [V2 API] GET v2/types/enumdef/guid/{guid} not working as expected
> --
>
> Key: ATLAS-1396
> URL: https://issues.apache.org/jira/browse/ATLAS-1396
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: Vimal Sharma
>Assignee: Vimal Sharma
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1396.patch
>
>
> POST v2/types/enumdef
> {
> "name" : "creation_order1",
> "typeVersion" : "1.1",
> "elementDefs" : [
> {
> "ordinal" : 1,
> "value" : "PRE"
> },
> {
> "ordinal" : 2,
> "value" : "POST"
> },
> {
> "ordinal" : 3,
> "value" : "UNKNOWN"
> }
> ]
> }
> returns the response
> {
> "category": "ENUM",
> "guid": "c5642d55-9f8e-45b1-b4a9-709c97b46233",
> "createTime": 1481885315377,
> "updateTime": 1481885315377,
> "version": 1,
> "name": "creation_order1",
> "description": "creation_order1",
> "typeVersion": "1.1",
> "elementDefs": [
> {
> "value": "PRE",
> "ordinal": 1
> },
> {
> "value": "POST",
> "ordinal": 2
> },
> {
> "value": "UNKNOWN",
> "ordinal": 3
> }
> ]
> }
> But GET v2/types/enumdef/guid/c5642d55-9f8e-45b1-b4a9-709c97b46233 returns
> {
> "errorCode": "ATLAS4042E",
> "errorMessage": "Given type guid c5642d55-9f8e-45b1-b4a9-709c97b46233 was
> invalid"
> }
> GET v2/types/enumdef/name/creation_order1 returns
> {
> "category": "ENUM",
> "guid": "c5642d55-9f8e-45b1-b4a9-709c97b46233",
> "createTime": 1481885315377,
> "updateTime": 1481885315377,
> "version": 1,
> "name": "creation_order1",
> "typeVersion": "1.1",
> "elementDefs": [
> {
> "value": "PRE",
> "ordinal": 1
> },
> {
> "value": "POST",
> "ordinal": 2
> },
> {
> "value": "UNKNOWN",
> "ordinal": 3
> }
> ]
> }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-1396) [V2 API] GET v2/types/enumdef/guid/{guid} not working as expected
[
https://issues.apache.org/jira/browse/ATLAS-1396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vimal Sharma updated ATLAS-1396:
Attachment: (was: ATLAS-1396.patch)
> [V2 API] GET v2/types/enumdef/guid/{guid} not working as expected
> --
>
> Key: ATLAS-1396
> URL: https://issues.apache.org/jira/browse/ATLAS-1396
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: Vimal Sharma
>Assignee: Vimal Sharma
> Fix For: 0.8-incubating
>
>
> POST v2/types/enumdef
> {
> "name" : "creation_order1",
> "typeVersion" : "1.1",
> "elementDefs" : [
> {
> "ordinal" : 1,
> "value" : "PRE"
> },
> {
> "ordinal" : 2,
> "value" : "POST"
> },
> {
> "ordinal" : 3,
> "value" : "UNKNOWN"
> }
> ]
> }
> returns the response
> {
> "category": "ENUM",
> "guid": "c5642d55-9f8e-45b1-b4a9-709c97b46233",
> "createTime": 1481885315377,
> "updateTime": 1481885315377,
> "version": 1,
> "name": "creation_order1",
> "description": "creation_order1",
> "typeVersion": "1.1",
> "elementDefs": [
> {
> "value": "PRE",
> "ordinal": 1
> },
> {
> "value": "POST",
> "ordinal": 2
> },
> {
> "value": "UNKNOWN",
> "ordinal": 3
> }
> ]
> }
> But GET v2/types/enumdef/guid/c5642d55-9f8e-45b1-b4a9-709c97b46233 returns
> {
> "errorCode": "ATLAS4042E",
> "errorMessage": "Given type guid c5642d55-9f8e-45b1-b4a9-709c97b46233 was
> invalid"
> }
> GET v2/types/enumdef/name/creation_order1 returns
> {
> "category": "ENUM",
> "guid": "c5642d55-9f8e-45b1-b4a9-709c97b46233",
> "createTime": 1481885315377,
> "updateTime": 1481885315377,
> "version": 1,
> "name": "creation_order1",
> "typeVersion": "1.1",
> "elementDefs": [
> {
> "value": "PRE",
> "ordinal": 1
> },
> {
> "value": "POST",
> "ordinal": 2
> },
> {
> "value": "UNKNOWN",
> "ordinal": 3
> }
> ]
> }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-1396) [V2 API] GET v2/types/enumdef/guid/{guid} not working as expected
[
https://issues.apache.org/jira/browse/ATLAS-1396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vimal Sharma updated ATLAS-1396:
Attachment: ATLAS-1396.patch
The same issue as mentioned in the description was occurring for StructType,
ClassificationType and EntityType as well.
The attached patch fixes the issue. Verified using Postman client
> [V2 API] GET v2/types/enumdef/guid/{guid} not working as expected
> --
>
> Key: ATLAS-1396
> URL: https://issues.apache.org/jira/browse/ATLAS-1396
> Project: Atlas
> Issue Type: Bug
>Reporter: Vimal Sharma
>Assignee: Vimal Sharma
> Attachments: ATLAS-1396.patch
>
>
> POST v2/types/enumdef
> {
> "name" : "creation_order1",
> "typeVersion" : "1.1",
> "elementDefs" : [
> {
> "ordinal" : 1,
> "value" : "PRE"
> },
> {
> "ordinal" : 2,
> "value" : "POST"
> },
> {
> "ordinal" : 3,
> "value" : "UNKNOWN"
> }
> ]
> }
> returns the response
> {
> "category": "ENUM",
> "guid": "c5642d55-9f8e-45b1-b4a9-709c97b46233",
> "createTime": 1481885315377,
> "updateTime": 1481885315377,
> "version": 1,
> "name": "creation_order1",
> "description": "creation_order1",
> "typeVersion": "1.1",
> "elementDefs": [
> {
> "value": "PRE",
> "ordinal": 1
> },
> {
> "value": "POST",
> "ordinal": 2
> },
> {
> "value": "UNKNOWN",
> "ordinal": 3
> }
> ]
> }
> But GET v2/types/enumdef/guid/c5642d55-9f8e-45b1-b4a9-709c97b46233 returns
> {
> "errorCode": "ATLAS4042E",
> "errorMessage": "Given type guid c5642d55-9f8e-45b1-b4a9-709c97b46233 was
> invalid"
> }
> GET v2/types/enumdef/name/creation_order1 returns
> {
> "category": "ENUM",
> "guid": "c5642d55-9f8e-45b1-b4a9-709c97b46233",
> "createTime": 1481885315377,
> "updateTime": 1481885315377,
> "version": 1,
> "name": "creation_order1",
> "typeVersion": "1.1",
> "elementDefs": [
> {
> "value": "PRE",
> "ordinal": 1
> },
> {
> "value": "POST",
> "ordinal": 2
> },
> {
> "value": "UNKNOWN",
> "ordinal": 3
> }
> ]
> }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ATLAS-1432) Responsive Loader and css changes
[ https://issues.apache.org/jira/browse/ATLAS-1432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15814135#comment-15814135 ] Vimal Sharma commented on ATLAS-1432: - +1 for the patch > Responsive Loader and css changes > - > > Key: ATLAS-1432 > URL: https://issues.apache.org/jira/browse/ATLAS-1432 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.7-incubating >Reporter: Keval Bhatt >Assignee: Keval Bhatt > Fix For: 0.7.1-incubating > > Attachments: ATLAS-1432.1.patch, ATLAS-1432.patch > > > Showing loader sign for all crud operation of entity,Tag and search to make > the user experience smooth. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1427) Support an option to exclude protocols in SSL mode
[ https://issues.apache.org/jira/browse/ATLAS-1427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15811018#comment-15811018 ] Vimal Sharma commented on ATLAS-1427: - +1 for fix for test failures > Support an option to exclude protocols in SSL mode > -- > > Key: ATLAS-1427 > URL: https://issues.apache.org/jira/browse/ATLAS-1427 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 0.8-incubating >Reporter: Madhan Neethiraj >Assignee: Nixon Rodrigues > Fix For: 0.8-incubating, 0.7.1-incubating > > Attachments: ATLAS-1427-0.7-incubating.patch, ATLAS-1427.1.patch, > ATLAS-1427.patch > > > Atlas server should support an option to exclude protocols in SSL mode, which > can be used to disable less secure protocols like TLSv1, TLSv1.1. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ATLAS-1422) test
[ https://issues.apache.org/jira/browse/ATLAS-1422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vimal Sharma resolved ATLAS-1422. - Resolution: Invalid > test > > > Key: ATLAS-1422 > URL: https://issues.apache.org/jira/browse/ATLAS-1422 > Project: Atlas > Issue Type: Bug >Reporter: Varsha > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ATLAS-1409) Entity creation for a new type
[
https://issues.apache.org/jira/browse/ATLAS-1409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vimal Sharma resolved ATLAS-1409.
-
Resolution: Not A Bug
Thanks Nixon for the suggestion. Closing as this is not an issue
> Entity creation for a new type
> --
>
> Key: ATLAS-1409
> URL: https://issues.apache.org/jira/browse/ATLAS-1409
> Project: Atlas
> Issue Type: Bug
>Reporter: Vimal Sharma
>
> I created a "spark_dataframe" type using POST
> POST /v2/types/entitydef
> {
> "name": "spark_dataframe",
> "superTypes": [
> "DataSet"
> ],
> "typeVersion": "1.0",
> "attributeDefs": [
> {
> "name": "source",
> "typeName": "string",
> "cardinality": "SINGLE",
> "isIndexable": false,
> "isOptional": false,
> "isUnique": false
> },
> {
> "name": "destination",
> "typeName": "string",
> "cardinality": "SINGLE",
> "isIndexable": false,
> "isOptional": true,
> "isUnique": false
> }
> ]
> }
> But when I try to create an entity using the request
> POST v2/entity/
> {
> "typeName": "spark_dataframe",
> "attributes" : {
> "source" :
> "hdfs://vimal-fenton-4-1.openstacklocal:8020/apps/hive/warehouse/source",
> "destination" :
> "hdfs://vimal-fenton-4-1.openstacklocal:8020/apps/hive/warehouse/destination"
> },
> "classifications": [
>
> ]
> }
> The server throws a type not found exception
> 2016-12-21 10:45:44,388 ERROR - [pool-2-thread-4 -
> b00d8b4a-6ba5-416f-9186-1fff2c9b4e3b:] ~ Exception while getting a typed
> reference for the entity (AtlasInstanceRestAdapters:82)
> org.apache.atlas.typesystem.exception.TypeNotFoundException: Unknown
> datatype: spark_dataframe
> at
> org.apache.atlas.typesystem.types.TypeSystem.getDataType(TypeSystem.java:192)
> at
> org.apache.atlas.repository.graph.GraphHelper.getTypedReferenceableInstance(GraphHelper.java:730)
> at
> org.apache.atlas.services.DefaultMetadataService.getTypedReferenceableInstance(DefaultMetadataService.java:285)
> at
> org.apache.atlas.web.adapters.AtlasInstanceRestAdapters.getITypedReferenceable(AtlasInstanceRestAdapters.java:80)
> at
> org.apache.atlas.web.adapters.AtlasInstanceRestAdapters.getITypedReferenceables(AtlasInstanceRestAdapters.java:67)
> at
> org.apache.atlas.web.rest.EntityREST.createOrUpdate(EntityREST.java:91)
> at sun.reflect.GeneratedMethodAccessor150.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185)
> at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
> at
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> at
> com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:286)
> at
> com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:276)
> at
> com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:181)
> at
> com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)
> at
>
[jira] [Created] (ATLAS-1409) Entity creation for a new type
Vimal Sharma created ATLAS-1409:
---
Summary: Entity creation for a new type
Key: ATLAS-1409
URL: https://issues.apache.org/jira/browse/ATLAS-1409
Project: Atlas
Issue Type: Bug
Reporter: Vimal Sharma
I created a "spark_dataframe" type using POST
POST /v2/types/entitydef
{
"name": "spark_dataframe",
"superTypes": [
"DataSet"
],
"typeVersion": "1.0",
"attributeDefs": [
{
"name": "source",
"typeName": "string",
"cardinality": "SINGLE",
"isIndexable": false,
"isOptional": false,
"isUnique": false
},
{
"name": "destination",
"typeName": "string",
"cardinality": "SINGLE",
"isIndexable": false,
"isOptional": true,
"isUnique": false
}
]
}
But when I try to create an entity using the request
POST v2/entity/
{
"typeName": "spark_dataframe",
"attributes" : {
"source" :
"hdfs://vimal-fenton-4-1.openstacklocal:8020/apps/hive/warehouse/source",
"destination" :
"hdfs://vimal-fenton-4-1.openstacklocal:8020/apps/hive/warehouse/destination"
},
"classifications": [
]
}
The server throws a type not found exception
2016-12-21 10:45:44,388 ERROR - [pool-2-thread-4 -
b00d8b4a-6ba5-416f-9186-1fff2c9b4e3b:] ~ Exception while getting a typed
reference for the entity (AtlasInstanceRestAdapters:82)
org.apache.atlas.typesystem.exception.TypeNotFoundException: Unknown datatype:
spark_dataframe
at
org.apache.atlas.typesystem.types.TypeSystem.getDataType(TypeSystem.java:192)
at
org.apache.atlas.repository.graph.GraphHelper.getTypedReferenceableInstance(GraphHelper.java:730)
at
org.apache.atlas.services.DefaultMetadataService.getTypedReferenceableInstance(DefaultMetadataService.java:285)
at
org.apache.atlas.web.adapters.AtlasInstanceRestAdapters.getITypedReferenceable(AtlasInstanceRestAdapters.java:80)
at
org.apache.atlas.web.adapters.AtlasInstanceRestAdapters.getITypedReferenceables(AtlasInstanceRestAdapters.java:67)
at
org.apache.atlas.web.rest.EntityREST.createOrUpdate(EntityREST.java:91)
at sun.reflect.GeneratedMethodAccessor150.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
at
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185)
at
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
at
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
at
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
at
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
at
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
at
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
at
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
at
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
at
com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
at
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
at
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at
com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:286)
at
com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:276)
at
com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:181)
at
com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)
at
com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:85)
at
org.apache.atlas.web.filters.AuditFilter.doFilter(AuditFilter.java:71)
at
com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)
at
com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:120)
at
[jira] [Updated] (ATLAS-1399) [V2 API] PUT /v2/types/structdef/guid/{guid} fails while PUT /v2/types/structdef/name/{structGUID} suceeds
[
https://issues.apache.org/jira/browse/ATLAS-1399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vimal Sharma updated ATLAS-1399:
Issue Type: Bug (was: Improvement)
> [V2 API] PUT /v2/types/structdef/guid/{guid} fails while PUT
> /v2/types/structdef/name/{structGUID} suceeds
> --
>
> Key: ATLAS-1399
> URL: https://issues.apache.org/jira/browse/ATLAS-1399
> Project: Atlas
> Issue Type: Bug
>Reporter: Vimal Sharma
>
> For the below JSON
> {
> "category": "STRUCT",
> "guid": "9527b5c2-49f7-4e25-bab0-a352d58fc2bf",
> "createTime": 1481887151201,
> "updateTime": 1481887819834,
> "version": 3,
> "name": "table_creation_order",
> "description": "table_creation_order",
> "typeVersion": "1.0",
> "attributeDefs": [
> {
> "name": "order",
> "typeName": "int",
> "isOptional": false,
> "cardinality": "SINGLE",
> "valuesMinCount": 1,
> "valuesMaxCount": 1,
> "isUnique": false,
> "isIndexable": false
> },
> {
> "name": "tablename",
> "typeName": "string",
> "isOptional": false,
> "cardinality": "SINGLE",
> "valuesMinCount": 1,
> "valuesMaxCount": 1,
> "isUnique": false,
> "isIndexable": false
> },
> {
> "name": "before_tablename_guid",
> "typeName": "string",
> "isOptional": true,
> "cardinality": "SINGLE",
> "valuesMinCount": 0,
> "valuesMaxCount": 1,
> "isUnique": false,
> "isIndexable": false
> },
> {
> "name": "before_tablename_guid2",
> "typeName": "string",
> "isOptional": true,
> "cardinality": "SINGLE",
> "valuesMinCount": 0,
> "valuesMaxCount": 1,
> "isUnique": false,
> "isIndexable": false
> }
> ]
> }
> PUT /v2/types/structdef/name/{structGUID} succeeds but
> PUT /v2/types/structdef/guid/9527b5c2-49f7-4e25-bab0-a352d58fc2bf fails with
> the below exception
> 2016-12-16 11:34:08,381 ERROR - [pool-2-thread-7 -
> 2d2851fc-caf8-4460-a11e-facb60eeb223:] ~ graph rollback due to exception
> (GraphTransactionInterceptor:57)
> java.lang.NullPointerException
> at
> org.apache.atlas.repository.store.graph.v1.AtlasStructDefStoreV1.updateByGuid(AtlasStructDefStoreV1.java:235)
> at
> org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore.updateStructDefByGuid(AtlasTypeDefGraphStore.java:283)
> at
> org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:50)
> at
> org.apache.atlas.web.rest.TypesREST.updateStructDefByGuid(TypesREST.java:197)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185)
> at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
> at
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> at
>
[jira] [Created] (ATLAS-1399) [V2 API] PUT /v2/types/structdef/guid/{guid} fails while PUT /v2/types/structdef/name/{structGUID} suceeds
Vimal Sharma created ATLAS-1399:
---
Summary: [V2 API] PUT /v2/types/structdef/guid/{guid} fails while
PUT /v2/types/structdef/name/{structGUID} suceeds
Key: ATLAS-1399
URL: https://issues.apache.org/jira/browse/ATLAS-1399
Project: Atlas
Issue Type: Improvement
Reporter: Vimal Sharma
For the below JSON
{
"category": "STRUCT",
"guid": "9527b5c2-49f7-4e25-bab0-a352d58fc2bf",
"createTime": 1481887151201,
"updateTime": 1481887819834,
"version": 3,
"name": "table_creation_order",
"description": "table_creation_order",
"typeVersion": "1.0",
"attributeDefs": [
{
"name": "order",
"typeName": "int",
"isOptional": false,
"cardinality": "SINGLE",
"valuesMinCount": 1,
"valuesMaxCount": 1,
"isUnique": false,
"isIndexable": false
},
{
"name": "tablename",
"typeName": "string",
"isOptional": false,
"cardinality": "SINGLE",
"valuesMinCount": 1,
"valuesMaxCount": 1,
"isUnique": false,
"isIndexable": false
},
{
"name": "before_tablename_guid",
"typeName": "string",
"isOptional": true,
"cardinality": "SINGLE",
"valuesMinCount": 0,
"valuesMaxCount": 1,
"isUnique": false,
"isIndexable": false
},
{
"name": "before_tablename_guid2",
"typeName": "string",
"isOptional": true,
"cardinality": "SINGLE",
"valuesMinCount": 0,
"valuesMaxCount": 1,
"isUnique": false,
"isIndexable": false
}
]
}
PUT /v2/types/structdef/name/{structGUID} succeeds but
PUT /v2/types/structdef/guid/9527b5c2-49f7-4e25-bab0-a352d58fc2bf fails with
the below exception
2016-12-16 11:34:08,381 ERROR - [pool-2-thread-7 -
2d2851fc-caf8-4460-a11e-facb60eeb223:] ~ graph rollback due to exception
(GraphTransactionInterceptor:57)
java.lang.NullPointerException
at
org.apache.atlas.repository.store.graph.v1.AtlasStructDefStoreV1.updateByGuid(AtlasStructDefStoreV1.java:235)
at
org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore.updateStructDefByGuid(AtlasTypeDefGraphStore.java:283)
at
org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:50)
at
org.apache.atlas.web.rest.TypesREST.updateStructDefByGuid(TypesREST.java:197)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
at
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185)
at
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
at
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
at
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
at
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
at
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
at
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
at
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
at
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
at
com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
at
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
at
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at
com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:286)
at
com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:276)
at
com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:181)
at
com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)
at
com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:85)
[jira] [Created] (ATLAS-1398) POST request for Struct type accepts Enum type in request JSON
Vimal Sharma created ATLAS-1398:
---
Summary: POST request for Struct type accepts Enum type in request
JSON
Key: ATLAS-1398
URL: https://issues.apache.org/jira/browse/ATLAS-1398
Project: Atlas
Issue Type: Improvement
Reporter: Vimal Sharma
POST v2/types/structdef
{
"name" : "creation_order2",
"typeVersion" : "1.1",
"elementDefs" : [
{
"ordinal" : 1,
"value" : "PRE"
},
{
"ordinal" : 2,
"value" : "POST"
},
{
"ordinal" : 3,
"value" : "UNKNOWN"
}
]
}
return response
{
"category": "STRUCT",
"guid": "63d0755e-8e54-4f5f-9266-fa8d5df20969",
"createTime": 1481886280574,
"updateTime": 1481886280574,
"version": 1,
"name": "creation_order2",
"description": "creation_order2",
"typeVersion": "1.1",
"attributeDefs": []
}
The response suggests that and empty Struct is created.The POST request should
not create an empty Struct and should fail with the message "Invalid JSON"
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (ATLAS-1397) [V2 API] DELETE should return deleted type guid with proper message
Vimal Sharma created ATLAS-1397:
---
Summary: [V2 API] DELETE should return deleted type guid with
proper message
Key: ATLAS-1397
URL: https://issues.apache.org/jira/browse/ATLAS-1397
Project: Atlas
Issue Type: Improvement
Reporter: Vimal Sharma
Assignee: Vimal Sharma
POST v2/types/enumdef
{
"name" : "creation_order1",
"typeVersion" : "1.1",
"elementDefs" : [
{ "ordinal" : 1, "value" : "PRE" }
,
{ "ordinal" : 2, "value" : "POST" }
,
{ "ordinal" : 3, "value" : "UNKNOWN" }
]
}
returns the response
{
"category": "ENUM",
"guid": "c5642d55-9f8e-45b1-b4a9-709c97b46233",
"createTime": 1481885315377,
"updateTime": 1481885315377,
"version": 1,
"name": "creation_order1",
"description": "creation_order1",
"typeVersion": "1.1",
"elementDefs": [
{ "value": "PRE", "ordinal": 1 }
,
{ "value": "POST", "ordinal": 2 }
,
{ "value": "UNKNOWN", "ordinal": 3 }
]
}
DELETE v2/types/enumdef/name/creation_order1 is successful but doesn't return
anything. DELETE request should return some response in the below format:
{
"result" : "SUCCESS/FAIL"
"guid" : "{guid}"
}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (ATLAS-1396) [V2 API] GET v2/types/enumdef/guid/{guid} not working as expected
Vimal Sharma created ATLAS-1396:
---
Summary: [V2 API] GET v2/types/enumdef/guid/{guid} not working as
expected
Key: ATLAS-1396
URL: https://issues.apache.org/jira/browse/ATLAS-1396
Project: Atlas
Issue Type: Bug
Reporter: Vimal Sharma
Assignee: Vimal Sharma
POST v2/types/enumdef
{
"name" : "creation_order1",
"typeVersion" : "1.1",
"elementDefs" : [
{
"ordinal" : 1,
"value" : "PRE"
},
{
"ordinal" : 2,
"value" : "POST"
},
{
"ordinal" : 3,
"value" : "UNKNOWN"
}
]
}
returns the response
{
"category": "ENUM",
"guid": "c5642d55-9f8e-45b1-b4a9-709c97b46233",
"createTime": 1481885315377,
"updateTime": 1481885315377,
"version": 1,
"name": "creation_order1",
"description": "creation_order1",
"typeVersion": "1.1",
"elementDefs": [
{
"value": "PRE",
"ordinal": 1
},
{
"value": "POST",
"ordinal": 2
},
{
"value": "UNKNOWN",
"ordinal": 3
}
]
}
But GET v2/types/enumdef/guid/c5642d55-9f8e-45b1-b4a9-709c97b46233 returns
{
"errorCode": "ATLAS4042E",
"errorMessage": "Given type guid c5642d55-9f8e-45b1-b4a9-709c97b46233 was
invalid"
}
GET v2/types/enumdef/name/creation_order1 returns
{
"category": "ENUM",
"guid": "c5642d55-9f8e-45b1-b4a9-709c97b46233",
"createTime": 1481885315377,
"updateTime": 1481885315377,
"version": 1,
"name": "creation_order1",
"typeVersion": "1.1",
"elementDefs": [
{
"value": "PRE",
"ordinal": 1
},
{
"value": "POST",
"ordinal": 2
},
{
"value": "UNKNOWN",
"ordinal": 3
}
]
}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-1366) Documentation for new REST API
[ https://issues.apache.org/jira/browse/ATLAS-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vimal Sharma updated ATLAS-1366: Attachment: ATLAS-1366.patch I could create swagger.json using the jaxrs analyzer tool. Thanks a lot [~apoorvnaik] for suggesting jaxrs analyzer. NOTE: jaxrs analyzer tool works only with Java 8. Additional changes are required for proper annotation and examples. I will be updating this patch accordingly > Documentation for new REST API > -- > > Key: ATLAS-1366 > URL: https://issues.apache.org/jira/browse/ATLAS-1366 > Project: Atlas > Issue Type: Improvement >Reporter: Vimal Sharma >Assignee: Vimal Sharma > Attachments: ATLAS-1366.patch, swagger.json > > > New REST API documentation preferably with Swagger integration -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-1366) Documentation for new REST API
[ https://issues.apache.org/jira/browse/ATLAS-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vimal Sharma updated ATLAS-1366: Attachment: swagger.json > Documentation for new REST API > -- > > Key: ATLAS-1366 > URL: https://issues.apache.org/jira/browse/ATLAS-1366 > Project: Atlas > Issue Type: Improvement >Reporter: Vimal Sharma >Assignee: Vimal Sharma > Attachments: ATLAS-1366.patch, swagger.json > > > New REST API documentation preferably with Swagger integration -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1318) Atlas Type System does not have DELETE API
[ https://issues.apache.org/jira/browse/ATLAS-1318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15744345#comment-15744345 ] Vimal Sharma commented on ATLAS-1318: - [~breadpowder] Please go ahead and assign the bug to yourself. As [~apoorvnaik] said, please use the new REST endpoints. > Atlas Type System does not have DELETE API > -- > > Key: ATLAS-1318 > URL: https://issues.apache.org/jira/browse/ATLAS-1318 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.7-incubating >Reporter: Zineng Yuan > > I am trying to extend Atlas Type System by adding custom data type. However, > when I found a type name was misspecified and needed to be recreated, I can't > find a Restful Delete API. > Question is does Atlas expose a Delete API for custom data types/attributes? > Without this delete API, it's difficult to rely on Atlas as a meta store to > extend custom data. > Please do suggest how to recreate a data type in this case. Thank you! > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-1366) Documentation for new REST API
Vimal Sharma created ATLAS-1366: --- Summary: Documentation for new REST API Key: ATLAS-1366 URL: https://issues.apache.org/jira/browse/ATLAS-1366 Project: Atlas Issue Type: Improvement Reporter: Vimal Sharma Assignee: Vimal Sharma New REST API documentation preferably with Swagger integration -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1318) Atlas Type System does not have DELETE API
[
https://issues.apache.org/jira/browse/ATLAS-1318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15741306#comment-15741306
]
Vimal Sharma commented on ATLAS-1318:
-
[~breadpowder]
1) When deleting a type T, the approach would be to delete all the types T_Ref
(and all entities of T_Ref as well) which have reference to T. Otherwise for
the entities of type T_Ref, there would be a "ghost" reference to a type which
doesn't exist. "System" types are guaranteed to not have such references to
"Custom" types. So we can relax the criteria 3 for considering DELETION of type
T. The earlier suggestion was a "playing it safe" alternative when dealing with
System types. So, on DELETE request of a Type T, below steps can be followed:
A) Verify whether T is a "Custom" type
B) Find all "Custom" types T_Ref which have reference to T
C) Remove all entities of type T_Ref
D) Remove type T_Ref
E) Remove all entities of type T
F) Remove type T
2) Please go ahead with adding an optional attribute (maybe "typeKind") to
identify whether a type is a "Custom" or "System" type. The types for which
this attribute will not be available will be treated as "System" attributes.
3) I am not aware of any direct request to get type hierarchy. We might have to
get all the types using call "/api/atlas/types" and then scan for references in
"/api/atlas/types/{typeName}"
P.S. There is a catch in step B of point 1. What if, for some "Custom" type
T_Ref which has reference to T, user forgot to add "Custom" attribute. Now that
the type T is removed, there will be "ghost" references to T from T_Ref. One
solution is to look for references to T in all types and if any non "Custom"
type has reference to T, we should abort the delete.
> Atlas Type System does not have DELETE API
> --
>
> Key: ATLAS-1318
> URL: https://issues.apache.org/jira/browse/ATLAS-1318
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Zineng Yuan
>
> I am trying to extend Atlas Type System by adding custom data type. However,
> when I found a type name was misspecified and needed to be recreated, I can't
> find a Restful Delete API.
> Question is does Atlas expose a Delete API for custom data types/attributes?
> Without this delete API, it's difficult to rely on Atlas as a meta store to
> extend custom data.
> Please do suggest how to recreate a data type in this case. Thank you!
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (ATLAS-1365) Use proper Contructors for Hive Entity objects in HiveHook
Vimal Sharma created ATLAS-1365: --- Summary: Use proper Contructors for Hive Entity objects in HiveHook Key: ATLAS-1365 URL: https://issues.apache.org/jira/browse/ATLAS-1365 Project: Atlas Issue Type: Improvement Reporter: Vimal Sharma Assignee: Vimal Sharma Currently, default constructor for Entity is used and attributes like Table/Path/Database and EntityType are set through explicit calls to setter methods. This should be modified to use appropriate constructor for the data type. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1340) Credential Provider utility does not work with fully qualified local/HDFS jceks path
[ https://issues.apache.org/jira/browse/ATLAS-1340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15728451#comment-15728451 ] Vimal Sharma commented on ATLAS-1340: - +1 > Credential Provider utility does not work with fully qualified local/HDFS > jceks path > > > Key: ATLAS-1340 > URL: https://issues.apache.org/jira/browse/ATLAS-1340 > Project: Atlas > Issue Type: Bug >Affects Versions: trunk >Reporter: Vipin Rathor >Priority: Minor > Labels: patch, security > Fix For: trunk > > Attachments: ATLAS-1340-v2.patch, fix-hdfs-credProvider.patch > > > At present the Atlas Credential Provider utility (./bin/cputil.py) does not > work with credential provider path like > jceks://file/local/file/path/file.jceks or > jceks://hdfs@namenodehost:port/path/in/hdfs/to/file.jceks as mentioned in > documentation page at http://atlas.apache.org/Security.html (section: > Credential Provider Utility Script) > Current Behavior: > cputil.py always creates a credential provider file in local file system at > root directory as follows: > 1. For the input "jceks://file/local/file/path/file.jceks", > file created => /jceks:/file/local/file/path/file.jceks > 2. For the input "jceks://h...@namenode.com:8020/path/in/hdfs/to/file.jceks", > file created => /jceks:/h...@namenode.com:8020/path/in/hdfs/to/file.jceks on > local file system > Expected Behavior: > 1. For the input "jceks://file/local/file/path/file.jceks", > file created should be /local/file/path/file.jceks > 2. For the input "jceks://h...@namenode.com:8020/path/in/hdfs/to/file.jceks", > file created should be /path/in/hdfs/to/file.jceks on the specified HDFS file > system. > Steps to re-create: > 1. Run ./bin/cputil.py and provide fully qualified path to jceks file as > described above. > Attached is a patch to fix this issue. Tested with both local and HDFS jceks > credential provider path. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1351) HiveHook fails with NPE for hive process registration
[
https://issues.apache.org/jira/browse/ATLAS-1351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15727814#comment-15727814
]
Vimal Sharma commented on ATLAS-1351:
-
[~suma.shivaprasad] entityComparator function is used in methods
handleExternalTables and registerProcess. Either name(Table name) or path(DFS
path) is guaranteed to be available.
getT().getCompleteName itself might result in NullPointerException because
getT() would be null in case the entity is a DFS path.
> HiveHook fails with NPE for hive process registration
> -
>
> Key: ATLAS-1351
> URL: https://issues.apache.org/jira/browse/ATLAS-1351
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: Ayub Khan
>Assignee: Vimal Sharma
> Attachments: ATLAS-1351.patch, hive.log
>
>
> HiveHook fails with below stack trace whenever a sqoop import job to copy
> into hive table.
> *Impact: No hive process info is captured in Atlas*
> {noformat}
> 2016-12-06 11:41:02,304 ERROR [Atlas Logger 0]: hook.HiveHook
> (HiveHook.java:run(197)) - Atlas hook failed due to error
> java.lang.NullPointerException
> at
> org.apache.atlas.hive.hook.HiveHook$EntityComparator.compare(HiveHook.java:1093)
> at
> org.apache.atlas.hive.hook.HiveHook$EntityComparator.compare(HiveHook.java:1089)
> at java.util.TreeMap.compare(TreeMap.java:1188)
> at java.util.TreeMap.put(TreeMap.java:531)
> at java.util.TreeSet.add(TreeSet.java:255)
> at java.util.AbstractCollection.addAll(AbstractCollection.java:342)
> at java.util.TreeSet.addAll(TreeSet.java:312)
> at
> org.apache.atlas.hive.hook.HiveHook.registerProcess(HiveHook.java:608)
> at
> org.apache.atlas.hive.hook.HiveHook.fireAndForget(HiveHook.java:235)
> at org.apache.atlas.hive.hook.HiveHook.access$200(HiveHook.java:84)
> at org.apache.atlas.hive.hook.HiveHook$2.run(HiveHook.java:195)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> Attaching hive.log for reference.
> Sample sqoop import command:
> {noformat}
> /usr/hdp/current/sqoop-client/bin/sqoop import --connect
> jdbc:mysql://ctr-e64-1480733150053-3050-01-02.hwx.site/sqoopTests
> --username sqoop --password sqoop --hive-import --warehouse-dir /user/hrt_qa
> --table SqoopTablejufuv3lh71 --hive-table hiveSqoopTablejufuv3lh71temp4 --m 1
> --create-hive-table
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-1351) HiveHook fails with NPE for hive process registration
[
https://issues.apache.org/jira/browse/ATLAS-1351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vimal Sharma updated ATLAS-1351:
Attachment: ATLAS-1351.patch
> HiveHook fails with NPE for hive process registration
> -
>
> Key: ATLAS-1351
> URL: https://issues.apache.org/jira/browse/ATLAS-1351
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: Ayub Khan
> Attachments: ATLAS-1351.patch, hive.log
>
>
> HiveHook fails with below stack trace whenever a sqoop import job to copy
> into hive table.
> *Impact: No hive process info is captured in Atlas*
> {noformat}
> 2016-12-06 11:41:02,304 ERROR [Atlas Logger 0]: hook.HiveHook
> (HiveHook.java:run(197)) - Atlas hook failed due to error
> java.lang.NullPointerException
> at
> org.apache.atlas.hive.hook.HiveHook$EntityComparator.compare(HiveHook.java:1093)
> at
> org.apache.atlas.hive.hook.HiveHook$EntityComparator.compare(HiveHook.java:1089)
> at java.util.TreeMap.compare(TreeMap.java:1188)
> at java.util.TreeMap.put(TreeMap.java:531)
> at java.util.TreeSet.add(TreeSet.java:255)
> at java.util.AbstractCollection.addAll(AbstractCollection.java:342)
> at java.util.TreeSet.addAll(TreeSet.java:312)
> at
> org.apache.atlas.hive.hook.HiveHook.registerProcess(HiveHook.java:608)
> at
> org.apache.atlas.hive.hook.HiveHook.fireAndForget(HiveHook.java:235)
> at org.apache.atlas.hive.hook.HiveHook.access$200(HiveHook.java:84)
> at org.apache.atlas.hive.hook.HiveHook$2.run(HiveHook.java:195)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> Attaching hive.log for reference.
> Sample sqoop import command:
> {noformat}
> /usr/hdp/current/sqoop-client/bin/sqoop import --connect
> jdbc:mysql://ctr-e64-1480733150053-3050-01-02.hwx.site/sqoopTests
> --username sqoop --password sqoop --hive-import --warehouse-dir /user/hrt_qa
> --table SqoopTablejufuv3lh71 --hive-table hiveSqoopTablejufuv3lh71temp4 --m 1
> --create-hive-table
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (ATLAS-1351) HiveHook fails with NPE for hive process registration
[
https://issues.apache.org/jira/browse/ATLAS-1351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vimal Sharma reassigned ATLAS-1351:
---
Assignee: Vimal Sharma
> HiveHook fails with NPE for hive process registration
> -
>
> Key: ATLAS-1351
> URL: https://issues.apache.org/jira/browse/ATLAS-1351
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: Ayub Khan
>Assignee: Vimal Sharma
> Attachments: ATLAS-1351.patch, hive.log
>
>
> HiveHook fails with below stack trace whenever a sqoop import job to copy
> into hive table.
> *Impact: No hive process info is captured in Atlas*
> {noformat}
> 2016-12-06 11:41:02,304 ERROR [Atlas Logger 0]: hook.HiveHook
> (HiveHook.java:run(197)) - Atlas hook failed due to error
> java.lang.NullPointerException
> at
> org.apache.atlas.hive.hook.HiveHook$EntityComparator.compare(HiveHook.java:1093)
> at
> org.apache.atlas.hive.hook.HiveHook$EntityComparator.compare(HiveHook.java:1089)
> at java.util.TreeMap.compare(TreeMap.java:1188)
> at java.util.TreeMap.put(TreeMap.java:531)
> at java.util.TreeSet.add(TreeSet.java:255)
> at java.util.AbstractCollection.addAll(AbstractCollection.java:342)
> at java.util.TreeSet.addAll(TreeSet.java:312)
> at
> org.apache.atlas.hive.hook.HiveHook.registerProcess(HiveHook.java:608)
> at
> org.apache.atlas.hive.hook.HiveHook.fireAndForget(HiveHook.java:235)
> at org.apache.atlas.hive.hook.HiveHook.access$200(HiveHook.java:84)
> at org.apache.atlas.hive.hook.HiveHook$2.run(HiveHook.java:195)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> Attaching hive.log for reference.
> Sample sqoop import command:
> {noformat}
> /usr/hdp/current/sqoop-client/bin/sqoop import --connect
> jdbc:mysql://ctr-e64-1480733150053-3050-01-02.hwx.site/sqoopTests
> --username sqoop --password sqoop --hive-import --warehouse-dir /user/hrt_qa
> --table SqoopTablejufuv3lh71 --hive-table hiveSqoopTablejufuv3lh71temp4 --m 1
> --create-hive-table
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (ATLAS-1349) Reduce excess error logging in atlas logs
[ https://issues.apache.org/jira/browse/ATLAS-1349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vimal Sharma resolved ATLAS-1349. - Resolution: Fixed Committed to master. Thanks Apoorv https://github.com/apache/incubator-atlas/commit/c413975aa9a10b2e3f576c68fefeffe11229b693 > Reduce excess error logging in atlas logs > - > > Key: ATLAS-1349 > URL: https://issues.apache.org/jira/browse/ATLAS-1349 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.8-incubating >Reporter: Apoorv Naik >Assignee: Apoorv Naik > Fix For: 0.8-incubating > > Attachments: ATLAS-1349.patch > > > Currently there's lot of exception logging in the altas application logs > because of the graph transaction interceptor and the custom exception > mappers. This changeset fixes those problems. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1340) Credential Provider utility does not work with fully qualified local/HDFS jceks path
[ https://issues.apache.org/jira/browse/ATLAS-1340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15708414#comment-15708414 ] Vimal Sharma commented on ATLAS-1340: - Further, please mark the status as Patch Available when you upload a patch > Credential Provider utility does not work with fully qualified local/HDFS > jceks path > > > Key: ATLAS-1340 > URL: https://issues.apache.org/jira/browse/ATLAS-1340 > Project: Atlas > Issue Type: Bug >Affects Versions: trunk >Reporter: Vipin Rathor >Priority: Minor > Labels: patch, security > Attachments: fix-hdfs-credProvider.patch > > > At present the Atlas Credential Provider utility (./bin/cputil.py) does not > work with credential provider path like > jceks://file/local/file/path/file.jceks or > jceks://hdfs@namenodehost:port/path/in/hdfs/to/file.jceks as mentioned in > documentation page at http://atlas.apache.org/Security.html (section: > Credential Provider Utility Script) > Current Behavior: > cputil.py always creates a credential provider file in local file system at > root directory as follows: > 1. For the input "jceks://file/local/file/path/file.jceks", > file created => /jceks:/file/local/file/path/file.jceks > 2. For the input "jceks://h...@namenode.com:8020/path/in/hdfs/to/file.jceks", > file created => /jceks:/h...@namenode.com:8020/path/in/hdfs/to/file.jceks on > local file system > Expected Behavior: > 1. For the input "jceks://file/local/file/path/file.jceks", > file created should be /local/file/path/file.jceks > 2. For the input "jceks://h...@namenode.com:8020/path/in/hdfs/to/file.jceks", > file created should be /path/in/hdfs/to/file.jceks on the specified HDFS file > system. > Steps to re-create: > 1. Run ./bin/cputil.py and provide fully qualified path to jceks file as > described above. > Attached is a patch to fix this issue. Tested with both local and HDFS jceks > credential provider path. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1340) Credential Provider utility does not work with fully qualified local/HDFS jceks path
[
https://issues.apache.org/jira/browse/ATLAS-1340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15708401#comment-15708401
]
Vimal Sharma commented on ATLAS-1340:
-
Integration tests in CredentialProviderUtilityIT are failing with this patch:
Tests run: 4, Failures: 4, Errors: 0, Skipped: 0, Time elapsed: 0.547 sec <<<
FAILURE! - in org.apache.atlas.CredentialProviderUtilityIT
testEnterEmptyValues(org.apache.atlas.CredentialProviderUtilityIT) Time
elapsed: 0.271 sec <<< FAILURE!
java.io.IOException: No CredentialProviderFactory for
/var/folders/96/j44w9z7d6g78llqcyv5_6jj8gp/T/tempproviders7798648075874736001/test.jks
in hadoop.security.credential.provider.path
at
org.apache.atlas.CredentialProviderUtilityIT.testEnterEmptyValues(CredentialProviderUtilityIT.java:131)
testEnterMismatchedValues(org.apache.atlas.CredentialProviderUtilityIT) Time
elapsed: 0.001 sec <<< FAILURE!
java.io.IOException: No CredentialProviderFactory for
/var/folders/96/j44w9z7d6g78llqcyv5_6jj8gp/T/tempproviders6272433012975323657/test.jks
in hadoop.security.credential.provider.path
at
org.apache.atlas.CredentialProviderUtilityIT.testEnterMismatchedValues(CredentialProviderUtilityIT.java:185)
testEnterValidValues(org.apache.atlas.CredentialProviderUtilityIT) Time
elapsed: 0.001 sec <<< FAILURE!
java.io.IOException: No CredentialProviderFactory for
/var/folders/96/j44w9z7d6g78llqcyv5_6jj8gp/T/tempproviders502898944984490/test.jks
in hadoop.security.credential.provider.path
at
org.apache.atlas.CredentialProviderUtilityIT.testEnterValidValues(CredentialProviderUtilityIT.java:69)
testOverwriteValues(org.apache.atlas.CredentialProviderUtilityIT) Time
elapsed: 0.002 sec <<< FAILURE!
java.io.IOException: No CredentialProviderFactory for
/var/folders/96/j44w9z7d6g78llqcyv5_6jj8gp/T/tempproviders898796476766539793/test.jks
in hadoop.security.credential.provider.path
at
org.apache.atlas.CredentialProviderUtilityIT.testOverwriteValues(CredentialProviderUtilityIT.java:229)
Can you please fix these tests. Please submit the patch as
ATLAS-{BUG_NO}-{VERSION}.patch
> Credential Provider utility does not work with fully qualified local/HDFS
> jceks path
>
>
> Key: ATLAS-1340
> URL: https://issues.apache.org/jira/browse/ATLAS-1340
> Project: Atlas
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: Vipin Rathor
>Priority: Minor
> Labels: patch, security
> Attachments: fix-hdfs-credProvider.patch
>
>
> At present the Atlas Credential Provider utility (./bin/cputil.py) does not
> work with credential provider path like
> jceks://file/local/file/path/file.jceks or
> jceks://hdfs@namenodehost:port/path/in/hdfs/to/file.jceks as mentioned in
> documentation page at http://atlas.apache.org/Security.html (section:
> Credential Provider Utility Script)
> Current Behavior:
> cputil.py always creates a credential provider file in local file system at
> root directory as follows:
> 1. For the input "jceks://file/local/file/path/file.jceks",
> file created => /jceks:/file/local/file/path/file.jceks
> 2. For the input "jceks://h...@namenode.com:8020/path/in/hdfs/to/file.jceks",
> file created => /jceks:/h...@namenode.com:8020/path/in/hdfs/to/file.jceks on
> local file system
> Expected Behavior:
> 1. For the input "jceks://file/local/file/path/file.jceks",
> file created should be /local/file/path/file.jceks
> 2. For the input "jceks://h...@namenode.com:8020/path/in/hdfs/to/file.jceks",
> file created should be /path/in/hdfs/to/file.jceks on the specified HDFS file
> system.
> Steps to re-create:
> 1. Run ./bin/cputil.py and provide fully qualified path to jceks file as
> described above.
> Attached is a patch to fix this issue. Tested with both local and HDFS jceks
> credential provider path.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-1343) CTAS query is not captured by Atlas with Hive2
[ https://issues.apache.org/jira/browse/ATLAS-1343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vimal Sharma updated ATLAS-1343: Attachment: ATLAS-1343.patch The attached patch fixes the issue. Although the column level lineage is still not available from Hive2, this fix ensures that the CTAS query process registration with Atlas is not blocked. I have tested the patch with Hive2 and the process is being registered successfully > CTAS query is not captured by Atlas with Hive2 > -- > > Key: ATLAS-1343 > URL: https://issues.apache.org/jira/browse/ATLAS-1343 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.8-incubating >Reporter: Vimal Sharma >Assignee: Vimal Sharma > Fix For: 0.8-incubating > > Attachments: ATLAS-1343.patch > > > CTAS query is not captured by Atlas due to deprecation of method > getBaseCols() from Dependency class in LineageInfo in Hive2. Since the column > level lineage is not available from Hive2, Atlas Hook fails to capture the > process as well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-1343) CTAS query is not captured by Atlas with Hive2
Vimal Sharma created ATLAS-1343: --- Summary: CTAS query is not captured by Atlas with Hive2 Key: ATLAS-1343 URL: https://issues.apache.org/jira/browse/ATLAS-1343 Project: Atlas Issue Type: Bug Affects Versions: 0.8-incubating Reporter: Vimal Sharma Assignee: Vimal Sharma Fix For: 0.8-incubating CTAS query is not captured by Atlas due to deprecation of method getBaseCols() from Dependency class in LineageInfo in Hive2. Since the column level lineage is not available from Hive2, Atlas Hook fails to capture the process as well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ATLAS-1300) LineageResource API needs to map to the new LineageREST API
[ https://issues.apache.org/jira/browse/ATLAS-1300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vimal Sharma resolved ATLAS-1300. - Resolution: Fixed Committed to master. Thanks Sarath https://github.com/apache/incubator-atlas/commit/eec1201c9ff604b0697af2def66ade6d02ab0603 > LineageResource API needs to map to the new LineageREST API > --- > > Key: ATLAS-1300 > URL: https://issues.apache.org/jira/browse/ATLAS-1300 > Project: Atlas > Issue Type: New Feature >Affects Versions: 0.8-incubating >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian > > The current v1 Lineage API (LineageResource) needs to route to the new v2 > Lineage API (LineageREST). > 1. Inputs Graph > 2. Outputs Graph -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-1336) Storm Hook IT fails due to non registry of type storm_topology
[ https://issues.apache.org/jira/browse/ATLAS-1336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vimal Sharma updated ATLAS-1336: Attachment: ATLAS-1336.patch > Storm Hook IT fails due to non registry of type storm_topology > -- > > Key: ATLAS-1336 > URL: https://issues.apache.org/jira/browse/ATLAS-1336 > Project: Atlas > Issue Type: Bug >Reporter: Vimal Sharma >Assignee: Vimal Sharma > Attachments: ATLAS-1336.patch > > > Storm Hook IT is failing with the following error due to non registry of type > "storm_topology": > org.apache.atlas.typesystem.exception.TypeNotFoundException: Unknown > datatype: storm_topology > at > org.apache.atlas.typesystem.types.TypeSystem.getDataType(TypeSystem.java:192) > at > org.apache.atlas.repository.graph.GraphHelper.getTypedReferenceableInstance(GraphHelper.java:742) > at > org.apache.atlas.repository.graph.GraphHelper.deserializeClassInstances(GraphHelper.java:726) > at > org.apache.atlas.services.DefaultMetadataService.deserializeClassInstances(DefaultMetadataService.java:280) > at > org.apache.atlas.services.DefaultMetadataService.createEntities(DefaultMetadataService.java:268) > at > org.apache.atlas.web.resources.EntityResource.submit(EntityResource.java:130) > at > org.apache.atlas.LocalAtlasClient$1.invoke(LocalAtlasClient.java:82) > at > org.apache.atlas.LocalAtlasClient$EntityOperation.run(LocalAtlasClient.java:118) > at > org.apache.atlas.LocalAtlasClient.createEntity(LocalAtlasClient.java:85) > at org.apache.atlas.AtlasClient.createEntity(AtlasClient.java:486) > at > org.apache.atlas.notification.NotificationHookConsumer$HookConsumer.handleMessage(NotificationHookConsumer.java:221) > at > org.apache.atlas.notification.NotificationHookConsumer$HookConsumer.run(NotificationHookConsumer.java:202) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask.run(FutureTask.java:262) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) > 2016-11-28 12:30:52,628 WARN - [NotificationHookConsumer thread-0:] ~ Error > handling messageMetadata service API CREATE_ENTITY failed with status 400 > (Bad Request) Response Body > (org.apache.atlas.typesystem.exception.TypeNotFoundException: Unknown > datatype: storm_topology > at > org.apache.atlas.typesystem.types.TypeSystem.getDataType(TypeSystem.java:192) > at > org.apache.atlas.repository.graph.GraphHelper.getTypedReferenceableInstance(GraphHelper.java:742) > at > org.apache.atlas.repository.graph.GraphHelper.deserializeClassInstances(GraphHelper.java:726) > at > org.apache.atlas.services.DefaultMetadataService.deserializeClassInstances(DefaultMetadataService.java:280) > at > org.apache.atlas.services.DefaultMetadataService.createEntities(DefaultMetadataService.java:268) > at > org.apache.atlas.web.resources.EntityResource.submit(EntityResource.java:130) > at > org.apache.atlas.LocalAtlasClient$1.invoke(LocalAtlasClient.java:82) > at > org.apache.atlas.LocalAtlasClient$EntityOperation.run(LocalAtlasClient.java:118) > at > org.apache.atlas.LocalAtlasClient.createEntity(LocalAtlasClient.java:85) > at org.apache.atlas.AtlasClient.createEntity(AtlasClient.java:486) > at > org.apache.atlas.notification.NotificationHookConsumer$HookConsumer.handleMessage(NotificationHookConsumer.java:221) > at > org.apache.atlas.notification.NotificationHookConsumer$HookConsumer.run(NotificationHookConsumer.java:202) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask.run(FutureTask.java:262) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) > ) (NotificationHookConsumer$HookConsumer:252) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-1336) Storm Hook IT fails due to non registry of type storm_topology
Vimal Sharma created ATLAS-1336: --- Summary: Storm Hook IT fails due to non registry of type storm_topology Key: ATLAS-1336 URL: https://issues.apache.org/jira/browse/ATLAS-1336 Project: Atlas Issue Type: Bug Reporter: Vimal Sharma Assignee: Vimal Sharma Storm Hook IT is failing with the following error due to non registry of type "storm_topology": org.apache.atlas.typesystem.exception.TypeNotFoundException: Unknown datatype: storm_topology at org.apache.atlas.typesystem.types.TypeSystem.getDataType(TypeSystem.java:192) at org.apache.atlas.repository.graph.GraphHelper.getTypedReferenceableInstance(GraphHelper.java:742) at org.apache.atlas.repository.graph.GraphHelper.deserializeClassInstances(GraphHelper.java:726) at org.apache.atlas.services.DefaultMetadataService.deserializeClassInstances(DefaultMetadataService.java:280) at org.apache.atlas.services.DefaultMetadataService.createEntities(DefaultMetadataService.java:268) at org.apache.atlas.web.resources.EntityResource.submit(EntityResource.java:130) at org.apache.atlas.LocalAtlasClient$1.invoke(LocalAtlasClient.java:82) at org.apache.atlas.LocalAtlasClient$EntityOperation.run(LocalAtlasClient.java:118) at org.apache.atlas.LocalAtlasClient.createEntity(LocalAtlasClient.java:85) at org.apache.atlas.AtlasClient.createEntity(AtlasClient.java:486) at org.apache.atlas.notification.NotificationHookConsumer$HookConsumer.handleMessage(NotificationHookConsumer.java:221) at org.apache.atlas.notification.NotificationHookConsumer$HookConsumer.run(NotificationHookConsumer.java:202) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) 2016-11-28 12:30:52,628 WARN - [NotificationHookConsumer thread-0:] ~ Error handling messageMetadata service API CREATE_ENTITY failed with status 400 (Bad Request) Response Body (org.apache.atlas.typesystem.exception.TypeNotFoundException: Unknown datatype: storm_topology at org.apache.atlas.typesystem.types.TypeSystem.getDataType(TypeSystem.java:192) at org.apache.atlas.repository.graph.GraphHelper.getTypedReferenceableInstance(GraphHelper.java:742) at org.apache.atlas.repository.graph.GraphHelper.deserializeClassInstances(GraphHelper.java:726) at org.apache.atlas.services.DefaultMetadataService.deserializeClassInstances(DefaultMetadataService.java:280) at org.apache.atlas.services.DefaultMetadataService.createEntities(DefaultMetadataService.java:268) at org.apache.atlas.web.resources.EntityResource.submit(EntityResource.java:130) at org.apache.atlas.LocalAtlasClient$1.invoke(LocalAtlasClient.java:82) at org.apache.atlas.LocalAtlasClient$EntityOperation.run(LocalAtlasClient.java:118) at org.apache.atlas.LocalAtlasClient.createEntity(LocalAtlasClient.java:85) at org.apache.atlas.AtlasClient.createEntity(AtlasClient.java:486) at org.apache.atlas.notification.NotificationHookConsumer$HookConsumer.handleMessage(NotificationHookConsumer.java:221) at org.apache.atlas.notification.NotificationHookConsumer$HookConsumer.run(NotificationHookConsumer.java:202) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) ) (NotificationHookConsumer$HookConsumer:252) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1318) Atlas Type System does not have DELETE API
[ https://issues.apache.org/jira/browse/ATLAS-1318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15697363#comment-15697363 ] Vimal Sharma commented on ATLAS-1318: - Term Trait types are, by design, hierarchical in nature.So, there will be references to child term types. As long as none of the types in this hierarchy tree reference "System" types and there are no data entities for any of the type in the tree, deletion of a term trait type can be allowed. > Atlas Type System does not have DELETE API > -- > > Key: ATLAS-1318 > URL: https://issues.apache.org/jira/browse/ATLAS-1318 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.7-incubating >Reporter: Zineng Yuan > > I am trying to extend Atlas Type System by adding custom data type. However, > when I found a type name was misspecified and needed to be recreated, I can't > find a Restful Delete API. > Question is does Atlas expose a Delete API for custom data types/attributes? > Without this delete API, it's difficult to rely on Atlas as a meta store to > extend custom data. > Please do suggest how to recreate a data type in this case. Thank you! > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1318) Atlas Type System does not have DELETE API
[ https://issues.apache.org/jira/browse/ATLAS-1318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15695529#comment-15695529 ] Vimal Sharma commented on ATLAS-1318: - [~breadpowder] This solution looks reasonable. Can you please add one more condition to the above mentioned conditions: The candidate type for DELETE should not have references to any of the "System" types. By "System" types, I mean the default types which are registered during Atlas bootstrap. So, to reiterate your point, DELETE of a type will be successful only if: 1) It is a "Customized" data type 2) No data entities exist for the type 3) There are no references to any of the "System" types In all other cases, DELETE of the type would not be allowed by Atlas Server. > Atlas Type System does not have DELETE API > -- > > Key: ATLAS-1318 > URL: https://issues.apache.org/jira/browse/ATLAS-1318 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.7-incubating >Reporter: Zineng Yuan > > I am trying to extend Atlas Type System by adding custom data type. However, > when I found a type name was misspecified and needed to be recreated, I can't > find a Restful Delete API. > Question is does Atlas expose a Delete API for custom data types/attributes? > Without this delete API, it's difficult to rely on Atlas as a meta store to > extend custom data. > Please do suggest how to recreate a data type in this case. Thank you! > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-1325) Fix Apache Build failure due to Rat check on log files
[ https://issues.apache.org/jira/browse/ATLAS-1325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vimal Sharma updated ATLAS-1325: Attachment: ATLAS-1325.patch > Fix Apache Build failure due to Rat check on log files > --- > > Key: ATLAS-1325 > URL: https://issues.apache.org/jira/browse/ATLAS-1325 > Project: Atlas > Issue Type: Bug >Reporter: Vimal Sharma > Attachments: ATLAS-1325.patch > > > Build failed on Apache Nightly runs due to a log file inside project > directory. > [ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.7:check > (rat-check) on project apache-atlas: Too many unapproved licenses: 1 -> [Help > 1] > Exclude log files from Rat check -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1321) Fix failure of Hive ITs
[
https://issues.apache.org/jira/browse/ATLAS-1321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15693155#comment-15693155
]
Vimal Sharma commented on ATLAS-1321:
-
+1
> Fix failure of Hive ITs
> ---
>
> Key: ATLAS-1321
> URL: https://issues.apache.org/jira/browse/ATLAS-1321
> Project: Atlas
> Issue Type: Bug
>Reporter: Vimal Sharma
>Assignee: Vimal Sharma
> Attachments: ATLAS-1321-v2.patch, ATLAS-1321-v3.patch,
> ATLAS-1321-v4.patch, ATLAS-1321.patch
>
>
> Hive ITs fail because the Atlas TypeDef initializer cannot locate models
> directory. None of the types defined in hive-model.json are regsitered.
> Below is the stack trace:
> Caused by: org.apache.atlas.AtlasServiceException: Metadata service API
> org.apache.atlas.AtlasBaseClient$APIInfo@6398e143 failed with status 400 (Bad
> Request) Response Body ({"error":"Unknown datatype:
> hive_db","stackTrace":"org.apache.atlas.typesystem.exception.TypeNotFoundException:
> Unknown datatype: hive_db\n\tat
> org.apache.atlas.typesystem.types.TypeSystem.getDataType(TypeSystem.java:192)\n\tat
>
> org.apache.atlas.services.DefaultMetadataService.validateTypeExists(DefaultMetadataService.java:519)\n\tat
>
> org.apache.atlas.services.DefaultMetadataService.getEntityDefinitionReference(DefaultMetadataService.java:319)\n\tat
>
> org.apache.atlas.services.DefaultMetadataService.getEntityDefinition(DefaultMetadataService.java:327)\n\tat
>
> org.apache.atlas.web.resources.EntityResource.getEntityDefinitionByAttribute(EntityResource.java:525)\n\tat
>
> org.apache.atlas.web.resources.EntityResource.getEntity(EntityResource.java:506)\n\tat
> sun.reflect.GeneratedMethodAccessor77.invoke(Unknown Source)\n\tat
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat
> java.lang.reflect.Method.invoke(Method.java:606)\n\tat
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)\n\tat
>
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)\n\tat
>
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)\n\tat
>
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)\n\tat
>
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)\n\tat
>
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
>
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)\n\tat
>
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)\n\tat
>
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)\n\tat
>
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)\n\tat
>
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)\n\tat
>
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)\n\tat
>
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)\n\tat
>
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)\n\tat
> javax.servlet.http.HttpServlet.service(HttpServlet.java:790)\n\tat
> com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:286)\n\tat
>
> com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:276)\n\tat
>
> com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:181)\n\tat
>
> com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)\n\tat
>
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:85)\n\tat
> org.apache.atlas.web.filters.AuditFilter.doFilter(AuditFilter.java:73)\n\tat
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)\n\tat
>
> com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:120)\n\tat
> com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:135)\n\tat
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)\n\tat
>
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330)\n\tat
>
> org.apache.atlas.web.filters.AtlasAuthorizationFilter.doFilter(AtlasAuthorizationFilter.java:154)\n\tat
>
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)\n\tat
>
>
[jira] [Commented] (ATLAS-1324) Fix SecureEmbeddedServerTest.testServerConfiguredUsingCredentialProvider UT failure
[
https://issues.apache.org/jira/browse/ATLAS-1324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15693141#comment-15693141
]
Vimal Sharma commented on ATLAS-1324:
-
+1
> Fix SecureEmbeddedServerTest.testServerConfiguredUsingCredentialProvider UT
> failure
> ---
>
> Key: ATLAS-1324
> URL: https://issues.apache.org/jira/browse/ATLAS-1324
> Project: Atlas
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: Ayub Khan
>Assignee: Ayub Khan
> Fix For: trunk
>
> Attachments: ATLAS-1324.patch
>
>
> {noformat}
> testServerConfiguredUsingCredentialProvider(org.apache.atlas.web.service.SecureEmbeddedServerTest)
> Time elapsed: 16.378 sec <<< FAILURE!
> java.lang.AssertionError: War deploy failed
> at org.testng.Assert.fail(Assert.java:89)
> at org.testng.Assert.failNotEquals(Assert.java:489)
> at org.testng.Assert.assertEquals(Assert.java:118)
> at org.testng.Assert.assertEquals(Assert.java:365)
> at org.testng.Assert.assertEquals(Assert.java:375)
> at
> org.apache.atlas.web.service.SecureEmbeddedServerTest.testServerConfiguredUsingCredentialProvider(SecureEmbeddedServerTest.java:76)
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m;
> support was removed in 8.0
> Running org.apache.atlas.web.service.ServiceStateTest
> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.484 sec -
> in org.apache.atlas.web.service.ServiceStateTest
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m;
> support was removed in 8.0
> Running org.apache.atlas.web.setup.SetupStepsTest
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.66 sec - in
> org.apache.atlas.web.setup.SetupStepsTest
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m;
> support was removed in 8.0
> Running org.apache.atlas.web.TestUtils
> Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.149 sec -
> in org.apache.atlas.web.TestUtils
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m;
> support was removed in 8.0
> Running org.apache.atlas.web.util.ServletsTest
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.417 sec -
> in org.apache.atlas.web.util.ServletsTest
> Results :
> Failed tests:
> SecureEmbeddedServerTest.testServerConfiguredUsingCredentialProvider:78 War
> deploy failed
> Tests run: 107, Failures: 1, Errors: 0, Skipped: 0
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (ATLAS-1321) Fix failure of Hive ITs
[
https://issues.apache.org/jira/browse/ATLAS-1321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15692992#comment-15692992
]
Vimal Sharma edited comment on ATLAS-1321 at 11/24/16 11:13 AM:
Thanks [~ayubkhan] for reviewing. It was a great catch. Uploading the revised
patch
was (Author: svimal2106):
Thanks [~ayubkhan] for reviewing. Uploading the revised patch
> Fix failure of Hive ITs
> ---
>
> Key: ATLAS-1321
> URL: https://issues.apache.org/jira/browse/ATLAS-1321
> Project: Atlas
> Issue Type: Bug
>Reporter: Vimal Sharma
>Assignee: Vimal Sharma
> Attachments: ATLAS-1321-v2.patch, ATLAS-1321.patch
>
>
> Hive ITs fail because the Atlas TypeDef initializer cannot locate models
> directory. None of the types defined in hive-model.json are regsitered.
> Below is the stack trace:
> Caused by: org.apache.atlas.AtlasServiceException: Metadata service API
> org.apache.atlas.AtlasBaseClient$APIInfo@6398e143 failed with status 400 (Bad
> Request) Response Body ({"error":"Unknown datatype:
> hive_db","stackTrace":"org.apache.atlas.typesystem.exception.TypeNotFoundException:
> Unknown datatype: hive_db\n\tat
> org.apache.atlas.typesystem.types.TypeSystem.getDataType(TypeSystem.java:192)\n\tat
>
> org.apache.atlas.services.DefaultMetadataService.validateTypeExists(DefaultMetadataService.java:519)\n\tat
>
> org.apache.atlas.services.DefaultMetadataService.getEntityDefinitionReference(DefaultMetadataService.java:319)\n\tat
>
> org.apache.atlas.services.DefaultMetadataService.getEntityDefinition(DefaultMetadataService.java:327)\n\tat
>
> org.apache.atlas.web.resources.EntityResource.getEntityDefinitionByAttribute(EntityResource.java:525)\n\tat
>
> org.apache.atlas.web.resources.EntityResource.getEntity(EntityResource.java:506)\n\tat
> sun.reflect.GeneratedMethodAccessor77.invoke(Unknown Source)\n\tat
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat
> java.lang.reflect.Method.invoke(Method.java:606)\n\tat
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)\n\tat
>
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)\n\tat
>
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)\n\tat
>
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)\n\tat
>
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)\n\tat
>
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
>
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)\n\tat
>
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)\n\tat
>
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)\n\tat
>
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)\n\tat
>
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)\n\tat
>
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)\n\tat
>
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)\n\tat
>
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)\n\tat
> javax.servlet.http.HttpServlet.service(HttpServlet.java:790)\n\tat
> com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:286)\n\tat
>
> com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:276)\n\tat
>
> com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:181)\n\tat
>
> com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)\n\tat
>
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:85)\n\tat
> org.apache.atlas.web.filters.AuditFilter.doFilter(AuditFilter.java:73)\n\tat
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)\n\tat
>
> com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:120)\n\tat
> com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:135)\n\tat
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)\n\tat
>
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330)\n\tat
>
>
[jira] [Created] (ATLAS-1321) Fix failure of Hive ITs
Vimal Sharma created ATLAS-1321:
---
Summary: Fix failure of Hive ITs
Key: ATLAS-1321
URL: https://issues.apache.org/jira/browse/ATLAS-1321
Project: Atlas
Issue Type: Bug
Reporter: Vimal Sharma
Assignee: Vimal Sharma
Hive ITs fail because the Atlas TypeDef initializer cannot locate models
directory. None of the types defined in hive-model.json are regsitered.
Below is the stack trace:
Caused by: org.apache.atlas.AtlasServiceException: Metadata service API
org.apache.atlas.AtlasBaseClient$APIInfo@6398e143 failed with status 400 (Bad
Request) Response Body ({"error":"Unknown datatype:
hive_db","stackTrace":"org.apache.atlas.typesystem.exception.TypeNotFoundException:
Unknown datatype: hive_db\n\tat
org.apache.atlas.typesystem.types.TypeSystem.getDataType(TypeSystem.java:192)\n\tat
org.apache.atlas.services.DefaultMetadataService.validateTypeExists(DefaultMetadataService.java:519)\n\tat
org.apache.atlas.services.DefaultMetadataService.getEntityDefinitionReference(DefaultMetadataService.java:319)\n\tat
org.apache.atlas.services.DefaultMetadataService.getEntityDefinition(DefaultMetadataService.java:327)\n\tat
org.apache.atlas.web.resources.EntityResource.getEntityDefinitionByAttribute(EntityResource.java:525)\n\tat
org.apache.atlas.web.resources.EntityResource.getEntity(EntityResource.java:506)\n\tat
sun.reflect.GeneratedMethodAccessor77.invoke(Unknown Source)\n\tat
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat
java.lang.reflect.Method.invoke(Method.java:606)\n\tat
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)\n\tat
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)\n\tat
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)\n\tat
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)\n\tat
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)\n\tat
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)\n\tat
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)\n\tat
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)\n\tat
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)\n\tat
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)\n\tat
com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)\n\tat
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)\n\tat
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)\n\tat
javax.servlet.http.HttpServlet.service(HttpServlet.java:790)\n\tat
com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:286)\n\tat
com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:276)\n\tat
com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:181)\n\tat
com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)\n\tat
com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:85)\n\tat
org.apache.atlas.web.filters.AuditFilter.doFilter(AuditFilter.java:73)\n\tat
com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)\n\tat
com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:120)\n\tat
com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:135)\n\tat
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)\n\tat
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330)\n\tat
org.apache.atlas.web.filters.AtlasAuthorizationFilter.doFilter(AtlasAuthorizationFilter.java:154)\n\tat
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)\n\tat
org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:118)\n\tat
org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:84)\n\tat
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)\n\tat
[jira] [Commented] (ATLAS-1318) Atlas Type System does not have DELETE API
[ https://issues.apache.org/jira/browse/ATLAS-1318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15689063#comment-15689063 ] Vimal Sharma commented on ATLAS-1318: - [~breadpowder] Atlas does not support Delete/Update API for types. The reason is that if we support update/delete of types, the old data which was registered using original type will be inconsistent with the new typesytem. This will lead to backward compatibility issues. Addition of optional attributes to existing types is supported. Please look into https://issues.apache.org/jira/browse/ATLAS-1174 for more details. If you want to add/delete required attributes, then you will have to create a new type with a different name. > Atlas Type System does not have DELETE API > -- > > Key: ATLAS-1318 > URL: https://issues.apache.org/jira/browse/ATLAS-1318 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.7-incubating >Reporter: Zineng Yuan > > I am trying to extend Atlas Type System by adding custom data type. However, > when I found a type name was misspecified and needed to be recreated, I can't > find a Restful Delete API. > Question is does Atlas expose a Delete API for custom data types/attributes? > Without this delete API, it's difficult to rely on Atlas as a meta store to > extend custom data. > Please do suggest how to recreate a data type in this case. Thank you! > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-1315) Fix webapp Integration tests
[ https://issues.apache.org/jira/browse/ATLAS-1315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vimal Sharma updated ATLAS-1315: Attachment: ATLAS-1315.patch Uploading Apoorv's patch. Tests in description are failing. Looking into it > Fix webapp Integration tests > > > Key: ATLAS-1315 > URL: https://issues.apache.org/jira/browse/ATLAS-1315 > Project: Atlas > Issue Type: Bug >Reporter: Vimal Sharma > Fix For: trunk > > Attachments: ATLAS-1315.patch > > > webapp tests are failing. Below are the failing tests > EntityNotificationIT.testCreateEntity:90 NullPointer > EntityNotificationIT.testDeleteEntity:119 NullPointer > EntityJerseyResourceIT.testEntityDeduping:233 » AtlasService Metadata > service ... > org.apache.atlas.web.resources.EntityJerseyResourceIT.testEntityInvalidValue(org.apache.atlas.web.resources.EntityJerseyResourceIT) > Run 1: EntityJerseyResourceIT.testEntityInvalidValue:291 Expected > AtlasServiceException > Run 2: EntityJerseyResourceIT.testEntityInvalidValue:291 Expected > AtlasServiceException > EntityJerseyResourceIT.testSubmitEntity:128 NullPointer > EntityJerseyResourceIT.testSubmitEntityWithBadDateFormat:323 Was expecting > an exception here > EntityJerseyResourceIT.testUTF8:754 NullPointer > EntityLineageJerseyResourceIT.testInputLineageInfo:74 expected:<200> but > was:<404> > EntityLineageJerseyResourceIT.testLineageInfo:134 expected:<200> but > was:<404> > EntityLineageJerseyResourceIT.testOutputLineageInfo:104 expected:<200> but > was:<404> > MetadataDiscoveryJerseyResourceIT.testSearchByDSL:76 expected:<200> but > was:<400> > MetadataDiscoveryJerseyResourceIT.testSearchDSLLimits:108 expected:<200> > but was:<400> > MetadataDiscoveryJerseyResourceIT.testSearchUsingDSL:196 expected: but > was: > TypedefsJerseyResourceIT.testCreate:86 » AtlasService Metadata service API > org... > TypedefsJerseyResourceIT.testDuplicateCreate:98 » AtlasService Metadata > servic... > TypedefsJerseyResourceIT.testListTypesByFilter:254 » AtlasService Metadata > ser... > TypedefsJerseyResourceIT.testUpdate:118 » AtlasService Metadata service API > or... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (ATLAS-1315) Fix webapp Integration tests
[ https://issues.apache.org/jira/browse/ATLAS-1315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15685909#comment-15685909 ] Vimal Sharma edited comment on ATLAS-1315 at 11/22/16 7:03 AM: --- Uploading [~apoorvnaik]'s patch. Tests in description are failing. Looking into it was (Author: svimal2106): Uploading Apoorv's patch. Tests in description are failing. Looking into it > Fix webapp Integration tests > > > Key: ATLAS-1315 > URL: https://issues.apache.org/jira/browse/ATLAS-1315 > Project: Atlas > Issue Type: Bug >Reporter: Vimal Sharma > Fix For: trunk > > Attachments: ATLAS-1315.patch > > > webapp tests are failing. Below are the failing tests > EntityNotificationIT.testCreateEntity:90 NullPointer > EntityNotificationIT.testDeleteEntity:119 NullPointer > EntityJerseyResourceIT.testEntityDeduping:233 » AtlasService Metadata > service ... > org.apache.atlas.web.resources.EntityJerseyResourceIT.testEntityInvalidValue(org.apache.atlas.web.resources.EntityJerseyResourceIT) > Run 1: EntityJerseyResourceIT.testEntityInvalidValue:291 Expected > AtlasServiceException > Run 2: EntityJerseyResourceIT.testEntityInvalidValue:291 Expected > AtlasServiceException > EntityJerseyResourceIT.testSubmitEntity:128 NullPointer > EntityJerseyResourceIT.testSubmitEntityWithBadDateFormat:323 Was expecting > an exception here > EntityJerseyResourceIT.testUTF8:754 NullPointer > EntityLineageJerseyResourceIT.testInputLineageInfo:74 expected:<200> but > was:<404> > EntityLineageJerseyResourceIT.testLineageInfo:134 expected:<200> but > was:<404> > EntityLineageJerseyResourceIT.testOutputLineageInfo:104 expected:<200> but > was:<404> > MetadataDiscoveryJerseyResourceIT.testSearchByDSL:76 expected:<200> but > was:<400> > MetadataDiscoveryJerseyResourceIT.testSearchDSLLimits:108 expected:<200> > but was:<400> > MetadataDiscoveryJerseyResourceIT.testSearchUsingDSL:196 expected: but > was: > TypedefsJerseyResourceIT.testCreate:86 » AtlasService Metadata service API > org... > TypedefsJerseyResourceIT.testDuplicateCreate:98 » AtlasService Metadata > servic... > TypedefsJerseyResourceIT.testListTypesByFilter:254 » AtlasService Metadata > ser... > TypedefsJerseyResourceIT.testUpdate:118 » AtlasService Metadata service API > or... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-1315) Fix webapp Integration tests
Vimal Sharma created ATLAS-1315: --- Summary: Fix webapp Integration tests Key: ATLAS-1315 URL: https://issues.apache.org/jira/browse/ATLAS-1315 Project: Atlas Issue Type: Bug Reporter: Vimal Sharma Fix For: trunk webapp tests are failing. Below are the failing tests EntityNotificationIT.testCreateEntity:90 NullPointer EntityNotificationIT.testDeleteEntity:119 NullPointer EntityJerseyResourceIT.testEntityDeduping:233 » AtlasService Metadata service ... org.apache.atlas.web.resources.EntityJerseyResourceIT.testEntityInvalidValue(org.apache.atlas.web.resources.EntityJerseyResourceIT) Run 1: EntityJerseyResourceIT.testEntityInvalidValue:291 Expected AtlasServiceException Run 2: EntityJerseyResourceIT.testEntityInvalidValue:291 Expected AtlasServiceException EntityJerseyResourceIT.testSubmitEntity:128 NullPointer EntityJerseyResourceIT.testSubmitEntityWithBadDateFormat:323 Was expecting an exception here EntityJerseyResourceIT.testUTF8:754 NullPointer EntityLineageJerseyResourceIT.testInputLineageInfo:74 expected:<200> but was:<404> EntityLineageJerseyResourceIT.testLineageInfo:134 expected:<200> but was:<404> EntityLineageJerseyResourceIT.testOutputLineageInfo:104 expected:<200> but was:<404> MetadataDiscoveryJerseyResourceIT.testSearchByDSL:76 expected:<200> but was:<400> MetadataDiscoveryJerseyResourceIT.testSearchDSLLimits:108 expected:<200> but was:<400> MetadataDiscoveryJerseyResourceIT.testSearchUsingDSL:196 expected: but was: TypedefsJerseyResourceIT.testCreate:86 » AtlasService Metadata service API org... TypedefsJerseyResourceIT.testDuplicateCreate:98 » AtlasService Metadata servic... TypedefsJerseyResourceIT.testListTypesByFilter:254 » AtlasService Metadata ser... TypedefsJerseyResourceIT.testUpdate:118 » AtlasService Metadata service API or... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1313) Tests SSLAndKerberosTest.testService and SSLTest.testService are failing
[
https://issues.apache.org/jira/browse/ATLAS-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15683548#comment-15683548
]
Vimal Sharma commented on ATLAS-1313:
-
+1
> Tests SSLAndKerberosTest.testService and SSLTest.testService are failing
> -
>
> Key: ATLAS-1313
> URL: https://issues.apache.org/jira/browse/ATLAS-1313
> Project: Atlas
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: Vimal Sharma
>Assignee: Ayub Khan
> Fix For: trunk
>
> Attachments: ATLAS-1313.patch
>
>
> Tests SSLAndKerberosTest.testService and SSLTest.testService are failing with
> the below trace
> testService(org.apache.atlas.web.security.SSLTest) Time elapsed: 0.333 sec
> <<< FAILURE!
> org.apache.atlas.AtlasServiceException: Metadata service API
> org.apache.atlas.AtlasBaseClient$APIInfo@5d4ca7d9 failed with status 400 (Bad
> Request) Response Body ({"error":"Given search filter did not yield any
> results ","stackTrace":"java.lang.Exception: Given search filter did not
> yield any results \n\tat
> org.apache.atlas.web.resources.TypesResource.getTypesByFilter(TypesResource.java:289)\n\tat
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n\tat
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)\n\tat
>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat
> java.lang.reflect.Method.invoke(Method.java:606)\n\tat
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)\n\tat
>
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)\n\tat
>
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)\n\tat
>
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)\n\tat
>
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)\n\tat
>
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
>
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)\n\tat
>
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)\n\tat
>
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)\n\tat
>
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)\n\tat
>
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)\n\tat
>
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)\n\tat
>
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)\n\tat
>
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)\n\tat
> javax.servlet.http.HttpServlet.service(HttpServlet.java:790)\n\tat
> com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:286)\n\tat
>
> com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:276)\n\tat
>
> com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:181)\n\tat
>
> com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)\n\tat
>
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:85)\n\tat
> org.apache.atlas.web.filters.AuditFilter.doFilter(AuditFilter.java:71)\n\tat
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)\n\tat
>
> com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:120)\n\tat
> com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:135)\n\tat
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)\n\tat
>
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330)\n\tat
>
> org.apache.atlas.web.filters.AtlasAuthorizationFilter.doFilter(AtlasAuthorizationFilter.java:154)\n\tat
>
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)\n\tat
>
> org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:118)\n\tat
>
> org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:84)\n\tat
>
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)\n\tat
>
>
[jira] [Created] (ATLAS-1313) Tests SSLAndKerberosTest.testService and SSLTest.testService are failing
Vimal Sharma created ATLAS-1313:
---
Summary: Tests SSLAndKerberosTest.testService and
SSLTest.testService are failing
Key: ATLAS-1313
URL: https://issues.apache.org/jira/browse/ATLAS-1313
Project: Atlas
Issue Type: Bug
Reporter: Vimal Sharma
Tests SSLAndKerberosTest.testService and SSLTest.testService are failing with
the below trace
testService(org.apache.atlas.web.security.SSLTest) Time elapsed: 0.333 sec
<<< FAILURE!
org.apache.atlas.AtlasServiceException: Metadata service API
org.apache.atlas.AtlasBaseClient$APIInfo@5d4ca7d9 failed with status 400 (Bad
Request) Response Body ({"error":"Given search filter did not yield any results
","stackTrace":"java.lang.Exception: Given search filter did not yield any
results \n\tat
org.apache.atlas.web.resources.TypesResource.getTypesByFilter(TypesResource.java:289)\n\tat
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n\tat
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)\n\tat
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat
java.lang.reflect.Method.invoke(Method.java:606)\n\tat
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)\n\tat
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)\n\tat
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)\n\tat
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)\n\tat
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)\n\tat
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)\n\tat
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)\n\tat
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)\n\tat
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)\n\tat
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)\n\tat
com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)\n\tat
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)\n\tat
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)\n\tat
javax.servlet.http.HttpServlet.service(HttpServlet.java:790)\n\tat
com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:286)\n\tat
com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:276)\n\tat
com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:181)\n\tat
com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)\n\tat
com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:85)\n\tat
org.apache.atlas.web.filters.AuditFilter.doFilter(AuditFilter.java:71)\n\tat
com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)\n\tat
com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:120)\n\tat
com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:135)\n\tat
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)\n\tat
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330)\n\tat
org.apache.atlas.web.filters.AtlasAuthorizationFilter.doFilter(AtlasAuthorizationFilter.java:154)\n\tat
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)\n\tat
org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:118)\n\tat
org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:84)\n\tat
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)\n\tat
org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:113)\n\tat
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)\n\tat
org.springframework.security.web.session.SessionManagementFilter.doFilter(SessionManagementFilter.java:103)\n\tat
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)\n\tat
[jira] [Commented] (ATLAS-1303) Update hashCode and equals method to use standard JDK libraries
[ https://issues.apache.org/jira/browse/ATLAS-1303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15682699#comment-15682699 ] Vimal Sharma commented on ATLAS-1303: - I think there is a review board request for this JIRA. Can you add the review board link > Update hashCode and equals method to use standard JDK libraries > --- > > Key: ATLAS-1303 > URL: https://issues.apache.org/jira/browse/ATLAS-1303 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.8-incubating >Reporter: Apoorv Naik >Assignee: Apoorv Naik > Fix For: 0.8-incubating > > Attachments: 0001-Updated-equals-and-hashCode-signatures.patch > > > Currently all the hashCode and equals methods use numerous if-else branches > to determine the result. This change uses the existing JDK7 > Objects.equals(...) and Objects.hashCode(...) instead. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1291) Type "hive_column_lineage" not present in hive_model.json
[
https://issues.apache.org/jira/browse/ATLAS-1291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15678921#comment-15678921
]
Vimal Sharma commented on ATLAS-1291:
-
[~madhan.neethiraj] Before the commit for ATLAS-1272, the below code in
HiveDataModelGenerator was responsible for creating hive_column_lineage type. I
have created JSON for hive_column_lineage type in the patch looking at the
corresponding code in HiveDataModelGenerator. Please checkout to commit before
ATLAS-1272 to get details
{code}
private void createColumnLineageClass() throws AtlasException {
AttributeDefinition[] attributeDefinitions = new AttributeDefinition[]{
new AttributeDefinition("query",
HiveDataTypes.HIVE_PROCESS.getName(),
Multiplicity.REQUIRED, false, null),
new
AttributeDefinition("depenendencyType",DataTypes.STRING_TYPE.getName(),
Multiplicity.REQUIRED, false, null),
new
AttributeDefinition("expression",DataTypes.STRING_TYPE.getName(),
Multiplicity.OPTIONAL, false, null)
};
HierarchicalTypeDefinition definition =
new HierarchicalTypeDefinition<>(ClassType.class,
HiveDataTypes.HIVE_COLUMN_LINEAGE.getName(), null,
ImmutableSet.of(AtlasClient.PROCESS_SUPER_TYPE),
attributeDefinitions);
classTypeDefinitions.put(HiveDataTypes.HIVE_COLUMN_LINEAGE.getName(),
definition);
LOG.debug("Created definition for " +
HiveDataTypes.HIVE_COLUMN_LINEAGE.getName());
}
{code}
> Type "hive_column_lineage" not present in hive_model.json
> -
>
> Key: ATLAS-1291
> URL: https://issues.apache.org/jira/browse/ATLAS-1291
> Project: Atlas
> Issue Type: Bug
>Reporter: Vimal Sharma
>Assignee: Vimal Sharma
> Attachments: ATLAS-1291.patch
>
>
> Type "hive_column_lineage" was generated in HiveDataModelGenerator.java.
> The above file has been deprecated and the types are now registered from
> hive_model.json inside models directory.
> This file does not contain the type definition JSON for type
> "hive_column_lineage". Due to this, column level lineage hook messages are
> failing to be registered with Atlas.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-916) Return system attributes in get entity definition
[ https://issues.apache.org/jira/browse/ATLAS-916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vimal Sharma updated ATLAS-916: --- Attachment: ATLAS-916-v8.patch Attaching the latest patch which has been committed > Return system attributes in get entity definition > - > > Key: ATLAS-916 > URL: https://issues.apache.org/jira/browse/ATLAS-916 > Project: Atlas > Issue Type: Improvement >Reporter: Shwetha G S >Assignee: Vimal Sharma > Fix For: 0.8-incubating > > Attachments: ATLAS-916-v2.patch, ATLAS-916-v3-rebased.patch, > ATLAS-916-v4.patch, ATLAS-916-v8.patch, ATLAS-916.patch > > > Atlas should maintain system attributes created time, last modified time, > created by user and last modified by user for every entity. This information > should be returned in get entity definition -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-1291) Type "hive_column_lineage" not present in hive_model.json
[ https://issues.apache.org/jira/browse/ATLAS-1291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vimal Sharma updated ATLAS-1291: Attachment: ATLAS-1291.patch > Type "hive_column_lineage" not present in hive_model.json > - > > Key: ATLAS-1291 > URL: https://issues.apache.org/jira/browse/ATLAS-1291 > Project: Atlas > Issue Type: Bug >Reporter: Vimal Sharma > Attachments: ATLAS-1291.patch > > > Type "hive_column_lineage" was generated in HiveDataModelGenerator.java. > The above file has been deprecated and the types are now registered from > hive_model.json inside models directory. > This file does not contain the type definition JSON for type > "hive_column_lineage". Due to this, column level lineage hook messages are > failing to be registered with Atlas. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1299) The project org.apache.atlas:atlas-hbase-client-shaded:[unknown-version] (/xx/xx/incubator-atlas/shaded/hbase-client-shaded/pom.xml) has 1 error
[ https://issues.apache.org/jira/browse/ATLAS-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15673364#comment-15673364 ] Vimal Sharma commented on ATLAS-1299: - +1 > The project org.apache.atlas:atlas-hbase-client-shaded:[unknown-version] > (/xx/xx/incubator-atlas/shaded/hbase-client-shaded/pom.xml) has 1 error > > > Key: ATLAS-1299 > URL: https://issues.apache.org/jira/browse/ATLAS-1299 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.8-incubating > Environment: Centos 6.7;jdk 1.7.0_95;maven 3.3.9 >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Critical > Labels: patch > Attachments: ATLAS-1299.patch > > > Repetition of steps: > 1. Run command:git clone > https://git-wip-us.apache.org/repos/asf/incubator-atlas.git; > 2. Run command in the root path of atlas:export MAVEN_OPTS="-Xmx1536m > -XX:MaxPermSize=512m" && mvn clean package -Pdist -DskipTests. > Result: > [ERROR] The build could not read 2 projects -> [Help 1] > [ERROR] > [ERROR] The project > org.apache.atlas:atlas-hbase-client-shaded:[unknown-version] > (/home/pengjianhua/opensource/incubator-atlas/shaded/hbase-client-shaded/pom.xml) > has 1 error > [ERROR] Non-resolvable parent POM for > org.apache.atlas:atlas-hbase-client-shaded:[unknown-version]: Could not find > artifact org.apache.atlas:apache-atlas:pom:0.8-incubating-SNAPSHOT and > 'parent.relativePath' points at wrong local POM @ line 22, column 13 -> [Help > 2] > [ERROR] > [ERROR] The project > org.apache.atlas:atlas-hbase-server-shaded:[unknown-version] > (/home/pengjianhua/opensource/incubator-atlas/shaded/hbase-server-shaded/pom.xml) > has 1 error > [ERROR] Non-resolvable parent POM for > org.apache.atlas:atlas-hbase-server-shaded:[unknown-version]: Could not find > artifact org.apache.atlas:apache-atlas:pom:0.8-incubating-SNAPSHOT and > 'parent.relativePath' points at wrong local POM @ line 22, column 13 -> [Help > 2] > [ERROR] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1298) UI never finishes loading
[ https://issues.apache.org/jira/browse/ATLAS-1298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15671171#comment-15671171 ] Vimal Sharma commented on ATLAS-1298: - Can you attach the application.log anyway. > UI never finishes loading > - > > Key: ATLAS-1298 > URL: https://issues.apache.org/jira/browse/ATLAS-1298 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.7-incubating > Environment: Atlas 0.7 - Profile Berkeley/ElasticSearch >Reporter: PJ Van Aeken > > The REST API works fine, and I can see the data from the quickstart script > but when I go to the UI, I only get the login screen, followed by the > two-tone background and a "loading circle" which never completes loading. > There are no errors in application.log. > Note: I am running inside a docker container but port 21000 is exposed to the > host. I am querying the API from my browser on the host machine, so not from > inside the docker container. It works with both localhost and the internal > docker ip. > Any help debugging/fixing this would be greatly appreciated. > *EDIT:* Running the master branch outside of docker, "mylaptopname:21000" > works just fine but "localhost:21000" suffers from the same issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1299) The project org.apache.atlas:atlas-hbase-client-shaded:[unknown-version] (/xx/xx/incubator-atlas/shaded/hbase-client-shaded/pom.xml) has 1 error
[ https://issues.apache.org/jira/browse/ATLAS-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15671158#comment-15671158 ] Vimal Sharma commented on ATLAS-1299: - I could not reproduce the issue after following the mentioned steps. Can you try "mvn clean install -DskipTests" before "mvn clean package" > The project org.apache.atlas:atlas-hbase-client-shaded:[unknown-version] > (/xx/xx/incubator-atlas/shaded/hbase-client-shaded/pom.xml) has 1 error > > > Key: ATLAS-1299 > URL: https://issues.apache.org/jira/browse/ATLAS-1299 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.8-incubating > Environment: Centos 6.7;jdk 1.7.0_95;maven 3.3.9 >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Critical > Labels: patch > > Repetition of steps: > 1. Run command:git clone > https://git-wip-us.apache.org/repos/asf/incubator-atlas.git; > 2. Run command in the root path of atlas:export MAVEN_OPTS="-Xmx1536m > -XX:MaxPermSize=512m" && mvn clean package -Pdist -DskipTests. > Result: > [ERROR] The build could not read 2 projects -> [Help 1] > [ERROR] > [ERROR] The project > org.apache.atlas:atlas-hbase-client-shaded:[unknown-version] > (/home/pengjianhua/opensource/incubator-atlas/shaded/hbase-client-shaded/pom.xml) > has 1 error > [ERROR] Non-resolvable parent POM for > org.apache.atlas:atlas-hbase-client-shaded:[unknown-version]: Could not find > artifact org.apache.atlas:apache-atlas:pom:0.8-incubating-SNAPSHOT and > 'parent.relativePath' points at wrong local POM @ line 22, column 13 -> [Help > 2] > [ERROR] > [ERROR] The project > org.apache.atlas:atlas-hbase-server-shaded:[unknown-version] > (/home/pengjianhua/opensource/incubator-atlas/shaded/hbase-server-shaded/pom.xml) > has 1 error > [ERROR] Non-resolvable parent POM for > org.apache.atlas:atlas-hbase-server-shaded:[unknown-version]: Could not find > artifact org.apache.atlas:apache-atlas:pom:0.8-incubating-SNAPSHOT and > 'parent.relativePath' points at wrong local POM @ line 22, column 13 -> [Help > 2] > [ERROR] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-1297) HBaseBasedAuditRepositoryTest tests are failing
Vimal Sharma created ATLAS-1297: --- Summary: HBaseBasedAuditRepositoryTest tests are failing Key: ATLAS-1297 URL: https://issues.apache.org/jira/browse/ATLAS-1297 Project: Atlas Issue Type: Bug Reporter: Vimal Sharma After ATLAS-1246 commit, the tests in HBaseBasedAuditRepositoryTest are failing: Tests run: 6, Failures: 4, Errors: 0, Skipped: 2, Time elapsed: 1.734 sec <<< FAILURE! - in org.apache.atlas.repository.audit.HBaseBasedAuditRepositoryTest setup(org.apache.atlas.repository.audit.HBaseBasedAuditRepositoryTest) Time elapsed: 1.67 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) 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 org.apache.hadoop.hbase.util.JVMClusterUtil.createMasterThread(JVMClusterUtil.java:139) at org.apache.hadoop.hbase.LocalHBaseCluster.addMaster(LocalHBaseCluster.java:217) at org.apache.hadoop.hbase.LocalHBaseCluster.(LocalHBaseCluster.java:153) at org.apache.hadoop.hbase.LocalHBaseCluster.(LocalHBaseCluster.java:95) at org.apache.hadoop.hbase.LocalHBaseCluster.(LocalHBaseCluster.java:83) at org.apache.atlas.repository.audit.HBaseTestUtils.startCluster(HBaseTestUtils.java:40) at org.apache.atlas.repository.audit.HBaseBasedAuditRepositoryTest.setup(HBaseBasedAuditRepositoryTest.java:40) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1279) Remove QueryPlan attribute from Hive Process entity
[ https://issues.apache.org/jira/browse/ATLAS-1279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15666434#comment-15666434 ] Vimal Sharma commented on ATLAS-1279: - Committed to master. Thanks Shwetha for the review > Remove QueryPlan attribute from Hive Process entity > --- > > Key: ATLAS-1279 > URL: https://issues.apache.org/jira/browse/ATLAS-1279 > Project: Atlas > Issue Type: Bug >Reporter: Vimal Sharma >Assignee: Vimal Sharma > Fix For: 0.8-incubating > > Attachments: ATLAS-1279-v2.patch, ATLAS-1279.patch > > > The attribute QueryPlan is a required attribute of a Hive Process entity. > This attribute is not used anywhere. Further due to API changes in Hive LLAP > version, there is conflict in function call to get JSON Plan of query. The > function calls in Hive 1.2 and Hive 2 have different method signature. > Since, QueryPlan is not used, it should be removed so that Atlas code is > consistent for Hive 1.x and Hive 2.x -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1081) Atlas jetty server configuration
[ https://issues.apache.org/jira/browse/ATLAS-1081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15666252#comment-15666252 ] Vimal Sharma commented on ATLAS-1081: - +1 > Atlas jetty server configuration > > > Key: ATLAS-1081 > URL: https://issues.apache.org/jira/browse/ATLAS-1081 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Assignee: Shwetha G S > Fix For: 0.8-incubating > > Attachments: ATLAS-1081-v2.patch, ATLAS-1081.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-1279) Remove QueryPlan attribute from Hive Process entity
[ https://issues.apache.org/jira/browse/ATLAS-1279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vimal Sharma updated ATLAS-1279: Fix Version/s: 0.8-incubating > Remove QueryPlan attribute from Hive Process entity > --- > > Key: ATLAS-1279 > URL: https://issues.apache.org/jira/browse/ATLAS-1279 > Project: Atlas > Issue Type: Bug >Reporter: Vimal Sharma >Assignee: Vimal Sharma > Fix For: 0.8-incubating > > Attachments: ATLAS-1279-v2.patch, ATLAS-1279.patch > > > The attribute QueryPlan is a required attribute of a Hive Process entity. > This attribute is not used anywhere. Further due to API changes in Hive LLAP > version, there is conflict in function call to get JSON Plan of query. The > function calls in Hive 1.2 and Hive 2 have different method signature. > Since, QueryPlan is not used, it should be removed so that Atlas code is > consistent for Hive 1.x and Hive 2.x -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-1291) Type "hive_column_lineage" not present in hive_model.json
Vimal Sharma created ATLAS-1291: --- Summary: Type "hive_column_lineage" not present in hive_model.json Key: ATLAS-1291 URL: https://issues.apache.org/jira/browse/ATLAS-1291 Project: Atlas Issue Type: Bug Reporter: Vimal Sharma Type "hive_column_lineage" was generated in HiveDataModelGenerator.java. The above file has been deprecated and the types are now registered from hive_model.json inside models directory. This file does not contain the type definition JSON for type "hive_column_lineage". Due to this, column level lineage hook messages are failing to be registered with Atlas. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1081) Atlas jetty server configuration
[ https://issues.apache.org/jira/browse/ATLAS-1081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15663697#comment-15663697 ] Vimal Sharma commented on ATLAS-1081: - Why are there separate methods to get Integer, Long and String configuration values. Rest looks good to me. > Atlas jetty server configuration > > > Key: ATLAS-1081 > URL: https://issues.apache.org/jira/browse/ATLAS-1081 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha G S >Assignee: Shwetha G S > Fix For: 0.8-incubating > > Attachments: ATLAS-1081-v2.patch, ATLAS-1081.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-916) Return system attributes in get entity definition
[ https://issues.apache.org/jira/browse/ATLAS-916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vimal Sharma updated ATLAS-916: --- Attachment: ATLAS-916-v4.patch > Return system attributes in get entity definition > - > > Key: ATLAS-916 > URL: https://issues.apache.org/jira/browse/ATLAS-916 > Project: Atlas > Issue Type: Improvement >Reporter: Shwetha G S >Assignee: Vimal Sharma > Attachments: ATLAS-916-v2.patch, ATLAS-916-v3-rebased.patch, > ATLAS-916-v4.patch, ATLAS-916.patch > > > Atlas should maintain system attributes created time, last modified time, > created by user and last modified by user for every entity. This information > should be returned in get entity definition -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-1279) Remove QueryPlan attribute from Hive Process entity
[ https://issues.apache.org/jira/browse/ATLAS-1279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vimal Sharma updated ATLAS-1279: Attachment: ATLAS-1279-v2.patch Created ATLAS-1282 to track removal of queryplan attribute when support for required attribute removal is added Rebased the patch > Remove QueryPlan attribute from Hive Process entity > --- > > Key: ATLAS-1279 > URL: https://issues.apache.org/jira/browse/ATLAS-1279 > Project: Atlas > Issue Type: Bug >Reporter: Vimal Sharma >Assignee: Vimal Sharma > Attachments: ATLAS-1279-v2.patch, ATLAS-1279.patch > > > The attribute QueryPlan is a required attribute of a Hive Process entity. > This attribute is not used anywhere. Further due to API changes in Hive LLAP > version, there is conflict in function call to get JSON Plan of query. The > function calls in Hive 1.2 and Hive 2 have different method signature. > Since, QueryPlan is not used, it should be removed so that Atlas code is > consistent for Hive 1.x and Hive 2.x -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-1279) Remove QueryPlan attribute from Hive Process entity
[ https://issues.apache.org/jira/browse/ATLAS-1279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vimal Sharma updated ATLAS-1279: Attachment: (was: ATLAS-1279.patch) > Remove QueryPlan attribute from Hive Process entity > --- > > Key: ATLAS-1279 > URL: https://issues.apache.org/jira/browse/ATLAS-1279 > Project: Atlas > Issue Type: Bug >Reporter: Vimal Sharma >Assignee: Vimal Sharma > Attachments: ATLAS-1279-v2.patch, ATLAS-1279.patch > > > The attribute QueryPlan is a required attribute of a Hive Process entity. > This attribute is not used anywhere. Further due to API changes in Hive LLAP > version, there is conflict in function call to get JSON Plan of query. The > function calls in Hive 1.2 and Hive 2 have different method signature. > Since, QueryPlan is not used, it should be removed so that Atlas code is > consistent for Hive 1.x and Hive 2.x -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-1279) Remove QueryPlan attribute from Hive Process entity
[ https://issues.apache.org/jira/browse/ATLAS-1279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vimal Sharma updated ATLAS-1279: Attachment: ATLAS-1279.patch > Remove QueryPlan attribute from Hive Process entity > --- > > Key: ATLAS-1279 > URL: https://issues.apache.org/jira/browse/ATLAS-1279 > Project: Atlas > Issue Type: Bug >Reporter: Vimal Sharma >Assignee: Vimal Sharma > Attachments: ATLAS-1279.patch, ATLAS-1279.patch > > > The attribute QueryPlan is a required attribute of a Hive Process entity. > This attribute is not used anywhere. Further due to API changes in Hive LLAP > version, there is conflict in function call to get JSON Plan of query. The > function calls in Hive 1.2 and Hive 2 have different method signature. > Since, QueryPlan is not used, it should be removed so that Atlas code is > consistent for Hive 1.x and Hive 2.x -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1276) webapp test failures
[
https://issues.apache.org/jira/browse/ATLAS-1276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15653833#comment-15653833
]
Vimal Sharma commented on ATLAS-1276:
-
Webapp tests are also failing
Failed tests:
EntityNotificationIT.testCreateEntity:85->BaseResourceIT.createInstance:114 »
AtlasService
EntityNotificationIT.testDeleteEntity:111->BaseResourceIT.createInstance:114
» AtlasService
NotificationHookConsumerIT.testCreateEntity:89->BaseResourceIT.waitFor:287 »
...
NotificationHookConsumerIT.testDeleteByQualifiedName:164 » AtlasService
Metada...
NotificationHookConsumerIT.testMessageHandleFailureConsumerContinues:72->BaseResourceIT.waitFor:287
»
NotificationHookConsumerIT.testUpdateEntityFullUpdate:183 » AtlasService
Metad...
NotificationHookConsumerIT.testUpdateEntityPartial:111 » AtlasService
Metadata...
NotificationHookConsumerIT.testUpdatePartialUpdatingQualifiedName:136 »
AtlasService
DataSetLineageJerseyResourceIT.setUp:58->setupInstances:224->database:272->BaseResourceIT.createInstance:114
» AtlasService
EntityJerseyResourceIT.testDeleteEntitiesViaClientApi:874->BaseResourceIT.createInstance:114
» AtlasService
EntityJerseyResourceIT.testDeleteEntitiesViaRestApi:844->BaseResourceIT.createInstance:114
» AtlasService
EntityJerseyResourceIT.testDeleteEntityByUniqAttribute:903->BaseResourceIT.createInstance:114
» AtlasService
EntityJerseyResourceIT.testEntityDeduping:176 » AtlasService Metadata service
...
EntityJerseyResourceIT.testGetEntityByAttribute:283->BaseResourceIT.createInstance:114
» AtlasService
EntityJerseyResourceIT.testRequestUser:138 » AtlasService Metadata service
API...
EntityJerseyResourceIT.testSubmitEntity:115->BaseResourceIT.createInstance:114
» AtlasService
EntityJerseyResourceIT.testSubmitEntityWithBadDateFormat:299 expected:
but was:
EntityJerseyResourceIT.testSubmitSingleEntity:156 expected:<201> but was:<400>
Tests run: 82, Failures: 18, Errors: 0, Skipped: 27
> webapp test failures
>
>
> Key: ATLAS-1276
> URL: https://issues.apache.org/jira/browse/ATLAS-1276
> Project: Atlas
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: Shwetha G S
>Assignee: Ayub Khan
>Priority: Blocker
> Attachments: ATLAS-1276.patch
>
>
> Failed tests:
> QuickStartIT.runQuickStart:45 » AtlasService Metadata service API
> CREATE_TYPE ...
>
> EntityNotificationIT.setUp:73->BaseResourceIT.createTypeDefinitions:191->BaseResourceIT.createType:100->BaseResourceIT.createType:105
> » AtlasService
>
> NotificationHookConsumerIT.setUp:48->BaseResourceIT.createTypeDefinitions:191->BaseResourceIT.createType:100->BaseResourceIT.createType:105
> » AtlasService
>
> DataSetLineageJerseyResourceIT.setUp:57->BaseResourceIT.createTypeDefinitions:191->BaseResourceIT.createType:100->BaseResourceIT.createType:105
> » AtlasService
>
> EntityJerseyResourceIT.setUp:104->BaseResourceIT.createTypeDefinitions:191->BaseResourceIT.createType:100->BaseResourceIT.createType:105
> » AtlasService
> Tests run: 86, Failures: 5, Errors: 0, Skipped: 58
> Tests run: 34, Failures: 1, Errors: 0, Skipped: 33, Time elapsed: 1.593 sec
> <<< FAILURE! - in org.apache.atlas.web.resources.EntityJerseyResourceIT
> setUp(org.apache.atlas.web.resources.EntityJerseyResourceIT) Time elapsed:
> 1.446 sec <<< FAILURE!
> org.apache.atlas.AtlasServiceException: Metadata service API CREATE_TYPE
> failed with status 400 (Bad Request) Response Body ({"error":"Unknown
> datatype:
> DataSet","stackTrace":"org.apache.atlas.typesystem.exception.TypeNotFoundException:
> Unknown datatype: DataSet\n\tat
> org.apache.atlas.typesystem.types.TypeSystem.getDataType(TypeSystem.java:192)\n\tat
>
> org.apache.atlas.typesystem.types.TypeSystem$TransientTypeSystem.dataType(TypeSystem.java:398)\n\tat
>
> org.apache.atlas.typesystem.types.TypeSystem$TransientTypeSystem.validateSuperTypes(TypeSystem.java:460)\n\tat
>
> org.apache.atlas.typesystem.types.TypeSystem$TransientTypeSystem.validateAndSetupSuperTypes(TypeSystem.java:489)\n\tat
>
> org.apache.atlas.typesystem.types.TypeSystem$TransientTypeSystem.verifyTypes(TypeSystem.java:708)\n\tat
>
> org.apache.atlas.typesystem.types.TypeSystem.createTransientTypeSystem(TypeSystem.java:346)\n\tat
>
> org.apache.atlas.services.DefaultMetadataService.createOrUpdateTypes(DefaultMetadataService.java:189)\n\tat
>
> org.apache.atlas.services.DefaultMetadataService.createType(DefaultMetadataService.java:180)\n\tat
>
> org.apache.atlas.web.resources.TypesResource.submit(TypesResource.java:94)\n\tat
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n\tat
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)\n\tat
>
>
[jira] [Assigned] (ATLAS-1280) Build Atlas with Hive2
[ https://issues.apache.org/jira/browse/ATLAS-1280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vimal Sharma reassigned ATLAS-1280: --- Assignee: Vimal Sharma > Build Atlas with Hive2 > -- > > Key: ATLAS-1280 > URL: https://issues.apache.org/jira/browse/ATLAS-1280 > Project: Atlas > Issue Type: Bug >Reporter: Vimal Sharma >Assignee: Vimal Sharma > Attachments: ATLAS-1280.patch > > > Atlas is currently built with Hive version 1.2 > Due to significant changes in Hive2(LLAP), it might be useful to build Atlas > using the Hive 2.1.0 release. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-1280) Build Atlas with Hive2
[ https://issues.apache.org/jira/browse/ATLAS-1280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vimal Sharma updated ATLAS-1280: Attachment: ATLAS-1280.patch Attaching the patch with required changes in Atlas code to compile with Hive version 2.1.0 This JIRA will serve as a placeholder for migration to Hive2. Some IT tests in HiveHookIT are failing. Please build Atlas using -DskipTests option. Please try out this patch to verify that Atlas Hive Hook functions correctly. > Build Atlas with Hive2 > -- > > Key: ATLAS-1280 > URL: https://issues.apache.org/jira/browse/ATLAS-1280 > Project: Atlas > Issue Type: Bug >Reporter: Vimal Sharma > Attachments: ATLAS-1280.patch > > > Atlas is currently built with Hive version 1.2 > Due to significant changes in Hive2(LLAP), it might be useful to build Atlas > using the Hive 2.1.0 release. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-1276) webapp test failures
[
https://issues.apache.org/jira/browse/ATLAS-1276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15653764#comment-15653764
]
Vimal Sharma commented on ATLAS-1276:
-
Hive tests are also failing with the same error.
Caused by: org.apache.atlas.AtlasServiceException: Metadata service API
GET_ENTITY failed with status 400 (Bad Request) Response Body
({"error":"Unknown datatype:
hive_db","stackTrace":"org.apache.atlas.typesystem.exception.TypeNotFoundException:
Unknown datatype: hive_db\n\tat
org.apache.atlas.typesystem.types.TypeSystem.getDataType(TypeSystem.java:192)\n\tat
org.apache.atlas.services.DefaultMetadataService.validateTypeExists(DefaultMetadataService.java:491)\n\tat
org.apache.atlas.services.DefaultMetadataService.getEntityDefinitionReference(DefaultMetadataService.java:304)\n\tat
org.apache.atlas.services.DefaultMetadataService.getEntityDefinition(DefaultMetadataService.java:312)\n\tat
org.apache.atlas.web.resources.EntityResource.getEntityDefinitionByAttribute(EntityResource.java:572)\n\tat
org.apache.atlas.web.resources.EntityResource.getEntity(EntityResource.java:551)\n\tat
sun.reflect.GeneratedMethodAccessor77.invoke(Unknown Source)\n\tat
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat
java.lang.reflect.Method.invoke(Method.java:606)\n\tat
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)\n\tat
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)\n\tat
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)\n\tat
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)\n\tat
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)\n\tat
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)\n\tat
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)\n\tat
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)\n\tat
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)\n\tat
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)\n\tat
com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)\n\tat
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)\n\tat
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)\n\tat
javax.servlet.http.HttpServlet.service(HttpServlet.java:790)\n\tat
com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:286)\n\tat
com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:276)\n\tat
com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:181)\n\tat
com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)\n\tat
com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:85)\n\tat
org.apache.atlas.web.filters.AuditFilter.doFilter(AuditFilter.java:71)\n\tat
com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)\n\tat
com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:120)\n\tat
com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:135)\n\tat
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)\n\tat
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330)\n\tat
org.apache.atlas.web.filters.AtlasAuthorizationFilter.doFilter(AtlasAuthorizationFilter.java:154)\n\tat
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)\n\tat
org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:118)\n\tat
org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:84)\n\tat
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)\n\tat
org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:113)\n\tat
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)\n\tat
org.springframework.security.web.session.SessionManagementFilter.doFilter(SessionManagementFilter.java:103)\n\tat
