[jira] [Commented] (ATLAS-88) Atlas should provide tar ball for released version
[ https://issues.apache.org/jira/browse/ATLAS-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14965243#comment-14965243 ] Herman Yu commented on ATLAS-88: I see the latest built 102 was successful. however, I still don't see a link to the tar ball. would you please let us know how to download the tar ball? thanks. > Atlas should provide tar ball for released version > -- > > Key: ATLAS-88 > URL: https://issues.apache.org/jira/browse/ATLAS-88 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.5-incubating >Reporter: Chen He >Assignee: Venkatesh Seetharam > > I followed instruction and find there is only source.tar.gz file available in > the download page. It should provide apache-atlas-0.5-tar.gz tar ball. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-242) lineage hive table schema REST API does not accept any tableName value
David Kaspar created ATLAS-242:
--
Summary: 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)
