[jira] [Commented] (ATLAS-242) lineage hive table schema REST API does not accept any tableName value
[
https://issues.apache.org/jira/browse/ATLAS-242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14984921#comment-14984921
]
David Kaspar commented on ATLAS-242:
[~shwethags]: Thanks for help - it works properly when using this table format.
Please, feel free to close the issue as Invalid. Would it be possible to add
this note to the API documentation?
> lineage hive table schema REST API does not accept any tableName value
> --
>
> Key: ATLAS-242
> URL: https://issues.apache.org/jira/browse/ATLAS-242
> Project: Atlas
> Issue Type: Bug
>Reporter: David Kaspar
>
> This issue is filed for "RangerAtlasDemo_v4.ova" VM-image release.
> When I call:
> http://127.0.0.1:21000/api/atlas/lineage/hive/table/{tableName}/schema
> REST API method, then it always returns 404 Not Found and returns an error
> which claims that given {tableName} does not exist.
> Since REST API documentation (application.wadl) does not state details, I
> have tried to use existing Hive table names, existing GUIDs of Hive tables
> but none of them works.
> Similarly for /api/atlas/lineage/hive/table/{tableName}/outputs/graph and
> /api/atlas/lineage/hive/table/{tableName}/inputs/graph.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Issue Comment Deleted] (ATLAS-242) lineage hive table schema REST API does not accept any tableName value
[
https://issues.apache.org/jira/browse/ATLAS-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Kaspar updated ATLAS-242:
---
Comment: was deleted
(was: Hi,
I am on vacation until November 1st, 2015.
If you need any immediate assistance, please, contact my manager Martin Ryzl
(martin.r...@merck.com). Otherwise I will get back to you when I return.
Thanks,
David
Notice: This e-mail message, together with any attachments, contains
information of Merck & Co., Inc. (2000 Galloping Hill Road, Kenilworth,
New Jersey, USA 07033), and/or its affiliates Direct contact information
for affiliates is available at
http://www.merck.com/contact/contacts.html) that may be confidential,
proprietary copyrighted and/or legally privileged. It is intended solely
for the use of the individual or entity named on this message. If you are
not the intended recipient, and have received this message in error,
please notify us immediately by reply e-mail and then delete it from
your system.
)
> lineage hive table schema REST API does not accept any tableName value
> --
>
> Key: ATLAS-242
> URL: https://issues.apache.org/jira/browse/ATLAS-242
> Project: Atlas
> Issue Type: Bug
>Reporter: David Kaspar
>
> This issue is filed for "RangerAtlasDemo_v4.ova" VM-image release.
> When I call:
> http://127.0.0.1:21000/api/atlas/lineage/hive/table/{tableName}/schema
> REST API method, then it always returns 404 Not Found and returns an error
> which claims that given {tableName} does not exist.
> Since REST API documentation (application.wadl) does not state details, I
> have tried to use existing Hive table names, existing GUIDs of Hive tables
> but none of them works.
> Similarly for /api/atlas/lineage/hive/table/{tableName}/outputs/graph and
> /api/atlas/lineage/hive/table/{tableName}/inputs/graph.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ATLAS-242) lineage hive table schema REST API does not accept any tableName value
[
https://issues.apache.org/jira/browse/ATLAS-242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14980033#comment-14980033
]
David Kaspar commented on ATLAS-242:
Hi,
I am on vacation until November 1st, 2015.
If you need any immediate assistance, please, contact my manager Martin Ryzl
(martin.r...@merck.com). Otherwise I will get back to you when I return.
Thanks,
David
Notice: This e-mail message, together with any attachments, contains
information of Merck & Co., Inc. (2000 Galloping Hill Road, Kenilworth,
New Jersey, USA 07033), and/or its affiliates Direct contact information
for affiliates is available at
http://www.merck.com/contact/contacts.html) that may be confidential,
proprietary copyrighted and/or legally privileged. It is intended solely
for the use of the individual or entity named on this message. If you are
not the intended recipient, and have received this message in error,
please notify us immediately by reply e-mail and then delete it from
your system.
> lineage hive table schema REST API does not accept any tableName value
> --
>
> Key: ATLAS-242
> URL: https://issues.apache.org/jira/browse/ATLAS-242
> Project: Atlas
> Issue Type: Bug
>Reporter: David Kaspar
>
> This issue is filed for "RangerAtlasDemo_v4.ova" VM-image release.
> When I call:
> http://127.0.0.1:21000/api/atlas/lineage/hive/table/{tableName}/schema
> REST API method, then it always returns 404 Not Found and returns an error
> which claims that given {tableName} does not exist.
> Since REST API documentation (application.wadl) does not state details, I
> have tried to use existing Hive table names, existing GUIDs of Hive tables
> but none of them works.
> Similarly for /api/atlas/lineage/hive/table/{tableName}/outputs/graph and
> /api/atlas/lineage/hive/table/{tableName}/inputs/graph.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (ATLAS-241) Location aware Ranger conditions for Tag-based policy rules
David Kaspar created ATLAS-241: -- Summary: Location aware Ranger conditions for Tag-based policy rules Key: ATLAS-241 URL: https://issues.apache.org/jira/browse/ATLAS-241 Project: Atlas Issue Type: Bug Reporter: David Kaspar "This issue is based on "RangerAtlasDemo_v4.ova" VM-image release. I am filing this issue as "Bug" even through it might be rather a missing (or purposely hidden) feature. The Resource-based policy rules are having ability to express "Accessed from outside of location?" condition. This field was not working for me - I assume the it accepts a hard-coded list of location like (US, CH). I have tried several other countries... This condition is not possible to specify in Tag-based policy rules. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-240) Improve Atlas Search UI to provide hyperlinking between individual entities
David Kaspar created ATLAS-240: -- Summary: Improve Atlas Search UI to provide hyperlinking between individual entities Key: ATLAS-240 URL: https://issues.apache.org/jira/browse/ATLAS-240 Project: Atlas Issue Type: Bug Reporter: David Kaspar Priority: Minor This issue is filed for "RangerAtlasDemo_v4.ova" VM-image release. Filing as a "Bug" because I have not been able to file "Wish" issue type. As a user of Atlas Search UI, I would like to be able to navigate/hyperlink between individual entity details e.g. the UI for an entity representing specific table should display hyperlinks to related entities e.g. the database or the table columns. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-117) Build fails on the latest commit 48343db999...
[
https://issues.apache.org/jira/browse/ATLAS-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14736384#comment-14736384
]
David Kaspar commented on ATLAS-117:
[~doss...@gmail.com]: I have verified the ATLAS-117-4.patch and it compiles
without any issue.
> Build fails on the latest commit 48343db999...
> --
>
> Key: ATLAS-117
> URL: https://issues.apache.org/jira/browse/ATLAS-117
> Project: Atlas
> Issue Type: Bug
>Reporter: David Kaspar
>Assignee: Tom Beerbower
> Attachments: ATLAS-117-2.patch, ATLAS-117-3.patch, ATLAS-117-4.patch,
> ATLAS-117.patch
>
>
> Build fails when building the latest commit
> 48343db999b495458409644c8b9d2fd0bd9fa99d:
> {code}
> [INFO] Scanning for projects...
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for org.apache.atlas:atlas-webapp:war:0.6-incubating-SNAPSHOT
> [WARNING] 'build.plugins.plugin.version' for
> org.codehaus.mojo:keytool-maven-plugin is missing. @
> org.apache.atlas:atlas-webapp:[unknown-version],
> /Users/MYSELF/Projects/External/incubator-atlas/webapp/pom.xml, line 309,
> column 21
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they
> threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support
> building such malformed projects.
> [WARNING]
> [INFO]
>
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] apache-atlas
> [INFO] Apache Atlas Typesystem
> [INFO] Apache Atlas Client
> [INFO] Apache Atlas Notification
> [INFO] Apache Atlas Repository
> [INFO] Apache Atlas Web Application
> [INFO] Apache Atlas Documentation
> [INFO] Apache Atlas Hive Bridge
> [INFO]
>
> [INFO]
>
> [INFO] Building apache-atlas 0.6-incubating-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ apache-atlas ---
> [INFO] Deleting /Users/MYSELF/Projects/External/incubator-atlas/target
> [INFO] Deleting /Users/MYSELF/Projects/External/incubator-atlas (includes =
> [**/*.pyc], excludes = [])
> [INFO]
> [INFO] --- buildnumber-maven-plugin:1.0:create (default) @ apache-atlas ---
> [INFO] Checking for local modifications: skipped.
> [INFO] Updating project files from SCM: skipped.
> [WARNING] Cannot get the revision information from the scm repository,
> proceeding with revision of release :
> No such provider: 'https'.
> [INFO] Storing buildNumber: release at timestamp: 1440071695692
> [WARNING] Cannot get the branch information from the scm repository,
> proceeding with UNKNOWN_BRANCH :
> No such provider: 'https'.
> [INFO] Storing buildScmBranch: UNKNOWN_BRANCH
> [INFO]
> [INFO] --- maven-remote-resources-plugin:1.4:process (default) @ apache-atlas
> ---
> [INFO]
> [INFO] --- scala-maven-plugin:3.2.0:compile (scala-compile-first) @
> apache-atlas ---
> [INFO] No sources to compile
> [INFO]
> [INFO] --- scala-maven-plugin:3.2.0:testCompile (scala-test-compile-first) @
> apache-atlas ---
> [INFO] No sources to compile
> [INFO]
> [INFO] --- exec-maven-plugin:1.2.1:exec (python-test) @ apache-atlas ---
> test_jar_java_lookups_fail (TestMetadata.TestMetadata) ... ok
> test_jar_java_lookups_succeed_from_path (TestMetadata.TestMetadata) ... ok
> test_main (TestMetadata.TestMetadata) ... Apache Atlas Server started!!!
> ok
> --
> Ran 3 tests in 0.003s
> OK
> [INFO]
> [INFO] --- maven-site-plugin:3.2:attach-descriptor (attach-descriptor) @
> apache-atlas ---
> [INFO]
> [INFO] --- maven-assembly-plugin:2.2.1:single (default) @ apache-atlas ---
> [INFO] Reading assembly descriptor: src/main/assemblies/standalone-package.xml
> [INFO] Reading assembly descriptor: src/main/assemblies/src-package.xml
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] apache-atlas ... FAILURE [ 1.773
> s]
> [INFO] Apache Atlas Typesystem SKIPPED
> [INFO] Apache Atlas Client SKIPPED
> [INFO] Apache Atlas Notification .. SKIPPED
> [INFO] Apache Atlas Repository SKIPPED
> [INFO] Apache Atlas Web Application ... SKIPPED
> [INFO] Apache Atlas Documentation . SKIPPED
> [INFO] Apache Atlas Hive Bridge ... SKIPPED
> [INFO]
>
[jira] [Commented] (ATLAS-117) Build fails on the latest commit 48343db999...
[
https://issues.apache.org/jira/browse/ATLAS-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14730422#comment-14730422
]
David Kaspar commented on ATLAS-117:
I have verified the ATLAS-117-2.patch on my machine and it fixes the issue.
> Build fails on the latest commit 48343db999...
> --
>
> Key: ATLAS-117
> URL: https://issues.apache.org/jira/browse/ATLAS-117
> Project: Atlas
> Issue Type: Bug
>Reporter: David Kaspar
>Assignee: Tom Beerbower
> Attachments: ATLAS-117-2.patch, ATLAS-117.patch
>
>
> Build fails when building the latest commit
> 48343db999b495458409644c8b9d2fd0bd9fa99d:
> {code}
> [INFO] Scanning for projects...
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for org.apache.atlas:atlas-webapp:war:0.6-incubating-SNAPSHOT
> [WARNING] 'build.plugins.plugin.version' for
> org.codehaus.mojo:keytool-maven-plugin is missing. @
> org.apache.atlas:atlas-webapp:[unknown-version],
> /Users/MYSELF/Projects/External/incubator-atlas/webapp/pom.xml, line 309,
> column 21
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they
> threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support
> building such malformed projects.
> [WARNING]
> [INFO]
>
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] apache-atlas
> [INFO] Apache Atlas Typesystem
> [INFO] Apache Atlas Client
> [INFO] Apache Atlas Notification
> [INFO] Apache Atlas Repository
> [INFO] Apache Atlas Web Application
> [INFO] Apache Atlas Documentation
> [INFO] Apache Atlas Hive Bridge
> [INFO]
>
> [INFO]
>
> [INFO] Building apache-atlas 0.6-incubating-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ apache-atlas ---
> [INFO] Deleting /Users/MYSELF/Projects/External/incubator-atlas/target
> [INFO] Deleting /Users/MYSELF/Projects/External/incubator-atlas (includes =
> [**/*.pyc], excludes = [])
> [INFO]
> [INFO] --- buildnumber-maven-plugin:1.0:create (default) @ apache-atlas ---
> [INFO] Checking for local modifications: skipped.
> [INFO] Updating project files from SCM: skipped.
> [WARNING] Cannot get the revision information from the scm repository,
> proceeding with revision of release :
> No such provider: 'https'.
> [INFO] Storing buildNumber: release at timestamp: 1440071695692
> [WARNING] Cannot get the branch information from the scm repository,
> proceeding with UNKNOWN_BRANCH :
> No such provider: 'https'.
> [INFO] Storing buildScmBranch: UNKNOWN_BRANCH
> [INFO]
> [INFO] --- maven-remote-resources-plugin:1.4:process (default) @ apache-atlas
> ---
> [INFO]
> [INFO] --- scala-maven-plugin:3.2.0:compile (scala-compile-first) @
> apache-atlas ---
> [INFO] No sources to compile
> [INFO]
> [INFO] --- scala-maven-plugin:3.2.0:testCompile (scala-test-compile-first) @
> apache-atlas ---
> [INFO] No sources to compile
> [INFO]
> [INFO] --- exec-maven-plugin:1.2.1:exec (python-test) @ apache-atlas ---
> test_jar_java_lookups_fail (TestMetadata.TestMetadata) ... ok
> test_jar_java_lookups_succeed_from_path (TestMetadata.TestMetadata) ... ok
> test_main (TestMetadata.TestMetadata) ... Apache Atlas Server started!!!
> ok
> --
> Ran 3 tests in 0.003s
> OK
> [INFO]
> [INFO] --- maven-site-plugin:3.2:attach-descriptor (attach-descriptor) @
> apache-atlas ---
> [INFO]
> [INFO] --- maven-assembly-plugin:2.2.1:single (default) @ apache-atlas ---
> [INFO] Reading assembly descriptor: src/main/assemblies/standalone-package.xml
> [INFO] Reading assembly descriptor: src/main/assemblies/src-package.xml
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] apache-atlas ... FAILURE [ 1.773
> s]
> [INFO] Apache Atlas Typesystem SKIPPED
> [INFO] Apache Atlas Client SKIPPED
> [INFO] Apache Atlas Notification .. SKIPPED
> [INFO] Apache Atlas Repository SKIPPED
> [INFO] Apache Atlas Web Application ... SKIPPED
> [INFO] Apache Atlas Documentation . SKIPPED
> [INFO] Apache Atlas Hive Bridge ... SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
[jira] [Commented] (ATLAS-117) Build fails on the latest commit 48343db999...
[
https://issues.apache.org/jira/browse/ATLAS-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14716811#comment-14716811
]
David Kaspar commented on ATLAS-117:
I confirm that the ATLAS-117.patch fixed the issue.
Build fails on the latest commit 48343db999...
--
Key: ATLAS-117
URL: https://issues.apache.org/jira/browse/ATLAS-117
Project: Atlas
Issue Type: Bug
Reporter: David Kaspar
Assignee: Tom Beerbower
Attachments: ATLAS-117.patch
Build fails when building the latest commit
48343db999b495458409644c8b9d2fd0bd9fa99d:
{code}
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model
for org.apache.atlas:atlas-webapp:war:0.6-incubating-SNAPSHOT
[WARNING] 'build.plugins.plugin.version' for
org.codehaus.mojo:keytool-maven-plugin is missing. @
org.apache.atlas:atlas-webapp:[unknown-version],
/Users/MYSELF/Projects/External/incubator-atlas/webapp/pom.xml, line 309,
column 21
[WARNING]
[WARNING] It is highly recommended to fix these problems because they
threaten the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support
building such malformed projects.
[WARNING]
[INFO]
[INFO] Reactor Build Order:
[INFO]
[INFO] apache-atlas
[INFO] Apache Atlas Typesystem
[INFO] Apache Atlas Client
[INFO] Apache Atlas Notification
[INFO] Apache Atlas Repository
[INFO] Apache Atlas Web Application
[INFO] Apache Atlas Documentation
[INFO] Apache Atlas Hive Bridge
[INFO]
[INFO]
[INFO] Building apache-atlas 0.6-incubating-SNAPSHOT
[INFO]
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ apache-atlas ---
[INFO] Deleting /Users/MYSELF/Projects/External/incubator-atlas/target
[INFO] Deleting /Users/MYSELF/Projects/External/incubator-atlas (includes =
[**/*.pyc], excludes = [])
[INFO]
[INFO] --- buildnumber-maven-plugin:1.0:create (default) @ apache-atlas ---
[INFO] Checking for local modifications: skipped.
[INFO] Updating project files from SCM: skipped.
[WARNING] Cannot get the revision information from the scm repository,
proceeding with revision of release :
No such provider: 'https'.
[INFO] Storing buildNumber: release at timestamp: 1440071695692
[WARNING] Cannot get the branch information from the scm repository,
proceeding with UNKNOWN_BRANCH :
No such provider: 'https'.
[INFO] Storing buildScmBranch: UNKNOWN_BRANCH
[INFO]
[INFO] --- maven-remote-resources-plugin:1.4:process (default) @ apache-atlas
---
[INFO]
[INFO] --- scala-maven-plugin:3.2.0:compile (scala-compile-first) @
apache-atlas ---
[INFO] No sources to compile
[INFO]
[INFO] --- scala-maven-plugin:3.2.0:testCompile (scala-test-compile-first) @
apache-atlas ---
[INFO] No sources to compile
[INFO]
[INFO] --- exec-maven-plugin:1.2.1:exec (python-test) @ apache-atlas ---
test_jar_java_lookups_fail (TestMetadata.TestMetadata) ... ok
test_jar_java_lookups_succeed_from_path (TestMetadata.TestMetadata) ... ok
test_main (TestMetadata.TestMetadata) ... Apache Atlas Server started!!!
ok
--
Ran 3 tests in 0.003s
OK
[INFO]
[INFO] --- maven-site-plugin:3.2:attach-descriptor (attach-descriptor) @
apache-atlas ---
[INFO]
[INFO] --- maven-assembly-plugin:2.2.1:single (default) @ apache-atlas ---
[INFO] Reading assembly descriptor: src/main/assemblies/standalone-package.xml
[INFO] Reading assembly descriptor: src/main/assemblies/src-package.xml
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] apache-atlas ... FAILURE [ 1.773
s]
[INFO] Apache Atlas Typesystem SKIPPED
[INFO] Apache Atlas Client SKIPPED
[INFO] Apache Atlas Notification .. SKIPPED
[INFO] Apache Atlas Repository SKIPPED
[INFO] Apache Atlas Web Application ... SKIPPED
[INFO] Apache Atlas Documentation . SKIPPED
[INFO] Apache Atlas Hive Bridge ... SKIPPED
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 2.801 s
[INFO] Finished at:
[jira] [Updated] (ATLAS-61) Inconsistent metadata content
[
https://issues.apache.org/jira/browse/ATLAS-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Kaspar updated ATLAS-61:
--
Attachment: application.log
I am attaching my application.log file with the log of the first two runs of
Atlas. The Hive related entities are listed only as they are restored from
the DB during the second run of Atlas.
Inconsistent metadata content
-
Key: ATLAS-61
URL: https://issues.apache.org/jira/browse/ATLAS-61
Project: Atlas
Issue Type: Bug
Reporter: David Kaspar
Attachments: application.log
Steps to reproduce:
build Atlas binaries and install it to a fresh directory (aka in untar the
binary artifact to new/empty directory) and run:
{code}
apache-atlas-0.6-incubating-SNAPSHOT/bin/atlas_start.sh
sleep 30
curl http://127.0.0.1:21000/api/atlas/types
# it prints:
{results:[Process,Infrastructure,DataSet],count:3,requestId:1244107514@qtp-1475081618-0
- 4ced54d8-a726-4384-8e97-3f3d5535d307}
apache-atlas-0.6-incubating-SNAPSHOT/bin/atlas_stop.sh
apache-atlas-0.6-incubating-SNAPSHOT/bin/atlas_start.sh
sleep 30
curl http://127.0.0.1:21000/api/atlas/types
# it prints:
{results:[hive_function_type,hive_index,Process,hive_column,hive_serde,hive_function,hive_resourceuri,hive_table,hive_storagedesc,hive_principal_type,hive_process,hive_resource_type,hive_type,hive_object_type,Infrastructure,hive_order,hive_role,DataSet,hive_partition,hive_db],count:20,requestId:500065027@qtp-1586292005-0
- 22906b64-8c9e-4f1d-97b6-6eadf2a71bbf}
{code}
Note that I have not been load any types - I just started, stopped and then
started the atlas again and it printed inconsistent types.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (ATLAS-63) directory-properties in application.properties should be relative to Atlas home
[
https://issues.apache.org/jira/browse/ATLAS-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Kaspar closed ATLAS-63.
-
directory-properties in application.properties should be relative to Atlas
home
---
Key: ATLAS-63
URL: https://issues.apache.org/jira/browse/ATLAS-63
Project: Atlas
Issue Type: Bug
Reporter: David Kaspar
Priority: Minor
By default $ATLAS_HOME/conf/application.properties file contains:
{code}
atlas.graph.storage.directory=data/berkley
atlas.graph.index.search.directory=data/es
{code}
When Atlas software is run, it created the 'data' folder in
$ATLAS_HOME/server/webapp/atlas directory while I would expect it to be in
$ATLAS_HOME/data directory.
Setting the priority to Minor since the issue might be worked around by
specifying absolute path.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (ATLAS-60) Cannot load hive-data-model.json
David Kaspar created ATLAS-60:
-
Summary: Cannot load hive-data-model.json
Key: ATLAS-60
URL: https://issues.apache.org/jira/browse/ATLAS-60
Project: Atlas
Issue Type: Bug
Reporter: David Kaspar
When trying to load new types from
incubator-atlas/src/main/examples/hive-data-model.json to Atlas, then it fails
with the following exception:
{code}
$ curl -X POST -H Content-Type: application/json -d
@incubator-atlas/src/main/examples/hive-data-model.json
http://localhost:21000/api/atlas/types
{error:A multiplicty of more than one requires a collection type for
attribute 'resourceUris',stackTrace:org.apache.atlas.AtlasException: A
multiplicty of more than one requires a collection type for attribute
'resourceUris'\n\tat
org.apache.atlas.typesystem.types.TypeSystem$TransientTypeSystem.constructAttributeInfo(TypeSystem.java:453)\n\tat
org.apache.atlas.typesystem.types.TypeSystem$TransientTypeSystem.constructHierarchicalType(TypeSystem.java:476)\n\tat
org.apache.atlas.typesystem.types.TypeSystem$TransientTypeSystem.step3(TypeSystem.java:520)\n\tat
org.apache.atlas.typesystem.types.TypeSystem$TransientTypeSystem.defineTypes(TypeSystem.java:547)\n\tat
org.apache.atlas.typesystem.types.TypeSystem.defineTypes(TypeSystem.java:249)\n\tat
org.apache.atlas.typesystem.types.TypeSystem.defineTypes(TypeSystem.java:241)\n\tat
org.apache.atlas.services.DefaultMetadataService.createType(DefaultMetadataService.java:165)\n\tat
org.apache.atlas.web.resources.TypesResource.submit(TypesResource.java:84)\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:288)\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:1469)\n\tat
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1400)\n\tat
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1349)\n\tat
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1339)\n\tat
com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:416)\n\tat
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:537)\n\tat
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:699)\n\tat
javax.servlet.http.HttpServlet.service(HttpServlet.java:820)\n\tat
com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:287)\n\tat
com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:277)\n\tat
com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:182)\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:67)\n\tat
com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)\n\tat
com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:119)\n\tat
com.google.inject.servlet.GuiceFilter$1.call(GuiceFilter.java:133)\n\tat
com.google.inject.servlet.GuiceFilter$1.call(GuiceFilter.java:130)\n\tat
com.google.inject.servlet.GuiceFilter$Context.call(GuiceFilter.java:203)\n\tat
com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:130)\n\tat
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)\n\tat
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:399)\n\tat
org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)\n\tat
org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)\n\tat
