[jira] [Resolved] (ATLAS-3581) HBase hook converts qualifiedName to lowercase for namespace, table, column-family and column
[ https://issues.apache.org/jira/browse/ATLAS-3581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Mani resolved ATLAS-3581. Resolution: Fixed > HBase hook converts qualifiedName to lowercase for namespace, table, > column-family and column > - > > Key: ATLAS-3581 > URL: https://issues.apache.org/jira/browse/ATLAS-3581 > Project: Atlas > Issue Type: Bug > Components: atlas-intg >Reporter: Ramesh Mani >Assignee: Ramesh Mani >Priority: Major > > HBase hook converts qualifiedName to lowercase for namespace, table, > column-family and column -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3581) HBase hook converts qualifiedName to lowercase for namespace, table, column-family and column
Ramesh Mani created ATLAS-3581: -- Summary: HBase hook converts qualifiedName to lowercase for namespace, table, column-family and column Key: ATLAS-3581 URL: https://issues.apache.org/jira/browse/ATLAS-3581 Project: Atlas Issue Type: Bug Components: atlas-intg Reporter: Ramesh Mani HBase hook converts qualifiedName to lowercase for namespace, table, column-family and column -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-3581) HBase hook converts qualifiedName to lowercase for namespace, table, column-family and column
[ https://issues.apache.org/jira/browse/ATLAS-3581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Mani reassigned ATLAS-3581: -- Assignee: Ramesh Mani > HBase hook converts qualifiedName to lowercase for namespace, table, > column-family and column > - > > Key: ATLAS-3581 > URL: https://issues.apache.org/jira/browse/ATLAS-3581 > Project: Atlas > Issue Type: Bug > Components: atlas-intg >Reporter: Ramesh Mani >Assignee: Ramesh Mani >Priority: Major > > HBase hook converts qualifiedName to lowercase for namespace, table, > column-family and column -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3387) Consider X-FORWARDED-FOR header for getting end user IP address when connected with proxy
[
https://issues.apache.org/jira/browse/ATLAS-3387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16915517#comment-16915517
]
Ramesh Mani commented on ATLAS-3387:
[~nikhilbonte]
X-FORWARDED-FOR is a list of ips, that contains all the hops the call made,
please consider doing this.
String ret = httpServletRequest.getHeader("X-FORWARDED-FOR");
if (StringUtils.isNotBlank(ret)) {
String[] forwardedAddresses = ret(",");
if (ipAddress.length > 0) {
ret = forwardedAddresses[0].trim();
}
}
if (ret == null) {
try {
InetAddress inetAddr =
InetAddress.getByName(httpServletRequest.getRemoteAddr());
ret = inetAddr.getHostAddress();
} catch (UnknownHostException ex) {
LOG.error("Failed to retrieve client IP address", ex);
}
return ret;
> Consider X-FORWARDED-FOR header for getting end user IP address when
> connected with proxy
> -
>
> Key: ATLAS-3387
> URL: https://issues.apache.org/jira/browse/ATLAS-3387
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Reporter: Nikhil Bonte
>Assignee: Nikhil Bonte
>Priority: Major
> Attachments:
> ATLAS-3387-Consider-X-FORWARDED-FOR-header-for-getti.patch
>
>
> Consider X-FORWARDED-FOR header for getting end user IP address when
> connected with proxy
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Resolved] (ATLAS-3111) Ranger Hive Plugin enhancement for KILL query and Replication commands authorization
[ https://issues.apache.org/jira/browse/ATLAS-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Mani resolved ATLAS-3111. Resolution: Invalid Wrongly assigned project. > Ranger Hive Plugin enhancement for KILL query and Replication commands > authorization > > > Key: ATLAS-3111 > URL: https://issues.apache.org/jira/browse/ATLAS-3111 > Project: Atlas > Issue Type: Bug >Reporter: Ramesh Mani >Priority: Major > > 1) Hive KILL Query > With the HIVE-17483 JIRA, Hive has introduced a way to kill query and in > hive its a privileged action for Hive Admin Role. In order for the Ranger > Hive Authorizer to support authorization, we need to enhance the ranger hive > authorizer. Current Hive implementation is to Kill Query in a HiveService > which can be LLAP / HIVESERVER2 , later these HIVE SERVICEs can be grouped > into NAME SPACEs and kill query can be run against them. When > HiveServer2/LLAP Ranger Plugin sends the request to Ranger for Authorization, > it will be sending the HIVE SERVICE in the context with the COMMAND that is > executed. > With all the details proposal is to have > 1) In Ranger Hive Service Definition, we will have a new Resource "Hive > Service" to authorize. > 2) In Ranger Hive Permission Model, we will have a new Permission "Service > Admin" to group Kill Query operation. > "Service Admin" permission will enable hive ranger plugin to isolate various > admin operations in this case "Kill Query" and in future if hive introduces > other operations which are done at "HIVE SERVICE level" , group them under > this and authorize. > "Service Admin" won't be able to do DATABASE / TABLE / COLUMN operations as > this will all be taken care by the existing DATABASE/TABLE/COLUMN level > permission model. > 2) Replication Command > Hive has enhanced it authorization for Replication Task > https://issues.apache.org/jira/browse/HIVE-17005. The proposal from Ranger > side is to have "Repl Admin" permission in RangerHive privilege model and > command REPL DUMP and REPL LOAD should be authorized for the users with > "Admin" privilege on Database / Table level. > For REPL STATUS command, the user should have SELECT privilege on the > Database/ Table Level. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-3111) Ranger Hive Plugin enhancement for KILL query and Replication commands authorization
Ramesh Mani created ATLAS-3111: -- Summary: Ranger Hive Plugin enhancement for KILL query and Replication commands authorization Key: ATLAS-3111 URL: https://issues.apache.org/jira/browse/ATLAS-3111 Project: Atlas Issue Type: Bug Reporter: Ramesh Mani 1) Hive KILL Query With the HIVE-17483 JIRA, Hive has introduced a way to kill query and in hive its a privileged action for Hive Admin Role. In order for the Ranger Hive Authorizer to support authorization, we need to enhance the ranger hive authorizer. Current Hive implementation is to Kill Query in a HiveService which can be LLAP / HIVESERVER2 , later these HIVE SERVICEs can be grouped into NAME SPACEs and kill query can be run against them. When HiveServer2/LLAP Ranger Plugin sends the request to Ranger for Authorization, it will be sending the HIVE SERVICE in the context with the COMMAND that is executed. With all the details proposal is to have 1) In Ranger Hive Service Definition, we will have a new Resource "Hive Service" to authorize. 2) In Ranger Hive Permission Model, we will have a new Permission "Service Admin" to group Kill Query operation. "Service Admin" permission will enable hive ranger plugin to isolate various admin operations in this case "Kill Query" and in future if hive introduces other operations which are done at "HIVE SERVICE level" , group them under this and authorize. "Service Admin" won't be able to do DATABASE / TABLE / COLUMN operations as this will all be taken care by the existing DATABASE/TABLE/COLUMN level permission model. 2) Replication Command Hive has enhanced it authorization for Replication Task https://issues.apache.org/jira/browse/HIVE-17005. The proposal from Ranger side is to have "Repl Admin" permission in RangerHive privilege model and command REPL DUMP and REPL LOAD should be authorized for the users with "Admin" privilege on Database / Table level. For REPL STATUS command, the user should have SELECT privilege on the Database/ Table Level. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3092) Atlas Plugin ClassLoader Doesn't Restore Thread ClassLoader
[ https://issues.apache.org/jira/browse/ATLAS-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Mani updated ATLAS-3092: --- Attachment: 0001-ATLAS-3092-Atlas-Plugin-ClassLoader-Doesn-t-Restore-.patch > Atlas Plugin ClassLoader Doesn't Restore Thread ClassLoader > --- > > Key: ATLAS-3092 > URL: https://issues.apache.org/jira/browse/ATLAS-3092 > Project: Atlas > Issue Type: Bug >Reporter: Shawn Weeks >Assignee: Ramesh Mani >Priority: Minor > Attachments: > 0001-ATLAS-3092-Atlas-Plugin-ClassLoader-Doesn-t-Restore-.patch > > Time Spent: 40m > Remaining Estimate: 0h > > Currently when the AtlasPluginClassLoader is deactivated it sets the current > threads class loader to class loader that was active when the class was > instantiated. In applications like Hive where a single thread may be shared > among multiple sessions each with its own class loader this is breaking class > loading for UDFs. The deactivate method should set the current threads class > loader back to the class loader that was set when activate was called. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3092) Atlas Plugin ClassLoader Doesn't Restore Thread ClassLoader
[ https://issues.apache.org/jira/browse/ATLAS-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Mani updated ATLAS-3092: --- Attachment: (was: 0001-ATLAS-3092-Atlas-Plugin-ClassLoader-Doesn-t-Restore-.patch) > Atlas Plugin ClassLoader Doesn't Restore Thread ClassLoader > --- > > Key: ATLAS-3092 > URL: https://issues.apache.org/jira/browse/ATLAS-3092 > Project: Atlas > Issue Type: Bug >Reporter: Shawn Weeks >Assignee: Ramesh Mani >Priority: Minor > Attachments: > 0001-ATLAS-3092-Atlas-Plugin-ClassLoader-Doesn-t-Restore-.patch > > Time Spent: 40m > Remaining Estimate: 0h > > Currently when the AtlasPluginClassLoader is deactivated it sets the current > threads class loader to class loader that was active when the class was > instantiated. In applications like Hive where a single thread may be shared > among multiple sessions each with its own class loader this is breaking class > loading for UDFs. The deactivate method should set the current threads class > loader back to the class loader that was set when activate was called. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-3092) Atlas Plugin ClassLoader Doesn't Restore Thread ClassLoader
[ https://issues.apache.org/jira/browse/ATLAS-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16803462#comment-16803462 ] Ramesh Mani commented on ATLAS-3092: [~Absolutesantaja] Attached patch for this. Similar approach that is done in ranger side. > Atlas Plugin ClassLoader Doesn't Restore Thread ClassLoader > --- > > Key: ATLAS-3092 > URL: https://issues.apache.org/jira/browse/ATLAS-3092 > Project: Atlas > Issue Type: Bug >Reporter: Shawn Weeks >Priority: Minor > Attachments: > 0001-ATLAS-3092-Atlas-Plugin-ClassLoader-Doesn-t-Restore-.patch, > ALAS-3092-AtlasPluginClassLoader-for-UDF.patch > > Time Spent: 40m > Remaining Estimate: 0h > > Currently when the AtlasPluginClassLoader is deactivated it sets the current > threads class loader to class loader that was active when the class was > instantiated. In applications like Hive where a single thread may be shared > among multiple sessions each with its own class loader this is breaking class > loading for UDFs. The deactivate method should set the current threads class > loader back to the class loader that was set when activate was called. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (ATLAS-3092) Atlas Plugin ClassLoader Doesn't Restore Thread ClassLoader
[ https://issues.apache.org/jira/browse/ATLAS-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Mani reassigned ATLAS-3092: -- Assignee: Ramesh Mani > Atlas Plugin ClassLoader Doesn't Restore Thread ClassLoader > --- > > Key: ATLAS-3092 > URL: https://issues.apache.org/jira/browse/ATLAS-3092 > Project: Atlas > Issue Type: Bug >Reporter: Shawn Weeks >Assignee: Ramesh Mani >Priority: Minor > Attachments: > 0001-ATLAS-3092-Atlas-Plugin-ClassLoader-Doesn-t-Restore-.patch, > ALAS-3092-AtlasPluginClassLoader-for-UDF.patch > > Time Spent: 40m > Remaining Estimate: 0h > > Currently when the AtlasPluginClassLoader is deactivated it sets the current > threads class loader to class loader that was active when the class was > instantiated. In applications like Hive where a single thread may be shared > among multiple sessions each with its own class loader this is breaking class > loading for UDFs. The deactivate method should set the current threads class > loader back to the class loader that was set when activate was called. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3092) Atlas Plugin ClassLoader Doesn't Restore Thread ClassLoader
[ https://issues.apache.org/jira/browse/ATLAS-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Mani updated ATLAS-3092: --- Attachment: 0001-ATLAS-3092-Atlas-Plugin-ClassLoader-Doesn-t-Restore-.patch > Atlas Plugin ClassLoader Doesn't Restore Thread ClassLoader > --- > > Key: ATLAS-3092 > URL: https://issues.apache.org/jira/browse/ATLAS-3092 > Project: Atlas > Issue Type: Bug >Reporter: Shawn Weeks >Priority: Minor > Attachments: > 0001-ATLAS-3092-Atlas-Plugin-ClassLoader-Doesn-t-Restore-.patch, > ALAS-3092-AtlasPluginClassLoader-for-UDF.patch > > Time Spent: 40m > Remaining Estimate: 0h > > Currently when the AtlasPluginClassLoader is deactivated it sets the current > threads class loader to class loader that was active when the class was > instantiated. In applications like Hive where a single thread may be shared > among multiple sessions each with its own class loader this is breaking class > loading for UDFs. The deactivate method should set the current threads class > loader back to the class loader that was set when activate was called. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (ATLAS-2983) Fixes and clean up for Atlas Kafka bridge utility
[ https://issues.apache.org/jira/browse/ATLAS-2983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16704120#comment-16704120 ] Ramesh Mani edited comment on ATLAS-2983 at 11/30/18 1:28 AM: -- [~umesh.padashetty] Thanks for the patch commit link [https://github.com/apache/atlas/commit/18a4984a4f6d28cd03c0e2fed194b1f129a5a9ec] 1.0 https://github.com/apache/atlas/commit/73185dc51866f901aae23076ba8340fadbc1f2bb was (Author: rmani): [~umesh.padashetty] Thanks for the patch commit link [https://github.com/apache/atlas/commit/18a4984a4f6d28cd03c0e2fed194b1f129a5a9ec] > Fixes and clean up for Atlas Kafka bridge utility > - > > Key: ATLAS-2983 > URL: https://issues.apache.org/jira/browse/ATLAS-2983 > Project: Atlas > Issue Type: Bug > Components: atlas-core, atlas-webui >Affects Versions: 1.0.0, 1.1.0 >Reporter: Umesh Padashetty >Priority: Major > Attachments: ATLAS-2983.patch > > > # Currently, import-kafka.sh script allows selective kafka topic import by > providing -t or --topic option, but the script only checks for the topics > which start with the topic name provided and does not support regular > expression based selective import. With the fix provided, regex patterns can > be used along with -t as well as -f (file based import) option > # When a bad import-kafka command is being fired, following usage is being > printed on the console. Here, option should be -t instead of -n. Have fixed > this minor issue, along with some more text changes > ** import-kafka.sh [*-n* OR --topic ] > # Since we now have support for kakfa bridge and hbase hook/bridge, option > for creating entities for the following in Atlas UI could be removed > ## hbase_table > ## hbase_column > ## hbase_column_family > ## kafka_topic > ## hbase_namespace -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (ATLAS-2983) Fixes and clean up for Atlas Kafka bridge utility
[ https://issues.apache.org/jira/browse/ATLAS-2983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16704120#comment-16704120 ] Ramesh Mani edited comment on ATLAS-2983 at 11/30/18 1:26 AM: -- [~umesh.padashetty] Thanks for the patch commit link [https://github.com/apache/atlas/commit/18a4984a4f6d28cd03c0e2fed194b1f129a5a9ec] was (Author: rmani): commit link https://github.com/apache/atlas/commit/18a4984a4f6d28cd03c0e2fed194b1f129a5a9ec > Fixes and clean up for Atlas Kafka bridge utility > - > > Key: ATLAS-2983 > URL: https://issues.apache.org/jira/browse/ATLAS-2983 > Project: Atlas > Issue Type: Bug > Components: atlas-core, atlas-webui >Affects Versions: 1.0.0, 1.1.0 >Reporter: Umesh Padashetty >Priority: Major > Attachments: ATLAS-2983.patch > > > # Currently, import-kafka.sh script allows selective kafka topic import by > providing -t or --topic option, but the script only checks for the topics > which start with the topic name provided and does not support regular > expression based selective import. With the fix provided, regex patterns can > be used along with -t as well as -f (file based import) option > # When a bad import-kafka command is being fired, following usage is being > printed on the console. Here, option should be -t instead of -n. Have fixed > this minor issue, along with some more text changes > ** import-kafka.sh [*-n* OR --topic ] > # Since we now have support for kakfa bridge and hbase hook/bridge, option > for creating entities for the following in Atlas UI could be removed > ## hbase_table > ## hbase_column > ## hbase_column_family > ## kafka_topic > ## hbase_namespace -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2983) Fixes and clean up for Atlas Kafka bridge utility
[ https://issues.apache.org/jira/browse/ATLAS-2983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16704120#comment-16704120 ] Ramesh Mani commented on ATLAS-2983: commit link https://github.com/apache/atlas/commit/18a4984a4f6d28cd03c0e2fed194b1f129a5a9ec > Fixes and clean up for Atlas Kafka bridge utility > - > > Key: ATLAS-2983 > URL: https://issues.apache.org/jira/browse/ATLAS-2983 > Project: Atlas > Issue Type: Bug > Components: atlas-core, atlas-webui >Affects Versions: 1.0.0, 1.1.0 >Reporter: Umesh Padashetty >Priority: Major > Attachments: ATLAS-2983.patch > > > # Currently, import-kafka.sh script allows selective kafka topic import by > providing -t or --topic option, but the script only checks for the topics > which start with the topic name provided and does not support regular > expression based selective import. With the fix provided, regex patterns can > be used along with -t as well as -f (file based import) option > # When a bad import-kafka command is being fired, following usage is being > printed on the console. Here, option should be -t instead of -n. Have fixed > this minor issue, along with some more text changes > ** import-kafka.sh [*-n* OR --topic ] > # Since we now have support for kakfa bridge and hbase hook/bridge, option > for creating entities for the following in Atlas UI could be removed > ## hbase_table > ## hbase_column > ## hbase_column_family > ## kafka_topic > ## hbase_namespace -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2983) Fixes and clean up for Atlas Kafka bridge utility
[ https://issues.apache.org/jira/browse/ATLAS-2983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16704105#comment-16704105 ] Ramesh Mani commented on ATLAS-2983: [~umesh.padashetty] changes looks good +1 for the patch > Fixes and clean up for Atlas Kafka bridge utility > - > > Key: ATLAS-2983 > URL: https://issues.apache.org/jira/browse/ATLAS-2983 > Project: Atlas > Issue Type: Bug > Components: atlas-core, atlas-webui >Affects Versions: 1.0.0, 1.1.0 >Reporter: Umesh Padashetty >Priority: Major > Attachments: ATLAS-2983.patch > > > # Currently, import-kafka.sh script allows selective kafka topic import by > providing -t or --topic option, but the script only checks for the topics > which start with the topic name provided and does not support regular > expression based selective import. With the fix provided, regex patterns can > be used along with -t as well as -f (file based import) option > # When a bad import-kafka command is being fired, following usage is being > printed on the console. Here, option should be -t instead of -n. Have fixed > this minor issue, along with some more text changes > ** import-kafka.sh [*-n* OR --topic ] > # Since we now have support for kakfa bridge and hbase hook/bridge, option > for creating entities for the following in Atlas UI could be removed > ## hbase_table > ## hbase_column > ## hbase_column_family > ## kafka_topic > ## hbase_namespace -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2921) Atlas hive-bridge import-hive.sh returns 0 in case of java error
[ https://issues.apache.org/jira/browse/ATLAS-2921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16652507#comment-16652507 ] Ramesh Mani commented on ATLAS-2921: [~lterjeki] I have merged your changes. You could close this Jira and review for it. Thanks for your contribution. > Atlas hive-bridge import-hive.sh returns 0 in case of java error > > > Key: ATLAS-2921 > URL: https://issues.apache.org/jira/browse/ATLAS-2921 > Project: Atlas > Issue Type: Bug >Affects Versions: 1.0.0 >Reporter: László Dénes Terjéki >Priority: Minor > Attachments: > 0001-ATLAS-2921-Update-import-scripts-exit-status-in-case.patch, > ATLAS-2921.000.patch, ATLAS-2921.001.patch > > > When the import-hive.sh runs the java which has an error than the status code > is saved but only used for an echo message. Later the script exits with 0 > code instead of the error code. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (ATLAS-2921) Atlas hive-bridge import-hive.sh returns 0 in case of java error
[ https://issues.apache.org/jira/browse/ATLAS-2921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16652384#comment-16652384 ] Ramesh Mani edited comment on ATLAS-2921 at 10/16/18 8:19 PM: -- [~lterjeki] One last correction. Could you please create the patch using "git format-patch -n HEAD^ " and attach it. That would help me to signoff with your id in the commit. Thanks, Ramesh was (Author: rmani): [~lterjeki] One last correction. Could you please create the patch using git format-patch -n HEAD^ and attach it. That would help me to signoff with your id in the commit. Thanks, Ramesh > Atlas hive-bridge import-hive.sh returns 0 in case of java error > > > Key: ATLAS-2921 > URL: https://issues.apache.org/jira/browse/ATLAS-2921 > Project: Atlas > Issue Type: Bug >Affects Versions: 1.0.0 >Reporter: László Dénes Terjéki >Priority: Minor > Attachments: ATLAS-2921.000.patch, ATLAS-2921.001.patch > > > When the import-hive.sh runs the java which has an error than the status code > is saved but only used for an echo message. Later the script exits with 0 > code instead of the error code. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2921) Atlas hive-bridge import-hive.sh returns 0 in case of java error
[ https://issues.apache.org/jira/browse/ATLAS-2921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16652384#comment-16652384 ] Ramesh Mani commented on ATLAS-2921: [~lterjeki] One last correction. Could you please create the patch using git format-patch -n HEAD^ and attach it. That would help me to signoff with your id in the commit. Thanks, Ramesh > Atlas hive-bridge import-hive.sh returns 0 in case of java error > > > Key: ATLAS-2921 > URL: https://issues.apache.org/jira/browse/ATLAS-2921 > Project: Atlas > Issue Type: Bug >Affects Versions: 1.0.0 >Reporter: László Dénes Terjéki >Priority: Minor > Attachments: ATLAS-2921.000.patch, ATLAS-2921.001.patch > > > When the import-hive.sh runs the java which has an error than the status code > is saved but only used for an echo message. Later the script exits with 0 > code instead of the error code. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (ATLAS-2921) Atlas hive-bridge import-hive.sh returns 0 in case of java error
[ https://issues.apache.org/jira/browse/ATLAS-2921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16650963#comment-16650963 ] Ramesh Mani edited comment on ATLAS-2921 at 10/16/18 6:06 PM: -- [~lterjeki] Thanks for the patch. I see that we can update it for other bridge components scripts as well. In this way it will be uniform across. Could you please update the patch for them as well. Thank you. [https://github.com/apache/atlas/blob/master/addons/hbase-bridge/src/bin/import-hbase.sh] [https://github.com/apache/atlas/blob/master/addons/kafka-bridge/src/bin/import-kafka.sh] was (Author: rmani): [~lterjeki] Thanks for the patch. I see that we can update it for other bride components scripts as well. In this way it will be uniform across. Could you please update the patch for them as well. Thank you. [https://github.com/apache/atlas/blob/master/addons/hbase-bridge/src/bin/import-hbase.sh] [https://github.com/apache/atlas/blob/master/addons/kafka-bridge/src/bin/import-kafka.sh] > Atlas hive-bridge import-hive.sh returns 0 in case of java error > > > Key: ATLAS-2921 > URL: https://issues.apache.org/jira/browse/ATLAS-2921 > Project: Atlas > Issue Type: Bug >Affects Versions: 1.0.0 >Reporter: László Dénes Terjéki >Priority: Minor > Attachments: ATLAS-2921.000.patch, ATLAS-2921.001.patch > > > When the import-hive.sh runs the java which has an error than the status code > is saved but only used for an echo message. Later the script exits with 0 > code instead of the error code. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2921) Atlas hive-bridge import-hive.sh returns 0 in case of java error
[ https://issues.apache.org/jira/browse/ATLAS-2921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16652168#comment-16652168 ] Ramesh Mani commented on ATLAS-2921: +1 for the patch. Thanks. > Atlas hive-bridge import-hive.sh returns 0 in case of java error > > > Key: ATLAS-2921 > URL: https://issues.apache.org/jira/browse/ATLAS-2921 > Project: Atlas > Issue Type: Bug >Affects Versions: 1.0.0 >Reporter: László Dénes Terjéki >Priority: Minor > Attachments: ATLAS-2921.000.patch, ATLAS-2921.001.patch > > > When the import-hive.sh runs the java which has an error than the status code > is saved but only used for an echo message. Later the script exits with 0 > code instead of the error code. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (ATLAS-2921) Atlas hive-bridge import-hive.sh returns 0 in case of java error
[ https://issues.apache.org/jira/browse/ATLAS-2921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16650963#comment-16650963 ] Ramesh Mani edited comment on ATLAS-2921 at 10/15/18 11:36 PM: --- [~lterjeki] Thanks for the patch. I see that we can update it for other bride components scripts as well. In this way it will be uniform across. Could you please update the patch for them as well. Thank you. [https://github.com/apache/atlas/blob/master/addons/hbase-bridge/src/bin/import-hbase.sh] [https://github.com/apache/atlas/blob/master/addons/kafka-bridge/src/bin/import-kafka.sh] was (Author: rmani): [László Terjéki|https://reviews.apache.org/users/terjekid/] Thanks for the patch. I see that we can update it for other bride components scripts as well. In this way it will be uniform across. Could you please update the patch for them as well. Thank you. [https://github.com/apache/atlas/blob/master/addons/hbase-bridge/src/bin/import-hbase.sh] [https://github.com/apache/atlas/blob/master/addons/kafka-bridge/src/bin/import-kafka.sh] > Atlas hive-bridge import-hive.sh returns 0 in case of java error > > > Key: ATLAS-2921 > URL: https://issues.apache.org/jira/browse/ATLAS-2921 > Project: Atlas > Issue Type: Bug >Affects Versions: 1.0.0 >Reporter: László Dénes Terjéki >Priority: Minor > Attachments: ATLAS-2921.000.patch > > > When the import-hive.sh runs the java which has an error than the status code > is saved but only used for an echo message. Later the script exits with 0 > code instead of the error code. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2921) Atlas hive-bridge import-hive.sh returns 0 in case of java error
[ https://issues.apache.org/jira/browse/ATLAS-2921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16650963#comment-16650963 ] Ramesh Mani commented on ATLAS-2921: [László Terjéki|https://reviews.apache.org/users/terjekid/] Thanks for the patch. I see that we can update it for other bride components scripts as well. In this way it will be uniform across. Could you please update the patch for them as well. Thank you. [https://github.com/apache/atlas/blob/master/addons/hbase-bridge/src/bin/import-hbase.sh] [https://github.com/apache/atlas/blob/master/addons/kafka-bridge/src/bin/import-kafka.sh] > Atlas hive-bridge import-hive.sh returns 0 in case of java error > > > Key: ATLAS-2921 > URL: https://issues.apache.org/jira/browse/ATLAS-2921 > Project: Atlas > Issue Type: Bug >Affects Versions: 1.0.0 >Reporter: László Dénes Terjéki >Priority: Minor > Attachments: ATLAS-2921.000.patch > > > When the import-hive.sh runs the java which has an error than the status code > is saved but only used for an echo message. Later the script exits with 0 > code instead of the error code. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2801) Create a separate tar file for atlas-server components excluding atlas hook related components
[ https://issues.apache.org/jira/browse/ATLAS-2801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Mani updated ATLAS-2801: --- Attachment: 0001-ATLAS-2801-Create-a-separate-tar-file-for-atlas-serv.patch > Create a separate tar file for atlas-server components excluding atlas hook > related components > -- > > Key: ATLAS-2801 > URL: https://issues.apache.org/jira/browse/ATLAS-2801 > Project: Atlas > Issue Type: Bug > Components: atlas-intg >Affects Versions: trunk >Reporter: Ramesh Mani >Assignee: Ramesh Mani >Priority: Major > Attachments: > 0001-ATLAS-2801-Create-a-separate-tar-file-for-atlas-serv.patch > > > Create a separate tar file for atlas-server components excluding atlas hook > related components. Already we have separate tar files for each of the atlas > hooks and it's better to have a separate atlas-server tar file for better > management of the packages. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2801) Create a separate tar file for atlas-server components excluding atlas hook related components
Ramesh Mani created ATLAS-2801: -- Summary: Create a separate tar file for atlas-server components excluding atlas hook related components Key: ATLAS-2801 URL: https://issues.apache.org/jira/browse/ATLAS-2801 Project: Atlas Issue Type: Bug Components: atlas-intg Affects Versions: trunk Reporter: Ramesh Mani Create a separate tar file for atlas-server components excluding atlas hook related components. Already we have separate tar files for each of the atlas hooks and it's better to have a separate atlas-server tar file for better management of the packages. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (ATLAS-2801) Create a separate tar file for atlas-server components excluding atlas hook related components
[ https://issues.apache.org/jira/browse/ATLAS-2801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Mani reassigned ATLAS-2801: -- Assignee: Ramesh Mani > Create a separate tar file for atlas-server components excluding atlas hook > related components > -- > > Key: ATLAS-2801 > URL: https://issues.apache.org/jira/browse/ATLAS-2801 > Project: Atlas > Issue Type: Bug > Components: atlas-intg >Affects Versions: trunk >Reporter: Ramesh Mani >Assignee: Ramesh Mani >Priority: Major > > Create a separate tar file for atlas-server components excluding atlas hook > related components. Already we have separate tar files for each of the atlas > hooks and it's better to have a separate atlas-server tar file for better > management of the packages. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2785) Import Hive script should handle table name with database in -t option
[ https://issues.apache.org/jira/browse/ATLAS-2785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Mani updated ATLAS-2785: --- Fix Version/s: 1.1.0 > Import Hive script should handle table name with database in -t option > -- > > Key: ATLAS-2785 > URL: https://issues.apache.org/jira/browse/ATLAS-2785 > Project: Atlas > Issue Type: Bug >Affects Versions: trunk, 1.1.0 >Reporter: Ramesh Mani >Assignee: Ramesh Mani >Priority: Major > Fix For: trunk, 1.1.0 > > > Import Hive script should handle table name with database in -t > option.Currently if database name is there in table name for - t or > tablename option , it imports all the table. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2785) Import Hive script should handle table name with database in -t option
[ https://issues.apache.org/jira/browse/ATLAS-2785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Mani updated ATLAS-2785: --- Fix Version/s: trunk > Import Hive script should handle table name with database in -t option > -- > > Key: ATLAS-2785 > URL: https://issues.apache.org/jira/browse/ATLAS-2785 > Project: Atlas > Issue Type: Bug >Affects Versions: trunk, 1.1.0 >Reporter: Ramesh Mani >Assignee: Ramesh Mani >Priority: Major > Fix For: trunk, 1.1.0 > > > Import Hive script should handle table name with database in -t > option.Currently if database name is there in table name for - t or > tablename option , it imports all the table. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2785) Import Hive script should handle table name with database in -t option
[ https://issues.apache.org/jira/browse/ATLAS-2785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Mani updated ATLAS-2785: --- Affects Version/s: 1.1.0 > Import Hive script should handle table name with database in -t option > -- > > Key: ATLAS-2785 > URL: https://issues.apache.org/jira/browse/ATLAS-2785 > Project: Atlas > Issue Type: Bug >Affects Versions: trunk, 1.1.0 >Reporter: Ramesh Mani >Assignee: Ramesh Mani >Priority: Major > Fix For: trunk, 1.1.0 > > > Import Hive script should handle table name with database in -t > option.Currently if database name is there in table name for - t or > tablename option , it imports all the table. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2785) Import Hive script should handle table name with database in -t option
Ramesh Mani created ATLAS-2785: -- Summary: Import Hive script should handle table name with database in -t option Key: ATLAS-2785 URL: https://issues.apache.org/jira/browse/ATLAS-2785 Project: Atlas Issue Type: Bug Reporter: Ramesh Mani Assignee: Ramesh Mani Import Hive script should handle table name with database in -t option.Currently if database name is there in table name for - t or tablename option , it imports all the table. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2732) Handle kerberos security arguments in import-hbase.sh / import-hive.sh passed via command line
[ https://issues.apache.org/jira/browse/ATLAS-2732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Mani updated ATLAS-2732: --- Attachment: 0001-ATLAS-2732-Handle-kerberos-security-arguments-in-imp.patch > Handle kerberos security arguments in import-hbase.sh / import-hive.sh passed > via command line > -- > > Key: ATLAS-2732 > URL: https://issues.apache.org/jira/browse/ATLAS-2732 > Project: Atlas > Issue Type: Bug > Components: atlas-intg >Affects Versions: trunk >Reporter: Ramesh Mani >Assignee: Ramesh Mani >Priority: Major > Fix For: trunk > > Attachments: > 0001-ATLAS-2732-Handle-kerberos-security-arguments-in-imp.patch > > > Handle kerberos security arguments in import-hbase.sh / import-hive.sh . > Current when passed externally via command line import scripts fails with > exceptions. > e.g > ./import-hive.sh -d TEST_ATLAS_PATCH -t test > -Djava.security.krb5.conf=/etc/krb5.conf > -Djava.security.auth.login.config=/etc/atlas/conf/atlas_jaas.conf > ./import-hbase.sh -Djava.security.krb5.conf=/etc/krb5.conf > -Djava.security.auth.login.config=/etc/atlas/conf/atlas_jaas.conf -f > /tmp/hbase.txt -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2732) Handle kerberos security arguments in import-hbase.sh / import-hive.sh passed via command line
[ https://issues.apache.org/jira/browse/ATLAS-2732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Mani updated ATLAS-2732: --- Attachment: (was: 0001-ATLAS-2732-Handle-kerberos-security-arguments-in-imp.patch) > Handle kerberos security arguments in import-hbase.sh / import-hive.sh passed > via command line > -- > > Key: ATLAS-2732 > URL: https://issues.apache.org/jira/browse/ATLAS-2732 > Project: Atlas > Issue Type: Bug > Components: atlas-intg >Affects Versions: trunk >Reporter: Ramesh Mani >Assignee: Ramesh Mani >Priority: Major > Fix For: trunk > > > Handle kerberos security arguments in import-hbase.sh / import-hive.sh . > Current when passed externally via command line import scripts fails with > exceptions. > e.g > ./import-hive.sh -d TEST_ATLAS_PATCH -t test > -Djava.security.krb5.conf=/etc/krb5.conf > -Djava.security.auth.login.config=/etc/atlas/conf/atlas_jaas.conf > ./import-hbase.sh -Djava.security.krb5.conf=/etc/krb5.conf > -Djava.security.auth.login.config=/etc/atlas/conf/atlas_jaas.conf -f > /tmp/hbase.txt -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2732) Handle kerberos security arguments in import-hbase.sh / import-hive.sh passed via command line
[ https://issues.apache.org/jira/browse/ATLAS-2732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Mani updated ATLAS-2732: --- Attachment: 0001-ATLAS-2732-Handle-kerberos-security-arguments-in-imp.patch > Handle kerberos security arguments in import-hbase.sh / import-hive.sh passed > via command line > -- > > Key: ATLAS-2732 > URL: https://issues.apache.org/jira/browse/ATLAS-2732 > Project: Atlas > Issue Type: Bug > Components: atlas-intg >Affects Versions: trunk >Reporter: Ramesh Mani >Assignee: Ramesh Mani >Priority: Major > Fix For: trunk > > Attachments: > 0001-ATLAS-2732-Handle-kerberos-security-arguments-in-imp.patch > > > Handle kerberos security arguments in import-hbase.sh / import-hive.sh . > Current when passed externally via command line import scripts fails with > exceptions. > e.g > ./import-hive.sh -d TEST_ATLAS_PATCH -t test > -Djava.security.krb5.conf=/etc/krb5.conf > -Djava.security.auth.login.config=/etc/atlas/conf/atlas_jaas.conf > ./import-hbase.sh -Djava.security.krb5.conf=/etc/krb5.conf > -Djava.security.auth.login.config=/etc/atlas/conf/atlas_jaas.conf -f > /tmp/hbase.txt -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2732) Handle kerberos security arguments in import-hbase.sh / import-hive.sh passed via command line
Ramesh Mani created ATLAS-2732: -- Summary: Handle kerberos security arguments in import-hbase.sh / import-hive.sh passed via command line Key: ATLAS-2732 URL: https://issues.apache.org/jira/browse/ATLAS-2732 Project: Atlas Issue Type: Bug Components: atlas-intg Affects Versions: trunk Reporter: Ramesh Mani Assignee: Ramesh Mani Fix For: trunk Handle kerberos security arguments in import-hbase.sh / import-hive.sh . Current when passed externally via command line import scripts fails with exceptions. e.g ./import-hive.sh -d TEST_ATLAS_PATCH -t test -Djava.security.krb5.conf=/etc/krb5.conf -Djava.security.auth.login.config=/etc/atlas/conf/atlas_jaas.conf ./import-hbase.sh -Djava.security.krb5.conf=/etc/krb5.conf -Djava.security.auth.login.config=/etc/atlas/conf/atlas_jaas.conf -f /tmp/hbase.txt -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2650) HBase Atlas Hook : Handle NPE in HBase table import when getNameAsString() is null
[ https://issues.apache.org/jira/browse/ATLAS-2650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16478173#comment-16478173 ] Ramesh Mani commented on ATLAS-2650: This issue is not a valid bug, so resolving it > HBase Atlas Hook : Handle NPE in HBase table import when getNameAsString() is > null > -- > > Key: ATLAS-2650 > URL: https://issues.apache.org/jira/browse/ATLAS-2650 > Project: Atlas > Issue Type: Bug > Components: atlas-intg >Affects Versions: trunk >Reporter: Ramesh Mani >Priority: Critical > Fix For: trunk > > Attachments: > 0001-ATLAS-2650-HBase-Atlas-Hook-Handle-NPE-in-HBase-tabl.patch > > > HBase Atlas Hook : Handle NPE in HBase table import when getNameAsString() is > null > When HTableDescriptor.getNameAsString() to get the table name is null, we > need to get the table name with HTableDescriptor.getTableName().getName() -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2680) Import hbase script : Importing using regex failed to import certain regex
[ https://issues.apache.org/jira/browse/ATLAS-2680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16478164#comment-16478164 ] Ramesh Mani commented on ATLAS-2680: Review link for 0.8 branch patch https://reviews.apache.org/r/67163/ > Import hbase script : Importing using regex failed to import certain regex > -- > > Key: ATLAS-2680 > URL: https://issues.apache.org/jira/browse/ATLAS-2680 > Project: Atlas > Issue Type: Bug > Components: atlas-intg >Affects Versions: 1.0.0 >Reporter: Ramesh Mani >Assignee: Ramesh Mani >Priority: Major > Fix For: 1.0.0, 0.8.3 > > Attachments: > 0001-ATLAS-2680-Import-hbase-script-Importing-using-regex.patch, > 0001-ATLAS-2680-import-hbase-fails-to-match-namespaces.patch_08_branch > > > Import hbase script : Importing using regex failed to import certain regex > contain ^, $ etc. > e.g > ^nm.*" > nm.*a$ > ns_(.)* -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2680) Import hbase script : Importing using regex failed to import certain regex
[ https://issues.apache.org/jira/browse/ATLAS-2680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Mani updated ATLAS-2680: --- Attachment: 0001-ATLAS-2680-Import-hbase-script-Importing-using-regex.patch > Import hbase script : Importing using regex failed to import certain regex > -- > > Key: ATLAS-2680 > URL: https://issues.apache.org/jira/browse/ATLAS-2680 > Project: Atlas > Issue Type: Bug > Components: atlas-intg >Affects Versions: 1.0.0 >Reporter: Ramesh Mani >Assignee: Ramesh Mani >Priority: Major > Fix For: 1.0.0, 0.8.3 > > Attachments: > 0001-ATLAS-2680-Import-hbase-script-Importing-using-regex.patch, > 0001-ATLAS-2680-import-hbase-fails-to-match-namespaces.patch_08_branch > > > Import hbase script : Importing using regex failed to import certain regex > contain ^, $ etc. > e.g > ^nm.*" > nm.*a$ > ns_(.)* -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2680) Import hbase script : Importing using regex failed to import certain regex
[ https://issues.apache.org/jira/browse/ATLAS-2680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Mani updated ATLAS-2680: --- Attachment: 0001-ATLAS-2680-import-hbase-fails-to-match-namespaces.patch_08_branch > Import hbase script : Importing using regex failed to import certain regex > -- > > Key: ATLAS-2680 > URL: https://issues.apache.org/jira/browse/ATLAS-2680 > Project: Atlas > Issue Type: Bug > Components: atlas-intg >Affects Versions: 1.0.0 >Reporter: Ramesh Mani >Assignee: Ramesh Mani >Priority: Major > Fix For: 1.0.0, 0.8.3 > > Attachments: > 0001-ATLAS-2680-Import-hbase-script-Importing-using-regex.patch, > 0001-ATLAS-2680-import-hbase-fails-to-match-namespaces.patch_08_branch > > > Import hbase script : Importing using regex failed to import certain regex > contain ^, $ etc. > e.g > ^nm.*" > nm.*a$ > ns_(.)* -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-2650) HBase Atlas Hook : Handle NPE in HBase table import when getNameAsString() is null
[ https://issues.apache.org/jira/browse/ATLAS-2650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Mani resolved ATLAS-2650. Resolution: Not A Bug > HBase Atlas Hook : Handle NPE in HBase table import when getNameAsString() is > null > -- > > Key: ATLAS-2650 > URL: https://issues.apache.org/jira/browse/ATLAS-2650 > Project: Atlas > Issue Type: Bug > Components: atlas-intg >Affects Versions: trunk >Reporter: Ramesh Mani >Priority: Critical > Fix For: trunk > > Attachments: > 0001-ATLAS-2650-HBase-Atlas-Hook-Handle-NPE-in-HBase-tabl.patch > > > HBase Atlas Hook : Handle NPE in HBase table import when getNameAsString() is > null > When HTableDescriptor.getNameAsString() to get the table name is null, we > need to get the table name with HTableDescriptor.getTableName().getName() -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2680) Import hbase script : Importing using regex failed to import certain regex
[ https://issues.apache.org/jira/browse/ATLAS-2680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Mani updated ATLAS-2680: --- Fix Version/s: 0.8.3 > Import hbase script : Importing using regex failed to import certain regex > -- > > Key: ATLAS-2680 > URL: https://issues.apache.org/jira/browse/ATLAS-2680 > Project: Atlas > Issue Type: Bug > Components: atlas-intg >Affects Versions: 1.0.0 >Reporter: Ramesh Mani >Assignee: Ramesh Mani >Priority: Major > Fix For: 1.0.0, 0.8.3 > > > Import hbase script : Importing using regex failed to import certain regex > contain ^, $ etc. > e.g > ^nm.*" > nm.*a$ > ns_(.)* -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (ATLAS-2680) Import hbase script : Importing using regex failed to import certain regex
[ https://issues.apache.org/jira/browse/ATLAS-2680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Mani reassigned ATLAS-2680: -- Assignee: Ramesh Mani > Import hbase script : Importing using regex failed to import certain regex > -- > > Key: ATLAS-2680 > URL: https://issues.apache.org/jira/browse/ATLAS-2680 > Project: Atlas > Issue Type: Bug > Components: atlas-intg >Affects Versions: 1.0.0 >Reporter: Ramesh Mani >Assignee: Ramesh Mani >Priority: Major > Fix For: 1.0.0 > > > Import hbase script : Importing using regex failed to import certain regex > contain ^, $ etc. > e.g > ^nm.*" > nm.*a$ > ns_(.)* -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2680) Import hbase script : Importing using regex failed to import certain regex
Ramesh Mani created ATLAS-2680: -- Summary: Import hbase script : Importing using regex failed to import certain regex Key: ATLAS-2680 URL: https://issues.apache.org/jira/browse/ATLAS-2680 Project: Atlas Issue Type: Bug Components: atlas-intg Affects Versions: trunk Reporter: Ramesh Mani Fix For: trunk Import hbase script : Importing using regex failed to import certain regex contain ^, $ etc. e.g ^nm.*" nm.*a$ ns_(.)* -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2649) Updated Hive Hook to create lineage between HBase table and Hive table
[
https://issues.apache.org/jira/browse/ATLAS-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramesh Mani updated ATLAS-2649:
---
Attachment: 0001-ATLAS-2649-updated-Hive-Hook-to-create-lineage-betwe.patch
> Updated Hive Hook to create lineage between HBase table and Hive table
> --
>
> Key: ATLAS-2649
> URL: https://issues.apache.org/jira/browse/ATLAS-2649
> Project: Atlas
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: Ramesh Mani
>Assignee: Ramesh Mani
>Priority: Major
> Fix For: trunk
>
> Attachments:
> 0001-ATLAS-2649-updated-Hive-Hook-to-create-lineage-betwe.patch
>
>
> Hive Hook should create lineage entities when storage handler mechanism to
> create hbase tables via hive.
> When Hive on HBase is done via Hive's HBaseStorageHandler mechanism,
> corresponding HBase table is created in HBase and data is store in it. In
> this process Hive Hook should show Input process as Hive Table and Output as
> HBase Table.
> e.g
> CREATE TABLE hbase_table_emp(id int, name string, role string)
> STORED BY 'org.apache.hadoop.hive.hbase.HBaseStorageHandler'
> WITH SERDEPROPERTIES ("hbase.columns.mapping" = ":key,cf1:name,cf1:role")
> TBLPROPERTIES ("hbase.table.name" = "emp");
> This will create a corresponding HBase table emp
> hbase(main):003:0> list
> TABLE
> ATLAS_ENTITY_AUDIT_EVENTS
> atlas_janus
> emp
> 3 row(s)
> Took 0.0127 seconds
> => ["ATLAS_ENTITY_AUDIT_EVENTS", "atlas_janus", "emp"]
> hbase(main):004:0> describe 'emp'
> Table emp is ENABLED
> emp
> COLUMN FAMILIES DESCRIPTION
> {NAME => 'cf1', VERSIONS => '1', EVICT_BLOCKS_ON_CLOSE => 'false',
> NEW_VERSION_BEHAVIOR => 'false', KEEP_DELETED_CELLS =>
> 'FALSE', CACHE_DATA_ON_WRITE => 'false', DATA_BLOCK_ENCODING => 'NONE', TTL
> => 'FOREVER', MIN_VERSIONS => '0', REPLICATION
> _SCOPE => '0', BLOOMFILTER => 'ROW', CACHE_INDEX_ON_WRITE => 'false',
> IN_MEMORY => 'false', CACHE_BLOOMS_ON_WRITE => 'fals
> e', PREFETCH_BLOCKS_ON_OPEN => 'false', COMPRESSION => 'NONE', BLOCKCACHE =>
> 'true', BLOCKSIZE => '65536'}
> 1 row(s)
> Took 0.1961 seconds
>
> In this process the Hive hook should provide the lineage info for the
> corresponding Hive table -> HBase Table Storage.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-2649) Updated Hive Hook to create lineage between HBase table and Hive table
[
https://issues.apache.org/jira/browse/ATLAS-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramesh Mani updated ATLAS-2649:
---
Attachment: (was:
0001-ATLAS-2649-Hive-Hook-should-create-lineage-entities-.patch)
> Updated Hive Hook to create lineage between HBase table and Hive table
> --
>
> Key: ATLAS-2649
> URL: https://issues.apache.org/jira/browse/ATLAS-2649
> Project: Atlas
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: Ramesh Mani
>Assignee: Ramesh Mani
>Priority: Major
> Fix For: trunk
>
> Attachments:
> 0001-ATLAS-2649-updated-Hive-Hook-to-create-lineage-betwe.patch
>
>
> Hive Hook should create lineage entities when storage handler mechanism to
> create hbase tables via hive.
> When Hive on HBase is done via Hive's HBaseStorageHandler mechanism,
> corresponding HBase table is created in HBase and data is store in it. In
> this process Hive Hook should show Input process as Hive Table and Output as
> HBase Table.
> e.g
> CREATE TABLE hbase_table_emp(id int, name string, role string)
> STORED BY 'org.apache.hadoop.hive.hbase.HBaseStorageHandler'
> WITH SERDEPROPERTIES ("hbase.columns.mapping" = ":key,cf1:name,cf1:role")
> TBLPROPERTIES ("hbase.table.name" = "emp");
> This will create a corresponding HBase table emp
> hbase(main):003:0> list
> TABLE
> ATLAS_ENTITY_AUDIT_EVENTS
> atlas_janus
> emp
> 3 row(s)
> Took 0.0127 seconds
> => ["ATLAS_ENTITY_AUDIT_EVENTS", "atlas_janus", "emp"]
> hbase(main):004:0> describe 'emp'
> Table emp is ENABLED
> emp
> COLUMN FAMILIES DESCRIPTION
> {NAME => 'cf1', VERSIONS => '1', EVICT_BLOCKS_ON_CLOSE => 'false',
> NEW_VERSION_BEHAVIOR => 'false', KEEP_DELETED_CELLS =>
> 'FALSE', CACHE_DATA_ON_WRITE => 'false', DATA_BLOCK_ENCODING => 'NONE', TTL
> => 'FOREVER', MIN_VERSIONS => '0', REPLICATION
> _SCOPE => '0', BLOOMFILTER => 'ROW', CACHE_INDEX_ON_WRITE => 'false',
> IN_MEMORY => 'false', CACHE_BLOOMS_ON_WRITE => 'fals
> e', PREFETCH_BLOCKS_ON_OPEN => 'false', COMPRESSION => 'NONE', BLOCKCACHE =>
> 'true', BLOCKSIZE => '65536'}
> 1 row(s)
> Took 0.1961 seconds
>
> In this process the Hive hook should provide the lineage info for the
> corresponding Hive table -> HBase Table Storage.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-2649) Updated Hive Hook to create lineage between HBase table and Hive table
[
https://issues.apache.org/jira/browse/ATLAS-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramesh Mani updated ATLAS-2649:
---
Summary: Updated Hive Hook to create lineage between HBase table and Hive
table (was: Hive Hook should create lineage entities when storage handler
mechanism to create hbase tables via hive)
> Updated Hive Hook to create lineage between HBase table and Hive table
> --
>
> Key: ATLAS-2649
> URL: https://issues.apache.org/jira/browse/ATLAS-2649
> Project: Atlas
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: Ramesh Mani
>Assignee: Ramesh Mani
>Priority: Major
> Fix For: trunk
>
> Attachments:
> 0001-ATLAS-2649-Hive-Hook-should-create-lineage-entities-.patch
>
>
> Hive Hook should create lineage entities when storage handler mechanism to
> create hbase tables via hive.
> When Hive on HBase is done via Hive's HBaseStorageHandler mechanism,
> corresponding HBase table is created in HBase and data is store in it. In
> this process Hive Hook should show Input process as Hive Table and Output as
> HBase Table.
> e.g
> CREATE TABLE hbase_table_emp(id int, name string, role string)
> STORED BY 'org.apache.hadoop.hive.hbase.HBaseStorageHandler'
> WITH SERDEPROPERTIES ("hbase.columns.mapping" = ":key,cf1:name,cf1:role")
> TBLPROPERTIES ("hbase.table.name" = "emp");
> This will create a corresponding HBase table emp
> hbase(main):003:0> list
> TABLE
> ATLAS_ENTITY_AUDIT_EVENTS
> atlas_janus
> emp
> 3 row(s)
> Took 0.0127 seconds
> => ["ATLAS_ENTITY_AUDIT_EVENTS", "atlas_janus", "emp"]
> hbase(main):004:0> describe 'emp'
> Table emp is ENABLED
> emp
> COLUMN FAMILIES DESCRIPTION
> {NAME => 'cf1', VERSIONS => '1', EVICT_BLOCKS_ON_CLOSE => 'false',
> NEW_VERSION_BEHAVIOR => 'false', KEEP_DELETED_CELLS =>
> 'FALSE', CACHE_DATA_ON_WRITE => 'false', DATA_BLOCK_ENCODING => 'NONE', TTL
> => 'FOREVER', MIN_VERSIONS => '0', REPLICATION
> _SCOPE => '0', BLOOMFILTER => 'ROW', CACHE_INDEX_ON_WRITE => 'false',
> IN_MEMORY => 'false', CACHE_BLOOMS_ON_WRITE => 'fals
> e', PREFETCH_BLOCKS_ON_OPEN => 'false', COMPRESSION => 'NONE', BLOCKCACHE =>
> 'true', BLOCKSIZE => '65536'}
> 1 row(s)
> Took 0.1961 seconds
>
> In this process the Hive hook should provide the lineage info for the
> corresponding Hive table -> HBase Table Storage.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-2649) Hive Hook should create lineage entities when storage handler mechanism to create hbase tables via hive
[
https://issues.apache.org/jira/browse/ATLAS-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramesh Mani updated ATLAS-2649:
---
Attachment: 0001-ATLAS-2649-Hive-Hook-should-create-lineage-entities-.patch
> Hive Hook should create lineage entities when storage handler mechanism to
> create hbase tables via hive
> ---
>
> Key: ATLAS-2649
> URL: https://issues.apache.org/jira/browse/ATLAS-2649
> Project: Atlas
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: Ramesh Mani
>Assignee: Ramesh Mani
>Priority: Major
> Fix For: trunk
>
> Attachments:
> 0001-ATLAS-2649-Hive-Hook-should-create-lineage-entities-.patch
>
>
> Hive Hook should create lineage entities when storage handler mechanism to
> create hbase tables via hive.
> When Hive on HBase is done via Hive's HBaseStorageHandler mechanism,
> corresponding HBase table is created in HBase and data is store in it. In
> this process Hive Hook should show Input process as Hive Table and Output as
> HBase Table.
> e.g
> CREATE TABLE hbase_table_emp(id int, name string, role string)
> STORED BY 'org.apache.hadoop.hive.hbase.HBaseStorageHandler'
> WITH SERDEPROPERTIES ("hbase.columns.mapping" = ":key,cf1:name,cf1:role")
> TBLPROPERTIES ("hbase.table.name" = "emp");
> This will create a corresponding HBase table emp
> hbase(main):003:0> list
> TABLE
> ATLAS_ENTITY_AUDIT_EVENTS
> atlas_janus
> emp
> 3 row(s)
> Took 0.0127 seconds
> => ["ATLAS_ENTITY_AUDIT_EVENTS", "atlas_janus", "emp"]
> hbase(main):004:0> describe 'emp'
> Table emp is ENABLED
> emp
> COLUMN FAMILIES DESCRIPTION
> {NAME => 'cf1', VERSIONS => '1', EVICT_BLOCKS_ON_CLOSE => 'false',
> NEW_VERSION_BEHAVIOR => 'false', KEEP_DELETED_CELLS =>
> 'FALSE', CACHE_DATA_ON_WRITE => 'false', DATA_BLOCK_ENCODING => 'NONE', TTL
> => 'FOREVER', MIN_VERSIONS => '0', REPLICATION
> _SCOPE => '0', BLOOMFILTER => 'ROW', CACHE_INDEX_ON_WRITE => 'false',
> IN_MEMORY => 'false', CACHE_BLOOMS_ON_WRITE => 'fals
> e', PREFETCH_BLOCKS_ON_OPEN => 'false', COMPRESSION => 'NONE', BLOCKCACHE =>
> 'true', BLOCKSIZE => '65536'}
> 1 row(s)
> Took 0.1961 seconds
>
> In this process the Hive hook should provide the lineage info for the
> corresponding Hive table -> HBase Table Storage.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-2649) Hive Hook should create lineage entities when storage handler mechanism to create hbase tables via hive
[
https://issues.apache.org/jira/browse/ATLAS-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramesh Mani updated ATLAS-2649:
---
Attachment: (was:
0001-ATLAS-2649-Hive-Hook-should-create-lineage-entities-.patch)
> Hive Hook should create lineage entities when storage handler mechanism to
> create hbase tables via hive
> ---
>
> Key: ATLAS-2649
> URL: https://issues.apache.org/jira/browse/ATLAS-2649
> Project: Atlas
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: Ramesh Mani
>Assignee: Ramesh Mani
>Priority: Major
> Fix For: trunk
>
> Attachments:
> 0001-ATLAS-2649-Hive-Hook-should-create-lineage-entities-.patch
>
>
> Hive Hook should create lineage entities when storage handler mechanism to
> create hbase tables via hive.
> When Hive on HBase is done via Hive's HBaseStorageHandler mechanism,
> corresponding HBase table is created in HBase and data is store in it. In
> this process Hive Hook should show Input process as Hive Table and Output as
> HBase Table.
> e.g
> CREATE TABLE hbase_table_emp(id int, name string, role string)
> STORED BY 'org.apache.hadoop.hive.hbase.HBaseStorageHandler'
> WITH SERDEPROPERTIES ("hbase.columns.mapping" = ":key,cf1:name,cf1:role")
> TBLPROPERTIES ("hbase.table.name" = "emp");
> This will create a corresponding HBase table emp
> hbase(main):003:0> list
> TABLE
> ATLAS_ENTITY_AUDIT_EVENTS
> atlas_janus
> emp
> 3 row(s)
> Took 0.0127 seconds
> => ["ATLAS_ENTITY_AUDIT_EVENTS", "atlas_janus", "emp"]
> hbase(main):004:0> describe 'emp'
> Table emp is ENABLED
> emp
> COLUMN FAMILIES DESCRIPTION
> {NAME => 'cf1', VERSIONS => '1', EVICT_BLOCKS_ON_CLOSE => 'false',
> NEW_VERSION_BEHAVIOR => 'false', KEEP_DELETED_CELLS =>
> 'FALSE', CACHE_DATA_ON_WRITE => 'false', DATA_BLOCK_ENCODING => 'NONE', TTL
> => 'FOREVER', MIN_VERSIONS => '0', REPLICATION
> _SCOPE => '0', BLOOMFILTER => 'ROW', CACHE_INDEX_ON_WRITE => 'false',
> IN_MEMORY => 'false', CACHE_BLOOMS_ON_WRITE => 'fals
> e', PREFETCH_BLOCKS_ON_OPEN => 'false', COMPRESSION => 'NONE', BLOCKCACHE =>
> 'true', BLOCKSIZE => '65536'}
> 1 row(s)
> Took 0.1961 seconds
>
> In this process the Hive hook should provide the lineage info for the
> corresponding Hive table -> HBase Table Storage.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-2649) Hive Hook should create lineage entities when storage handler mechanism to create hbase tables via hive
[
https://issues.apache.org/jira/browse/ATLAS-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramesh Mani updated ATLAS-2649:
---
Attachment: 0001-ATLAS-2649-Hive-Hook-should-create-lineage-entities-.patch
> Hive Hook should create lineage entities when storage handler mechanism to
> create hbase tables via hive
> ---
>
> Key: ATLAS-2649
> URL: https://issues.apache.org/jira/browse/ATLAS-2649
> Project: Atlas
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: Ramesh Mani
>Assignee: Ramesh Mani
>Priority: Major
> Fix For: trunk
>
> Attachments:
> 0001-ATLAS-2649-Hive-Hook-should-create-lineage-entities-.patch
>
>
> Hive Hook should create lineage entities when storage handler mechanism to
> create hbase tables via hive.
> When Hive on HBase is done via Hive's HBaseStorageHandler mechanism,
> corresponding HBase table is created in HBase and data is store in it. In
> this process Hive Hook should show Input process as Hive Table and Output as
> HBase Table.
> e.g
> CREATE TABLE hbase_table_emp(id int, name string, role string)
> STORED BY 'org.apache.hadoop.hive.hbase.HBaseStorageHandler'
> WITH SERDEPROPERTIES ("hbase.columns.mapping" = ":key,cf1:name,cf1:role")
> TBLPROPERTIES ("hbase.table.name" = "emp");
> This will create a corresponding HBase table emp
> hbase(main):003:0> list
> TABLE
> ATLAS_ENTITY_AUDIT_EVENTS
> atlas_janus
> emp
> 3 row(s)
> Took 0.0127 seconds
> => ["ATLAS_ENTITY_AUDIT_EVENTS", "atlas_janus", "emp"]
> hbase(main):004:0> describe 'emp'
> Table emp is ENABLED
> emp
> COLUMN FAMILIES DESCRIPTION
> {NAME => 'cf1', VERSIONS => '1', EVICT_BLOCKS_ON_CLOSE => 'false',
> NEW_VERSION_BEHAVIOR => 'false', KEEP_DELETED_CELLS =>
> 'FALSE', CACHE_DATA_ON_WRITE => 'false', DATA_BLOCK_ENCODING => 'NONE', TTL
> => 'FOREVER', MIN_VERSIONS => '0', REPLICATION
> _SCOPE => '0', BLOOMFILTER => 'ROW', CACHE_INDEX_ON_WRITE => 'false',
> IN_MEMORY => 'false', CACHE_BLOOMS_ON_WRITE => 'fals
> e', PREFETCH_BLOCKS_ON_OPEN => 'false', COMPRESSION => 'NONE', BLOCKCACHE =>
> 'true', BLOCKSIZE => '65536'}
> 1 row(s)
> Took 0.1961 seconds
>
> In this process the Hive hook should provide the lineage info for the
> corresponding Hive table -> HBase Table Storage.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (ATLAS-2666) Add unit test to KafkaBridge
[ https://issues.apache.org/jira/browse/ATLAS-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Mani reassigned ATLAS-2666: -- Assignee: Ramesh Mani > Add unit test to KafkaBridge > > > Key: ATLAS-2666 > URL: https://issues.apache.org/jira/browse/ATLAS-2666 > Project: Atlas > Issue Type: Bug > Components: atlas-intg >Affects Versions: trunk >Reporter: Ramesh Mani >Assignee: Ramesh Mani >Priority: Minor > Fix For: trunk > > > Add unit test to KafkaBridge -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2666) Add unit test to KafkaBridge
Ramesh Mani created ATLAS-2666: -- Summary: Add unit test to KafkaBridge Key: ATLAS-2666 URL: https://issues.apache.org/jira/browse/ATLAS-2666 Project: Atlas Issue Type: Bug Components: atlas-intg Affects Versions: trunk Reporter: Ramesh Mani Fix For: trunk Add unit test to KafkaBridge -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2650) HBase Atlas Hook : Handle NPE in HBase table import when getNameAsString() is null
[ https://issues.apache.org/jira/browse/ATLAS-2650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Mani updated ATLAS-2650: --- Attachment: 0001-ATLAS-2650-HBase-Atlas-Hook-Handle-NPE-in-HBase-tabl.patch > HBase Atlas Hook : Handle NPE in HBase table import when getNameAsString() is > null > -- > > Key: ATLAS-2650 > URL: https://issues.apache.org/jira/browse/ATLAS-2650 > Project: Atlas > Issue Type: Bug > Components: atlas-intg >Affects Versions: trunk >Reporter: Ramesh Mani >Priority: Critical > Fix For: trunk > > Attachments: > 0001-ATLAS-2650-HBase-Atlas-Hook-Handle-NPE-in-HBase-tabl.patch > > > HBase Atlas Hook : Handle NPE in HBase table import when getNameAsString() is > null > When HTableDescriptor.getNameAsString() to get the table name is null, we > need to get the table name with HTableDescriptor.getTableName().getName() -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2650) HBase Atlas Hook : Handle NPE in HBase table import when getNameAsString() is null
[ https://issues.apache.org/jira/browse/ATLAS-2650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Mani updated ATLAS-2650: --- Description: HBase Atlas Hook : Handle NPE in HBase table import when getNameAsString() is null When HTableDescriptor.getNameAsString() to get the table name is null, we need to get the table name with HTableDescriptor.getTableName().getName() was: HBase Atlas Hook : Handle NPE in HBase table import when getNameAsString() is null HTableDescriptor.getNameAsString() to get the table name is null we need to get the table name with HTableDescriptor.getTableName().getName() > HBase Atlas Hook : Handle NPE in HBase table import when getNameAsString() is > null > -- > > Key: ATLAS-2650 > URL: https://issues.apache.org/jira/browse/ATLAS-2650 > Project: Atlas > Issue Type: Bug > Components: atlas-intg >Affects Versions: trunk >Reporter: Ramesh Mani >Priority: Critical > Fix For: trunk > > > HBase Atlas Hook : Handle NPE in HBase table import when getNameAsString() is > null > When HTableDescriptor.getNameAsString() to get the table name is null, we > need to get the table name with HTableDescriptor.getTableName().getName() -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2650) HBase Atlas Hook : Handle NPE in HBase table import when getNameAsString() is null
Ramesh Mani created ATLAS-2650: -- Summary: HBase Atlas Hook : Handle NPE in HBase table import when getNameAsString() is null Key: ATLAS-2650 URL: https://issues.apache.org/jira/browse/ATLAS-2650 Project: Atlas Issue Type: Bug Components: atlas-intg Affects Versions: trunk Reporter: Ramesh Mani Fix For: trunk HBase Atlas Hook : Handle NPE in HBase table import when getNameAsString() is null HTableDescriptor.getNameAsString() to get the table name is null we need to get the table name with HTableDescriptor.getTableName().getName() -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (ATLAS-2649) Hive Hook should create lineage entities when storage handler mechanism to create hbase tables via hive
[
https://issues.apache.org/jira/browse/ATLAS-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramesh Mani updated ATLAS-2649:
---
Comment: was deleted
(was: https://issues.apache.org/jira/browse/ATLAS-2649 this will have this
change included in it.)
> Hive Hook should create lineage entities when storage handler mechanism to
> create hbase tables via hive
> ---
>
> Key: ATLAS-2649
> URL: https://issues.apache.org/jira/browse/ATLAS-2649
> Project: Atlas
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: Ramesh Mani
>Assignee: Ramesh Mani
>Priority: Major
> Fix For: trunk
>
>
> Hive Hook should create lineage entities when storage handler mechanism to
> create hbase tables via hive.
> When Hive on HBase is done via Hive's HBaseStorageHandler mechanism,
> corresponding HBase table is created in HBase and data is store in it. In
> this process Hive Hook should show Input process as Hive Table and Output as
> HBase Table.
> e.g
> CREATE TABLE hbase_table_emp(id int, name string, role string)
> STORED BY 'org.apache.hadoop.hive.hbase.HBaseStorageHandler'
> WITH SERDEPROPERTIES ("hbase.columns.mapping" = ":key,cf1:name,cf1:role")
> TBLPROPERTIES ("hbase.table.name" = "emp");
> This will create a corresponding HBase table emp
> hbase(main):003:0> list
> TABLE
> ATLAS_ENTITY_AUDIT_EVENTS
> atlas_janus
> emp
> 3 row(s)
> Took 0.0127 seconds
> => ["ATLAS_ENTITY_AUDIT_EVENTS", "atlas_janus", "emp"]
> hbase(main):004:0> describe 'emp'
> Table emp is ENABLED
> emp
> COLUMN FAMILIES DESCRIPTION
> {NAME => 'cf1', VERSIONS => '1', EVICT_BLOCKS_ON_CLOSE => 'false',
> NEW_VERSION_BEHAVIOR => 'false', KEEP_DELETED_CELLS =>
> 'FALSE', CACHE_DATA_ON_WRITE => 'false', DATA_BLOCK_ENCODING => 'NONE', TTL
> => 'FOREVER', MIN_VERSIONS => '0', REPLICATION
> _SCOPE => '0', BLOOMFILTER => 'ROW', CACHE_INDEX_ON_WRITE => 'false',
> IN_MEMORY => 'false', CACHE_BLOOMS_ON_WRITE => 'fals
> e', PREFETCH_BLOCKS_ON_OPEN => 'false', COMPRESSION => 'NONE', BLOCKCACHE =>
> 'true', BLOCKSIZE => '65536'}
> 1 row(s)
> Took 0.1961 seconds
>
> In this process the Hive hook should provide the lineage info for the
> corresponding Hive table -> HBase Table Storage.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (ATLAS-2649) Hive Hook should create lineage entities when storage handler mechanism to create hbase tables via hive
[
https://issues.apache.org/jira/browse/ATLAS-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16466205#comment-16466205
]
Ramesh Mani commented on ATLAS-2649:
https://issues.apache.org/jira/browse/ATLAS-2649 this will have this change
included in it.
> Hive Hook should create lineage entities when storage handler mechanism to
> create hbase tables via hive
> ---
>
> Key: ATLAS-2649
> URL: https://issues.apache.org/jira/browse/ATLAS-2649
> Project: Atlas
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: Ramesh Mani
>Assignee: Ramesh Mani
>Priority: Major
> Fix For: trunk
>
>
> Hive Hook should create lineage entities when storage handler mechanism to
> create hbase tables via hive.
> When Hive on HBase is done via Hive's HBaseStorageHandler mechanism,
> corresponding HBase table is created in HBase and data is store in it. In
> this process Hive Hook should show Input process as Hive Table and Output as
> HBase Table.
> e.g
> CREATE TABLE hbase_table_emp(id int, name string, role string)
> STORED BY 'org.apache.hadoop.hive.hbase.HBaseStorageHandler'
> WITH SERDEPROPERTIES ("hbase.columns.mapping" = ":key,cf1:name,cf1:role")
> TBLPROPERTIES ("hbase.table.name" = "emp");
> This will create a corresponding HBase table emp
> hbase(main):003:0> list
> TABLE
> ATLAS_ENTITY_AUDIT_EVENTS
> atlas_janus
> emp
> 3 row(s)
> Took 0.0127 seconds
> => ["ATLAS_ENTITY_AUDIT_EVENTS", "atlas_janus", "emp"]
> hbase(main):004:0> describe 'emp'
> Table emp is ENABLED
> emp
> COLUMN FAMILIES DESCRIPTION
> {NAME => 'cf1', VERSIONS => '1', EVICT_BLOCKS_ON_CLOSE => 'false',
> NEW_VERSION_BEHAVIOR => 'false', KEEP_DELETED_CELLS =>
> 'FALSE', CACHE_DATA_ON_WRITE => 'false', DATA_BLOCK_ENCODING => 'NONE', TTL
> => 'FOREVER', MIN_VERSIONS => '0', REPLICATION
> _SCOPE => '0', BLOOMFILTER => 'ROW', CACHE_INDEX_ON_WRITE => 'false',
> IN_MEMORY => 'false', CACHE_BLOOMS_ON_WRITE => 'fals
> e', PREFETCH_BLOCKS_ON_OPEN => 'false', COMPRESSION => 'NONE', BLOCKCACHE =>
> 'true', BLOCKSIZE => '65536'}
> 1 row(s)
> Took 0.1961 seconds
>
> In this process the Hive hook should provide the lineage info for the
> corresponding Hive table -> HBase Table Storage.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (ATLAS-2649) Hive Hook should create lineage entities when storage handler mechanism to create hbase tables via hive
[
https://issues.apache.org/jira/browse/ATLAS-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramesh Mani updated ATLAS-2649:
---
Comment: was deleted
(was: https://issues.apache.org/jira/browse/ATLAS-2649 this will have this
change included in it.)
> Hive Hook should create lineage entities when storage handler mechanism to
> create hbase tables via hive
> ---
>
> Key: ATLAS-2649
> URL: https://issues.apache.org/jira/browse/ATLAS-2649
> Project: Atlas
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: Ramesh Mani
>Assignee: Ramesh Mani
>Priority: Major
> Fix For: trunk
>
>
> Hive Hook should create lineage entities when storage handler mechanism to
> create hbase tables via hive.
> When Hive on HBase is done via Hive's HBaseStorageHandler mechanism,
> corresponding HBase table is created in HBase and data is store in it. In
> this process Hive Hook should show Input process as Hive Table and Output as
> HBase Table.
> e.g
> CREATE TABLE hbase_table_emp(id int, name string, role string)
> STORED BY 'org.apache.hadoop.hive.hbase.HBaseStorageHandler'
> WITH SERDEPROPERTIES ("hbase.columns.mapping" = ":key,cf1:name,cf1:role")
> TBLPROPERTIES ("hbase.table.name" = "emp");
> This will create a corresponding HBase table emp
> hbase(main):003:0> list
> TABLE
> ATLAS_ENTITY_AUDIT_EVENTS
> atlas_janus
> emp
> 3 row(s)
> Took 0.0127 seconds
> => ["ATLAS_ENTITY_AUDIT_EVENTS", "atlas_janus", "emp"]
> hbase(main):004:0> describe 'emp'
> Table emp is ENABLED
> emp
> COLUMN FAMILIES DESCRIPTION
> {NAME => 'cf1', VERSIONS => '1', EVICT_BLOCKS_ON_CLOSE => 'false',
> NEW_VERSION_BEHAVIOR => 'false', KEEP_DELETED_CELLS =>
> 'FALSE', CACHE_DATA_ON_WRITE => 'false', DATA_BLOCK_ENCODING => 'NONE', TTL
> => 'FOREVER', MIN_VERSIONS => '0', REPLICATION
> _SCOPE => '0', BLOOMFILTER => 'ROW', CACHE_INDEX_ON_WRITE => 'false',
> IN_MEMORY => 'false', CACHE_BLOOMS_ON_WRITE => 'fals
> e', PREFETCH_BLOCKS_ON_OPEN => 'false', COMPRESSION => 'NONE', BLOCKCACHE =>
> 'true', BLOCKSIZE => '65536'}
> 1 row(s)
> Took 0.1961 seconds
>
> In this process the Hive hook should provide the lineage info for the
> corresponding Hive table -> HBase Table Storage.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (ATLAS-2649) Hive Hook should create lineage entities when storage handler mechanism to create hbase tables via hive
[
https://issues.apache.org/jira/browse/ATLAS-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16465515#comment-16465515
]
Ramesh Mani commented on ATLAS-2649:
https://issues.apache.org/jira/browse/ATLAS-2649 this will have this change
included in it.
> Hive Hook should create lineage entities when storage handler mechanism to
> create hbase tables via hive
> ---
>
> Key: ATLAS-2649
> URL: https://issues.apache.org/jira/browse/ATLAS-2649
> Project: Atlas
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: Ramesh Mani
>Assignee: Ramesh Mani
>Priority: Major
> Fix For: trunk
>
>
> Hive Hook should create lineage entities when storage handler mechanism to
> create hbase tables via hive.
> When Hive on HBase is done via Hive's HBaseStorageHandler mechanism,
> corresponding HBase table is created in HBase and data is store in it. In
> this process Hive Hook should show Input process as Hive Table and Output as
> HBase Table.
> e.g
> CREATE TABLE hbase_table_emp(id int, name string, role string)
> STORED BY 'org.apache.hadoop.hive.hbase.HBaseStorageHandler'
> WITH SERDEPROPERTIES ("hbase.columns.mapping" = ":key,cf1:name,cf1:role")
> TBLPROPERTIES ("hbase.table.name" = "emp");
> This will create a corresponding HBase table emp
> hbase(main):003:0> list
> TABLE
> ATLAS_ENTITY_AUDIT_EVENTS
> atlas_janus
> emp
> 3 row(s)
> Took 0.0127 seconds
> => ["ATLAS_ENTITY_AUDIT_EVENTS", "atlas_janus", "emp"]
> hbase(main):004:0> describe 'emp'
> Table emp is ENABLED
> emp
> COLUMN FAMILIES DESCRIPTION
> {NAME => 'cf1', VERSIONS => '1', EVICT_BLOCKS_ON_CLOSE => 'false',
> NEW_VERSION_BEHAVIOR => 'false', KEEP_DELETED_CELLS =>
> 'FALSE', CACHE_DATA_ON_WRITE => 'false', DATA_BLOCK_ENCODING => 'NONE', TTL
> => 'FOREVER', MIN_VERSIONS => '0', REPLICATION
> _SCOPE => '0', BLOOMFILTER => 'ROW', CACHE_INDEX_ON_WRITE => 'false',
> IN_MEMORY => 'false', CACHE_BLOOMS_ON_WRITE => 'fals
> e', PREFETCH_BLOCKS_ON_OPEN => 'false', COMPRESSION => 'NONE', BLOCKCACHE =>
> 'true', BLOCKSIZE => '65536'}
> 1 row(s)
> Took 0.1961 seconds
>
> In this process the Hive hook should provide the lineage info for the
> corresponding Hive table -> HBase Table Storage.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-2649) Hive Hook should create lineage entities when storage handler mechanism to create hbase tables via hive
[
https://issues.apache.org/jira/browse/ATLAS-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramesh Mani updated ATLAS-2649:
---
Affects Version/s: trunk
> Hive Hook should create lineage entities when storage handler mechanism to
> create hbase tables via hive
> ---
>
> Key: ATLAS-2649
> URL: https://issues.apache.org/jira/browse/ATLAS-2649
> Project: Atlas
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: Ramesh Mani
>Priority: Major
> Fix For: trunk
>
>
> Hive Hook should create lineage entities when storage handler mechanism to
> create hbase tables via hive.
> When Hive on HBase is done via Hive's HBaseStorageHandler mechanism,
> corresponding HBase table is created in HBase and data is store in it. In
> this process Hive Hook should show Input process as Hive Table and Output as
> HBase Table.
> e.g
> CREATE TABLE hbase_table_emp(id int, name string, role string)
> STORED BY 'org.apache.hadoop.hive.hbase.HBaseStorageHandler'
> WITH SERDEPROPERTIES ("hbase.columns.mapping" = ":key,cf1:name,cf1:role")
> TBLPROPERTIES ("hbase.table.name" = "emp");
> This will create a corresponding HBase table emp
> hbase(main):003:0> list
> TABLE
> ATLAS_ENTITY_AUDIT_EVENTS
> atlas_janus
> emp
> 3 row(s)
> Took 0.0127 seconds
> => ["ATLAS_ENTITY_AUDIT_EVENTS", "atlas_janus", "emp"]
> hbase(main):004:0> describe 'emp'
> Table emp is ENABLED
> emp
> COLUMN FAMILIES DESCRIPTION
> {NAME => 'cf1', VERSIONS => '1', EVICT_BLOCKS_ON_CLOSE => 'false',
> NEW_VERSION_BEHAVIOR => 'false', KEEP_DELETED_CELLS =>
> 'FALSE', CACHE_DATA_ON_WRITE => 'false', DATA_BLOCK_ENCODING => 'NONE', TTL
> => 'FOREVER', MIN_VERSIONS => '0', REPLICATION
> _SCOPE => '0', BLOOMFILTER => 'ROW', CACHE_INDEX_ON_WRITE => 'false',
> IN_MEMORY => 'false', CACHE_BLOOMS_ON_WRITE => 'fals
> e', PREFETCH_BLOCKS_ON_OPEN => 'false', COMPRESSION => 'NONE', BLOCKCACHE =>
> 'true', BLOCKSIZE => '65536'}
> 1 row(s)
> Took 0.1961 seconds
>
> In this process the Hive hook should provide the lineage info for the
> corresponding Hive table -> HBase Table Storage.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (ATLAS-2649) Hive Hook should create lineage entities when storage handler mechanism to create hbase tables via hive
[
https://issues.apache.org/jira/browse/ATLAS-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramesh Mani reassigned ATLAS-2649:
--
Assignee: Ramesh Mani
> Hive Hook should create lineage entities when storage handler mechanism to
> create hbase tables via hive
> ---
>
> Key: ATLAS-2649
> URL: https://issues.apache.org/jira/browse/ATLAS-2649
> Project: Atlas
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: Ramesh Mani
>Assignee: Ramesh Mani
>Priority: Major
> Fix For: trunk
>
>
> Hive Hook should create lineage entities when storage handler mechanism to
> create hbase tables via hive.
> When Hive on HBase is done via Hive's HBaseStorageHandler mechanism,
> corresponding HBase table is created in HBase and data is store in it. In
> this process Hive Hook should show Input process as Hive Table and Output as
> HBase Table.
> e.g
> CREATE TABLE hbase_table_emp(id int, name string, role string)
> STORED BY 'org.apache.hadoop.hive.hbase.HBaseStorageHandler'
> WITH SERDEPROPERTIES ("hbase.columns.mapping" = ":key,cf1:name,cf1:role")
> TBLPROPERTIES ("hbase.table.name" = "emp");
> This will create a corresponding HBase table emp
> hbase(main):003:0> list
> TABLE
> ATLAS_ENTITY_AUDIT_EVENTS
> atlas_janus
> emp
> 3 row(s)
> Took 0.0127 seconds
> => ["ATLAS_ENTITY_AUDIT_EVENTS", "atlas_janus", "emp"]
> hbase(main):004:0> describe 'emp'
> Table emp is ENABLED
> emp
> COLUMN FAMILIES DESCRIPTION
> {NAME => 'cf1', VERSIONS => '1', EVICT_BLOCKS_ON_CLOSE => 'false',
> NEW_VERSION_BEHAVIOR => 'false', KEEP_DELETED_CELLS =>
> 'FALSE', CACHE_DATA_ON_WRITE => 'false', DATA_BLOCK_ENCODING => 'NONE', TTL
> => 'FOREVER', MIN_VERSIONS => '0', REPLICATION
> _SCOPE => '0', BLOOMFILTER => 'ROW', CACHE_INDEX_ON_WRITE => 'false',
> IN_MEMORY => 'false', CACHE_BLOOMS_ON_WRITE => 'fals
> e', PREFETCH_BLOCKS_ON_OPEN => 'false', COMPRESSION => 'NONE', BLOCKCACHE =>
> 'true', BLOCKSIZE => '65536'}
> 1 row(s)
> Took 0.1961 seconds
>
> In this process the Hive hook should provide the lineage info for the
> corresponding Hive table -> HBase Table Storage.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-2649) Hive Hook should create lineage entities when storage handler mechanism to create hbase tables via hive
[
https://issues.apache.org/jira/browse/ATLAS-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramesh Mani updated ATLAS-2649:
---
Fix Version/s: trunk
> Hive Hook should create lineage entities when storage handler mechanism to
> create hbase tables via hive
> ---
>
> Key: ATLAS-2649
> URL: https://issues.apache.org/jira/browse/ATLAS-2649
> Project: Atlas
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: Ramesh Mani
>Priority: Major
> Fix For: trunk
>
>
> Hive Hook should create lineage entities when storage handler mechanism to
> create hbase tables via hive.
> When Hive on HBase is done via Hive's HBaseStorageHandler mechanism,
> corresponding HBase table is created in HBase and data is store in it. In
> this process Hive Hook should show Input process as Hive Table and Output as
> HBase Table.
> e.g
> CREATE TABLE hbase_table_emp(id int, name string, role string)
> STORED BY 'org.apache.hadoop.hive.hbase.HBaseStorageHandler'
> WITH SERDEPROPERTIES ("hbase.columns.mapping" = ":key,cf1:name,cf1:role")
> TBLPROPERTIES ("hbase.table.name" = "emp");
> This will create a corresponding HBase table emp
> hbase(main):003:0> list
> TABLE
> ATLAS_ENTITY_AUDIT_EVENTS
> atlas_janus
> emp
> 3 row(s)
> Took 0.0127 seconds
> => ["ATLAS_ENTITY_AUDIT_EVENTS", "atlas_janus", "emp"]
> hbase(main):004:0> describe 'emp'
> Table emp is ENABLED
> emp
> COLUMN FAMILIES DESCRIPTION
> {NAME => 'cf1', VERSIONS => '1', EVICT_BLOCKS_ON_CLOSE => 'false',
> NEW_VERSION_BEHAVIOR => 'false', KEEP_DELETED_CELLS =>
> 'FALSE', CACHE_DATA_ON_WRITE => 'false', DATA_BLOCK_ENCODING => 'NONE', TTL
> => 'FOREVER', MIN_VERSIONS => '0', REPLICATION
> _SCOPE => '0', BLOOMFILTER => 'ROW', CACHE_INDEX_ON_WRITE => 'false',
> IN_MEMORY => 'false', CACHE_BLOOMS_ON_WRITE => 'fals
> e', PREFETCH_BLOCKS_ON_OPEN => 'false', COMPRESSION => 'NONE', BLOCKCACHE =>
> 'true', BLOCKSIZE => '65536'}
> 1 row(s)
> Took 0.1961 seconds
>
> In this process the Hive hook should provide the lineage info for the
> corresponding Hive table -> HBase Table Storage.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (ATLAS-2649) Hive Hook should create lineage entities when storage handler mechanism to create hbase tables via hive
Ramesh Mani created ATLAS-2649:
--
Summary: Hive Hook should create lineage entities when storage
handler mechanism to create hbase tables via hive
Key: ATLAS-2649
URL: https://issues.apache.org/jira/browse/ATLAS-2649
Project: Atlas
Issue Type: Bug
Reporter: Ramesh Mani
Hive Hook should create lineage entities when storage handler mechanism to
create hbase tables via hive.
When Hive on HBase is done via Hive's HBaseStorageHandler mechanism,
corresponding HBase table is created in HBase and data is store in it. In this
process Hive Hook should show Input process as Hive Table and Output as HBase
Table.
e.g
CREATE TABLE hbase_table_emp(id int, name string, role string)
STORED BY 'org.apache.hadoop.hive.hbase.HBaseStorageHandler'
WITH SERDEPROPERTIES ("hbase.columns.mapping" = ":key,cf1:name,cf1:role")
TBLPROPERTIES ("hbase.table.name" = "emp");
This will create a corresponding HBase table emp
hbase(main):003:0> list
TABLE
ATLAS_ENTITY_AUDIT_EVENTS
atlas_janus
emp
3 row(s)
Took 0.0127 seconds
=> ["ATLAS_ENTITY_AUDIT_EVENTS", "atlas_janus", "emp"]
hbase(main):004:0> describe 'emp'
Table emp is ENABLED
emp
COLUMN FAMILIES DESCRIPTION
{NAME => 'cf1', VERSIONS => '1', EVICT_BLOCKS_ON_CLOSE => 'false',
NEW_VERSION_BEHAVIOR => 'false', KEEP_DELETED_CELLS =>
'FALSE', CACHE_DATA_ON_WRITE => 'false', DATA_BLOCK_ENCODING => 'NONE', TTL =>
'FOREVER', MIN_VERSIONS => '0', REPLICATION
_SCOPE => '0', BLOOMFILTER => 'ROW', CACHE_INDEX_ON_WRITE => 'false', IN_MEMORY
=> 'false', CACHE_BLOOMS_ON_WRITE => 'fals
e', PREFETCH_BLOCKS_ON_OPEN => 'false', COMPRESSION => 'NONE', BLOCKCACHE =>
'true', BLOCKSIZE => '65536'}
1 row(s)
Took 0.1961 seconds
In this process the Hive hook should provide the lineage info for the
corresponding Hive table -> HBase Table Storage.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-2603) [Docs] Add Atlas Kafka Bridge Documents
[ https://issues.apache.org/jira/browse/ATLAS-2603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Mani updated ATLAS-2603: --- Attachment: 0001-ATLAS-2603-Docs-Add-Atlas-Kafka-Bridge-Documents_003.patch > [Docs] Add Atlas Kafka Bridge Documents > --- > > Key: ATLAS-2603 > URL: https://issues.apache.org/jira/browse/ATLAS-2603 > Project: Atlas > Issue Type: Bug >Reporter: Ramesh Mani >Assignee: Ramesh Mani >Priority: Major > Fix For: 1.0.0 > > Attachments: > 0001-ATLAS-2603-Docs-Add-Atlas-Kafka-Bridge-Documents.patch, > 0001-ATLAS-2603-Docs-Add-Atlas-Kafka-Bridge-Documents_002.patch, > 0001-ATLAS-2603-Docs-Add-Atlas-Kafka-Bridge-Documents_003.patch > > > [Docs] Add Atlas Kafka Bridge Documents -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2603) [Docs] Add Atlas Kafka Bridge Documents
[ https://issues.apache.org/jira/browse/ATLAS-2603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Mani updated ATLAS-2603: --- Attachment: 0001-ATLAS-2603-Docs-Add-Atlas-Kafka-Bridge-Documents_002.patch > [Docs] Add Atlas Kafka Bridge Documents > --- > > Key: ATLAS-2603 > URL: https://issues.apache.org/jira/browse/ATLAS-2603 > Project: Atlas > Issue Type: Bug >Reporter: Ramesh Mani >Assignee: Ramesh Mani >Priority: Major > Fix For: 1.0.0 > > Attachments: > 0001-ATLAS-2603-Docs-Add-Atlas-Kafka-Bridge-Documents.patch, > 0001-ATLAS-2603-Docs-Add-Atlas-Kafka-Bridge-Documents_002.patch > > > [Docs] Add Atlas Kafka Bridge Documents -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2317) [Docs] Add HBase Bridge Documents
[ https://issues.apache.org/jira/browse/ATLAS-2317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Mani updated ATLAS-2317: --- Fix Version/s: 1.0.0 > [Docs] Add HBase Bridge Documents > - > > Key: ATLAS-2317 > URL: https://issues.apache.org/jira/browse/ATLAS-2317 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.8.1 >Reporter: ShuMing Li >Assignee: Ramesh Mani >Priority: Major > Fix For: 1.0.0 > > Attachments: 0001-ATLAS-2317-Docs-Add-HBase-Bridge-Documents.patch > > > Since HBase Bridge has been already > supported(https://issues.apache.org/jira/browse/ATLAS-1805), We should update > index > docs(https://github.com/apache/atlas/blob/master/docs/src/site/twiki/index.twiki) > to add HBase Config knowledge. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2603) [Docs] Add Atlas Kafka Bridge Documents
[ https://issues.apache.org/jira/browse/ATLAS-2603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Mani updated ATLAS-2603: --- Fix Version/s: 1.0.0 > [Docs] Add Atlas Kafka Bridge Documents > --- > > Key: ATLAS-2603 > URL: https://issues.apache.org/jira/browse/ATLAS-2603 > Project: Atlas > Issue Type: Bug >Reporter: Ramesh Mani >Assignee: Ramesh Mani >Priority: Major > Fix For: 1.0.0 > > Attachments: > 0001-ATLAS-2603-Docs-Add-Atlas-Kafka-Bridge-Documents.patch > > > [Docs] Add Atlas Kafka Bridge Documents -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2603) [Docs] Add Atlas Kafka Bridge Documents
[ https://issues.apache.org/jira/browse/ATLAS-2603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Mani updated ATLAS-2603: --- Attachment: 0001-ATLAS-2603-Docs-Add-Atlas-Kafka-Bridge-Documents.patch > [Docs] Add Atlas Kafka Bridge Documents > --- > > Key: ATLAS-2603 > URL: https://issues.apache.org/jira/browse/ATLAS-2603 > Project: Atlas > Issue Type: Bug >Reporter: Ramesh Mani >Assignee: Ramesh Mani >Priority: Major > Attachments: > 0001-ATLAS-2603-Docs-Add-Atlas-Kafka-Bridge-Documents.patch > > > [Docs] Add Atlas Kafka Bridge Documents -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2317) [Docs] Add HBase Bridge Documents
[ https://issues.apache.org/jira/browse/ATLAS-2317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Mani updated ATLAS-2317: --- Attachment: 0001-ATLAS-2317-Docs-Add-HBase-Bridge-Documents.patch > [Docs] Add HBase Bridge Documents > - > > Key: ATLAS-2317 > URL: https://issues.apache.org/jira/browse/ATLAS-2317 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.8.1 >Reporter: ShuMing Li >Assignee: Ramesh Mani >Priority: Major > Attachments: 0001-ATLAS-2317-Docs-Add-HBase-Bridge-Documents.patch > > > Since HBase Bridge has been already > supported(https://issues.apache.org/jira/browse/ATLAS-1805), We should update > index > docs(https://github.com/apache/atlas/blob/master/docs/src/site/twiki/index.twiki) > to add HBase Config knowledge. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2317) [Docs] Add HBase Bridge Documents
[ https://issues.apache.org/jira/browse/ATLAS-2317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Mani updated ATLAS-2317: --- Attachment: (was: 0001-ATLAS-2317-Docs-Add-HBase-Bridge-Documents.patch) > [Docs] Add HBase Bridge Documents > - > > Key: ATLAS-2317 > URL: https://issues.apache.org/jira/browse/ATLAS-2317 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.8.1 >Reporter: ShuMing Li >Assignee: Ramesh Mani >Priority: Major > Attachments: 0001-ATLAS-2317-Docs-Add-HBase-Bridge-Documents.patch > > > Since HBase Bridge has been already > supported(https://issues.apache.org/jira/browse/ATLAS-1805), We should update > index > docs(https://github.com/apache/atlas/blob/master/docs/src/site/twiki/index.twiki) > to add HBase Config knowledge. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2603) [Docs] Add Atlas Kafka Bridge Documents
Ramesh Mani created ATLAS-2603: -- Summary: [Docs] Add Atlas Kafka Bridge Documents Key: ATLAS-2603 URL: https://issues.apache.org/jira/browse/ATLAS-2603 Project: Atlas Issue Type: Bug Reporter: Ramesh Mani Assignee: Ramesh Mani -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2603) [Docs] Add Atlas Kafka Bridge Documents
[ https://issues.apache.org/jira/browse/ATLAS-2603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Mani updated ATLAS-2603: --- Description: [Docs] Add Atlas Kafka Bridge Documents > [Docs] Add Atlas Kafka Bridge Documents > --- > > Key: ATLAS-2603 > URL: https://issues.apache.org/jira/browse/ATLAS-2603 > Project: Atlas > Issue Type: Bug >Reporter: Ramesh Mani >Assignee: Ramesh Mani >Priority: Major > > [Docs] Add Atlas Kafka Bridge Documents -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2317) [Docs] Add HBase Bridge Documents
[ https://issues.apache.org/jira/browse/ATLAS-2317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Mani updated ATLAS-2317: --- Attachment: 0001-ATLAS-2317-Docs-Add-HBase-Bridge-Documents.patch > [Docs] Add HBase Bridge Documents > - > > Key: ATLAS-2317 > URL: https://issues.apache.org/jira/browse/ATLAS-2317 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.8.1 >Reporter: ShuMing Li >Assignee: Ramesh Mani >Priority: Major > Attachments: 0001-ATLAS-2317-Docs-Add-HBase-Bridge-Documents.patch > > > Since HBase Bridge has been already > supported(https://issues.apache.org/jira/browse/ATLAS-1805), We should update > index > docs(https://github.com/apache/atlas/blob/master/docs/src/site/twiki/index.twiki) > to add HBase Config knowledge. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2586) Provide a utility to Import Kafka Entities into Atlas
[ https://issues.apache.org/jira/browse/ATLAS-2586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Mani updated ATLAS-2586: --- Attachment: 0001-ATLAS-2586-Provide-a-utility-to-Import-Kafka-Entitie_002.patch 0001-ATLAS-2586-Provide-a-utility-to-Import-Kafka-Entitie_001.patch > Provide a utility to Import Kafka Entities into Atlas > - > > Key: ATLAS-2586 > URL: https://issues.apache.org/jira/browse/ATLAS-2586 > Project: Atlas > Issue Type: Bug > Components: atlas-intg >Affects Versions: trunk, 1.0.0 >Reporter: Ramesh Mani >Assignee: Ramesh Mani >Priority: Major > Attachments: > 0001-ATLAS-2586-Provide-a-utility-to-Import-Kafka-Entitie.patch, > 0001-ATLAS-2586-Provide-a-utility-to-Import-Kafka-Entitie_001.patch, > 0001-ATLAS-2586-Provide-a-utility-to-Import-Kafka-Entitie_002.patch > > > Provide a utility to Import Kafka Entities into Atlas. Currently this will > handle TOPIC level metadata propagation to Atlas -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2586) Provide a utility to Import Kafka Entities into Atlas
[ https://issues.apache.org/jira/browse/ATLAS-2586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Mani updated ATLAS-2586: --- Attachment: 0001-ATLAS-2586-Provide-a-utility-to-Import-Kafka-Entitie.patch > Provide a utility to Import Kafka Entities into Atlas > - > > Key: ATLAS-2586 > URL: https://issues.apache.org/jira/browse/ATLAS-2586 > Project: Atlas > Issue Type: Bug > Components: atlas-intg >Affects Versions: trunk, 1.0.0 >Reporter: Ramesh Mani >Assignee: Ramesh Mani >Priority: Major > Attachments: > 0001-ATLAS-2586-Provide-a-utility-to-Import-Kafka-Entitie.patch > > > Provide a utility to Import Kafka Entities into Atlas. Currently this will > handle TOPIC level metadata propagation to Atlas -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2586) Provide a utility to Import Kafka Entities into Atlas
[ https://issues.apache.org/jira/browse/ATLAS-2586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Mani updated ATLAS-2586: --- Attachment: (was: 0001-ATLAS-2586-Provide-a-utility-to-Import-Kafka-Entitie.patch) > Provide a utility to Import Kafka Entities into Atlas > - > > Key: ATLAS-2586 > URL: https://issues.apache.org/jira/browse/ATLAS-2586 > Project: Atlas > Issue Type: Bug > Components: atlas-intg >Affects Versions: trunk, 1.0.0 >Reporter: Ramesh Mani >Assignee: Ramesh Mani >Priority: Major > Attachments: > 0001-ATLAS-2586-Provide-a-utility-to-Import-Kafka-Entitie.patch > > > Provide a utility to Import Kafka Entities into Atlas. Currently this will > handle TOPIC level metadata propagation to Atlas -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2586) Provide a utility to Import Kafka Entities into Atlas
[ https://issues.apache.org/jira/browse/ATLAS-2586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Mani updated ATLAS-2586: --- Attachment: 0001-ATLAS-2586-Provide-a-utility-to-Import-Kafka-Entitie.patch > Provide a utility to Import Kafka Entities into Atlas > - > > Key: ATLAS-2586 > URL: https://issues.apache.org/jira/browse/ATLAS-2586 > Project: Atlas > Issue Type: Bug > Components: atlas-intg >Affects Versions: trunk, 1.0.0 >Reporter: Ramesh Mani >Assignee: Ramesh Mani >Priority: Major > Attachments: > 0001-ATLAS-2586-Provide-a-utility-to-Import-Kafka-Entitie.patch > > > Provide a utility to Import Kafka Entities into Atlas. Currently this will > handle TOPIC level metadata propagation to Atlas -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2586) Provide a utility to Import Kafka Entities into Atlas
Ramesh Mani created ATLAS-2586: -- Summary: Provide a utility to Import Kafka Entities into Atlas Key: ATLAS-2586 URL: https://issues.apache.org/jira/browse/ATLAS-2586 Project: Atlas Issue Type: Bug Components: atlas-intg Affects Versions: trunk, 1.0.0 Reporter: Ramesh Mani Assignee: Ramesh Mani -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2559) HBase Atlas Hook doesn't create relationship between namespace and tables
[ https://issues.apache.org/jira/browse/ATLAS-2559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Mani updated ATLAS-2559: --- Attachment: 0001-ATLAS-2559-HBase-Atlas-Hook-doesn-t-create-relations.patch > HBase Atlas Hook doesn't create relationship between namespace and tables > - > > Key: ATLAS-2559 > URL: https://issues.apache.org/jira/browse/ATLAS-2559 > Project: Atlas > Issue Type: Bug > Components: atlas-intg >Affects Versions: trunk >Reporter: Ramesh Mani >Assignee: Ramesh Mani >Priority: Major > Fix For: trunk > > Attachments: > 0001-ATLAS-2559-HBase-Atlas-Hook-doesn-t-create-relations.patch > > > Atlas Entities created in HBase Atlas Hook doesn't have relationship between > HBase Namespace and Tables. > API /api/atlas/v2/entity/guid/ returned namespace entity json > with no relationship for namespace -> tables. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2559) HBase Atlas Hook doesn't create relationship between namespace and tables
[ https://issues.apache.org/jira/browse/ATLAS-2559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16436686#comment-16436686 ] Ramesh Mani commented on ATLAS-2559: Review link https://reviews.apache.org/r/66595/ > HBase Atlas Hook doesn't create relationship between namespace and tables > - > > Key: ATLAS-2559 > URL: https://issues.apache.org/jira/browse/ATLAS-2559 > Project: Atlas > Issue Type: Bug > Components: atlas-intg >Affects Versions: trunk >Reporter: Ramesh Mani >Assignee: Ramesh Mani >Priority: Major > Fix For: trunk > > Attachments: > 0001-ATLAS-2559-HBase-Atlas-Hook-doesn-t-create-relations.patch > > > Atlas Entities created in HBase Atlas Hook doesn't have relationship between > HBase Namespace and Tables. > API /api/atlas/v2/entity/guid/ returned namespace entity json > with no relationship for namespace -> tables. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2559) HBase Atlas Hook doesn't create relationship between namespace and tables
[ https://issues.apache.org/jira/browse/ATLAS-2559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Mani updated ATLAS-2559: --- Summary: HBase Atlas Hook doesn't create relationship between namespace and tables (was: HBase Atlas Hook doesn't create relationship between namespace and table) > HBase Atlas Hook doesn't create relationship between namespace and tables > - > > Key: ATLAS-2559 > URL: https://issues.apache.org/jira/browse/ATLAS-2559 > Project: Atlas > Issue Type: Bug > Components: atlas-intg >Affects Versions: trunk >Reporter: Ramesh Mani >Assignee: Ramesh Mani >Priority: Major > Fix For: trunk > > > Atlas Entities created in HBase Atlas Hook doesn't have relationship between > HBase Namespace and Tables. > API /api/atlas/v2/entity/guid/ returned namespace entity json > with no relationship for namespace -> tables. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2559) HBase Atlas Hook doesn't create relationship between namespace and table
[ https://issues.apache.org/jira/browse/ATLAS-2559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Mani updated ATLAS-2559: --- Description: Atlas Entities created in HBase Atlas Hook doesn't have relationship between HBase Namespace and Tables. API /api/atlas/v2/entity/guid/ returned namespace entity json with no relationship for namespace -> tables. was: Atlas Entities created in HBase Atlas Hook doesn't have relationship between HBase Namespace and Tables. API /api/atlas/v2/entity/guid/ returned namespace entity json with no relationship for namespace -> table. > HBase Atlas Hook doesn't create relationship between namespace and table > > > Key: ATLAS-2559 > URL: https://issues.apache.org/jira/browse/ATLAS-2559 > Project: Atlas > Issue Type: Bug > Components: atlas-intg >Affects Versions: trunk >Reporter: Ramesh Mani >Assignee: Ramesh Mani >Priority: Major > Fix For: trunk > > > Atlas Entities created in HBase Atlas Hook doesn't have relationship between > HBase Namespace and Tables. > API /api/atlas/v2/entity/guid/ returned namespace entity json > with no relationship for namespace -> tables. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2559) HBase Atlas Hook doesn't create relationship between namespace and table
Ramesh Mani created ATLAS-2559: -- Summary: HBase Atlas Hook doesn't create relationship between namespace and table Key: ATLAS-2559 URL: https://issues.apache.org/jira/browse/ATLAS-2559 Project: Atlas Issue Type: Bug Components: atlas-intg Affects Versions: trunk Reporter: Ramesh Mani Fix For: trunk Atlas Entities created in HBase Atlas Hook doesn't have relationship between HBase Namespace and Tables. API /api/atlas/v2/entity/guid/ returned namespace entity json with no relationship for namespace -> table. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (ATLAS-2559) HBase Atlas Hook doesn't create relationship between namespace and table
[ https://issues.apache.org/jira/browse/ATLAS-2559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Mani reassigned ATLAS-2559: -- Assignee: Ramesh Mani > HBase Atlas Hook doesn't create relationship between namespace and table > > > Key: ATLAS-2559 > URL: https://issues.apache.org/jira/browse/ATLAS-2559 > Project: Atlas > Issue Type: Bug > Components: atlas-intg >Affects Versions: trunk >Reporter: Ramesh Mani >Assignee: Ramesh Mani >Priority: Major > Fix For: trunk > > > Atlas Entities created in HBase Atlas Hook doesn't have relationship between > HBase Namespace and Tables. > API /api/atlas/v2/entity/guid/ returned namespace entity json > with no relationship for namespace -> table. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2542) Import Hbase doesn't update entity already present in Atlas
[ https://issues.apache.org/jira/browse/ATLAS-2542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Mani updated ATLAS-2542: --- Attachment: 0001-ATLAS-2542-Import-Hbase-doesn-t-update-entity-alread.patch > Import Hbase doesn't update entity already present in Atlas > --- > > Key: ATLAS-2542 > URL: https://issues.apache.org/jira/browse/ATLAS-2542 > Project: Atlas > Issue Type: Bug > Components: atlas-intg >Affects Versions: trunk >Reporter: Ramesh Mani >Assignee: Ramesh Mani >Priority: Major > Fix For: trunk > > Attachments: > 0001-ATLAS-2542-Import-Hbase-doesn-t-update-entity-alread.patch > > > When import is done after adding a new column family to the table, the new > column family was not getting added to the existing HBase Table. Issue is > similar to what is happening in Hive BUG ATLAS-2535 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (ATLAS-2542) Import Hbase doesn't update entity already present in Atlas
[ https://issues.apache.org/jira/browse/ATLAS-2542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Mani reassigned ATLAS-2542: -- Assignee: Ramesh Mani > Import Hbase doesn't update entity already present in Atlas > --- > > Key: ATLAS-2542 > URL: https://issues.apache.org/jira/browse/ATLAS-2542 > Project: Atlas > Issue Type: Bug > Components: atlas-intg >Affects Versions: trunk >Reporter: Ramesh Mani >Assignee: Ramesh Mani >Priority: Major > Fix For: trunk > > > When import is done after adding a new column family to the table, the new > column family was not getting added to the existing HBase Table. Issue is > similar to what is happening in Hive BUG ATLAS-2535 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2542) Import Hbase doesn't update entity already present in Atlas
Ramesh Mani created ATLAS-2542: -- Summary: Import Hbase doesn't update entity already present in Atlas Key: ATLAS-2542 URL: https://issues.apache.org/jira/browse/ATLAS-2542 Project: Atlas Issue Type: Bug Components: atlas-intg Affects Versions: trunk Reporter: Ramesh Mani Fix For: trunk When import is done after adding a new column family to the table, the new column family was not getting added to the existing HBase Table. Issue is similar to what is happening in Hive BUG ATLAS-2535 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2535) Import hive script doesn't update entity already present in Atlas
Ramesh Mani created ATLAS-2535: -- Summary: Import hive script doesn't update entity already present in Atlas Key: ATLAS-2535 URL: https://issues.apache.org/jira/browse/ATLAS-2535 Project: Atlas Issue Type: Bug Components: atlas-intg Affects Versions: trunk Reporter: Ramesh Mani Fix For: trunk Import hive script doesn't update entity already present in Atlas On running Import hive script , entities which are already present in Atlas have an entity update but the entity is not updated. For example : >> create table emp(id int,name); Run import hive.sh >> alter table emp add column (dob date); Run import hive.sh Import hive script is successfully completed. But emp table entity in Atlas doesn't have the new column dob. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2525) Atlas Hbase/Hive hook improvement to provide import from file
[
https://issues.apache.org/jira/browse/ATLAS-2525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16423113#comment-16423113
]
Ramesh Mani commented on ATLAS-2525:
[~nixonrodrigues] I have fixed this in subsequent patch which I have created
review request.
Please check this out. Thanks.
https://reviews.apache.org/r/66393/
> Atlas Hbase/Hive hook improvement to provide import from file
> -
>
> Key: ATLAS-2525
> URL: https://issues.apache.org/jira/browse/ATLAS-2525
> Project: Atlas
> Issue Type: Bug
>Affects Versions: trunk, 0.8.2
>Reporter: Ramesh Mani
>Assignee: Ramesh Mani
>Priority: Major
> Fix For: trunk, 0.8.2
>
> Attachments:
> 0001-ATLAS-2525-Atlas-Hbase-Hive-hook-improvement-to-prov.patch
>
>
> Atlas Hbase/Hive hook improvement to provide import from file
> Hook script should have another option -f to accept a file which contains the
> database/table in hive or namespace/table in hbase and import it into Atlas
> HIVE CASE:
> import-hive.sh -f
> {code:java}
> import-hive.sh -f
> Imports all databases and tables in the file...
> Format:
> database1:tbl1
> database1:tbl2
> database2:tbl1
> {code}
> HBASE CASE:
> {code:java}
> import-hbase.sh -f
> namespace1:tbl1
> namespace1:tbl2
> namespace2:tbl1
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-2525) Atlas Hbase/Hive hook improvement to provide import from file
[
https://issues.apache.org/jira/browse/ATLAS-2525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramesh Mani updated ATLAS-2525:
---
Attachment: 0001-ATLAS-2525-Atlas-Hbase-Hive-hook-improvement-to-prov.patch
> Atlas Hbase/Hive hook improvement to provide import from file
> -
>
> Key: ATLAS-2525
> URL: https://issues.apache.org/jira/browse/ATLAS-2525
> Project: Atlas
> Issue Type: Bug
>Affects Versions: trunk, 0.8.2
>Reporter: Ramesh Mani
>Assignee: Ramesh Mani
>Priority: Major
> Fix For: trunk, 0.8.2
>
> Attachments:
> 0001-ATLAS-2525-Atlas-Hbase-Hive-hook-improvement-to-prov.patch
>
>
> Atlas Hbase/Hive hook improvement to provide import from file
> Hook script should have another option -f to accept a file which contains the
> database/table in hive or namespace/table in hbase and import it into Atlas
> HIVE CASE:
> import-hive.sh -f
> {code:java}
> import-hive.sh -f
> Imports all databases and tables in the file...
> Format:
> database1:tbl1
> database1:tbl2
> database2:tbl1
> {code}
> HBASE CASE:
> {code:java}
> import-hbase.sh -f
> namespace1:tbl1
> namespace1:tbl2
> namespace2:tbl1
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-2522) Improvement to HBase import script functionality
[ https://issues.apache.org/jira/browse/ATLAS-2522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Mani updated ATLAS-2522: --- Attachment: (was: 0001-ATLAS-2522-Improvement-to-HBase-import-script-functi.patch) > Improvement to HBase import script functionality > > > Key: ATLAS-2522 > URL: https://issues.apache.org/jira/browse/ATLAS-2522 > Project: Atlas > Issue Type: Bug > Components: atlas-intg >Affects Versions: trunk, 1.0.0 >Reporter: Ramesh Mani >Assignee: Ramesh Mani >Priority: Major > Fix For: 1.0.0 > > > Improvement to HBase import script functionality > 1) To Import Tables also when NameSpace alone is given as option > 2) Wildcard support in options. > 3) Uniform error reporting > 4) Should import even if the entity is already present in Atlas. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2525) Atlas Hbase/Hive hook improvement to provide import from file
[
https://issues.apache.org/jira/browse/ATLAS-2525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramesh Mani updated ATLAS-2525:
---
Description:
Atlas Hbase/Hive hook improvement to provide import from file
Hook script should have another option -f to accept a file which contains the
database/table in hive or namespace/table in hbase and import it into Atlas
HIVE CASE:
import-hive.sh -f
{code:java}
import-hive.sh -f
Imports all databases and tables in the file...
Format:
database1:tbl1
database1:tbl2
database2:tbl1
{code}
HBASE CASE:
{code:java}
import-hbase.sh -f
namespace1:tbl1
namespace1:tbl2
namespace2:tbl1
{code}
was:
Atlas Hbase/Hive hook improvement to provide import from file
Hook script should have another option -f to accept a file which contains the
database/table in hive or namespace/table in hbase and import it into Atlas
HIVE CASE:
import-hive.sh -f
{code:java}
import-hive.sh -f
Imports all databases and tables in the file...
Format:
database1:tbl1
database1:tbl2
database2:tbl1
{code}
HBASE CASE:
{code:java}
import-hbase.sh [-t ]
namespace1:tbl1
namespace1:tbl2
namespace2:tbl1
{code}
> Atlas Hbase/Hive hook improvement to provide import from file
> -
>
> Key: ATLAS-2525
> URL: https://issues.apache.org/jira/browse/ATLAS-2525
> Project: Atlas
> Issue Type: Bug
>Affects Versions: trunk, 0.8.2
>Reporter: Ramesh Mani
>Assignee: Ramesh Mani
>Priority: Major
> Fix For: trunk, 0.8.2
>
>
> Atlas Hbase/Hive hook improvement to provide import from file
> Hook script should have another option -f to accept a file which contains the
> database/table in hive or namespace/table in hbase and import it into Atlas
> HIVE CASE:
> import-hive.sh -f
> {code:java}
> import-hive.sh -f
> Imports all databases and tables in the file...
> Format:
> database1:tbl1
> database1:tbl2
> database2:tbl1
> {code}
> HBASE CASE:
> {code:java}
> import-hbase.sh -f
> namespace1:tbl1
> namespace1:tbl2
> namespace2:tbl1
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-2525) Atlas Hbase/Hive hook improvement to provide import from file
[
https://issues.apache.org/jira/browse/ATLAS-2525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramesh Mani updated ATLAS-2525:
---
Attachment: (was:
0001-ATLAS-2525-Atlas-Hbase-Hive-hook-improvement-to-prov.patch)
> Atlas Hbase/Hive hook improvement to provide import from file
> -
>
> Key: ATLAS-2525
> URL: https://issues.apache.org/jira/browse/ATLAS-2525
> Project: Atlas
> Issue Type: Bug
>Affects Versions: trunk, 0.8.2
>Reporter: Ramesh Mani
>Assignee: Ramesh Mani
>Priority: Major
> Fix For: trunk, 0.8.2
>
>
> Atlas Hbase/Hive hook improvement to provide import from file
> Hook script should have another option -f to accept a file which contains the
> database/table in hive or namespace/table in hbase and import it into Atlas
> HIVE CASE:
> import-hive.sh -f
> {code:java}
> import-hive.sh -f
> Imports all databases and tables in the file...
> Format:
> database1:tbl1
> database1:tbl2
> database2:tbl1
> {code}
> HBASE CASE:
> {code:java}
> import-hbase.sh [-t ]
> namespace1:tbl1
> namespace1:tbl2
> namespace2:tbl1
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-2525) Atlas Hbase/Hive hook improvement to provide import from file
[
https://issues.apache.org/jira/browse/ATLAS-2525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramesh Mani updated ATLAS-2525:
---
Description:
Atlas Hbase/Hive hook improvement to provide import from file
Hook script should have another option -f to accept a file which contains the
database/table in hive or namespace/table in hbase and import it into Atlas
HIVE CASE:
import-hive.sh -f
{code:java}
import-hive.sh -f
Imports all databases and tables in the file...
Format:
database1:tbl1
database1:tbl2
database2:tbl1
{code}
HBASE CASE:
{code:java}
import-hbase.sh [-t ]
namespace1:tbl1
namespace1:tbl2
namespace2:tbl1
{code}
was:
Atlas Hbase/Hive hook improvement to provide import from file
Hook script should have another option -f to accept a file which contains the
database/table in hive or namespace/table in hbase and import it into Atlas
Format can be JSON or CSV.
HIVE CASE:
import-hive.sh -f : This can be JSON or CSV file
{code:java}
import-hive.sh -f : This can be JSON or CSV file
Imports all databases and tables in the file...
cvs format:
database1,tbl1,tbl2,tbl3,..
database2,tbl1,tbl2,tbl3,..
JSON format:
{
"database1" :["tbl1","tbl2","tbl3",..]
"database2" :["tbl1","tbl2","tbl3",..]
}{code}
JSON format:
{ "namespace1" :["tbl1","tbl2","tbl3",..] "namespace2"
:["tbl1","tbl2","tbl3",..] }
HBASE CASE:
{code:java}
import-hbase.sh [-t ] : This can be JSON or CSV file
cvs format:
namespace1,tbl1,tbl2,tbl3,..
namespace2,tbl1,tbl2,tbl3,..
JSON format:
{
"namespace1" :["tbl1","tbl2","tbl3",..]
"namespace2" :["tbl1","tbl2","tbl3",..]
}
{code:java}
{code}
> Atlas Hbase/Hive hook improvement to provide import from file
> -
>
> Key: ATLAS-2525
> URL: https://issues.apache.org/jira/browse/ATLAS-2525
> Project: Atlas
> Issue Type: Bug
>Affects Versions: trunk, 0.8.2
>Reporter: Ramesh Mani
>Assignee: Ramesh Mani
>Priority: Major
> Fix For: trunk, 0.8.2
>
>
> Atlas Hbase/Hive hook improvement to provide import from file
> Hook script should have another option -f to accept a file which contains the
> database/table in hive or namespace/table in hbase and import it into Atlas
> HIVE CASE:
> import-hive.sh -f
> {code:java}
> import-hive.sh -f
> Imports all databases and tables in the file...
> Format:
> database1:tbl1
> database1:tbl2
> database2:tbl1
> {code}
> HBASE CASE:
> {code:java}
> import-hbase.sh [-t ]
> namespace1:tbl1
> namespace1:tbl2
> namespace2:tbl1
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-2525) Atlas Hbase/Hive hook improvement to provide import from file
[
https://issues.apache.org/jira/browse/ATLAS-2525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramesh Mani updated ATLAS-2525:
---
Description:
Atlas Hbase/Hive hook improvement to provide import from file
Hook script should have another option -f to accept a file which contains the
database/table in hive or namespace/table in hbase and import it into Atlas
Format can be JSON or CSV.
HIVE CASE:
import-hive.sh -f : This can be JSON or CSV file
{code:java}
import-hive.sh -f : This can be JSON or CSV file
Imports all databases and tables in the file...
cvs format:
database1,tbl1,tbl2,tbl3,..
database2,tbl1,tbl2,tbl3,..
JSON format:
{
"database1" :["tbl1","tbl2","tbl3",..]
"database2" :["tbl1","tbl2","tbl3",..]
}{code}
JSON format:
{ "namespace1" :["tbl1","tbl2","tbl3",..] "namespace2"
:["tbl1","tbl2","tbl3",..] }
HBASE CASE:
{code:java}
import-hbase.sh [-t ] : This can be JSON or CSV file
cvs format:
namespace1,tbl1,tbl2,tbl3,..
namespace2,tbl1,tbl2,tbl3,..
JSON format:
{
"namespace1" :["tbl1","tbl2","tbl3",..]
"namespace2" :["tbl1","tbl2","tbl3",..]
}
{code:java}
{code}
was:
Atlas Hbase/Hive hook improvement to provide import from file
Hook script should have another option -f to accept a file which contains the
database/table in hive or namespace/table in hbase and import it into Atlas
Format can be JSON or CSV.
HIVE CASE:
import-hive.sh -f : This can be JSON or CSV file
{code:java}
{code:java}
import-hive.sh -f : This can be JSON or CSV file
Imports all databases and tables in the file...
cvs format:
database1,tbl1,tbl2,tbl3,..
database2,tbl1,tbl2,tbl3,..
JSON format:
{
"database1" :["tbl1","tbl2","tbl3",..]
"database2" :["tbl1","tbl2","tbl3",..]
}{code}
JSON format:
{ "namespace1" :["tbl1","tbl2","tbl3",..] "namespace2"
:["tbl1","tbl2","tbl3",..] }
HBASE CASE:
{code:java}
import-hbase.sh [-t ] : This can be JSON or CSV file
cvs format:
namespace1,tbl1,tbl2,tbl3,..
namespace2,tbl1,tbl2,tbl3,..
JSON format:
{
"namespace1" :["tbl1","tbl2","tbl3",..]
"namespace2" :["tbl1","tbl2","tbl3",..]
}
{code:java}
{code}
> Atlas Hbase/Hive hook improvement to provide import from file
> -
>
> Key: ATLAS-2525
> URL: https://issues.apache.org/jira/browse/ATLAS-2525
> Project: Atlas
> Issue Type: Bug
>Affects Versions: trunk, 0.8.2
>Reporter: Ramesh Mani
>Assignee: Ramesh Mani
>Priority: Major
> Fix For: trunk, 0.8.2
>
> Attachments:
> 0001-ATLAS-2525-Atlas-Hbase-Hive-hook-improvement-to-prov.patch
>
>
> Atlas Hbase/Hive hook improvement to provide import from file
> Hook script should have another option -f to accept a file which contains the
> database/table in hive or namespace/table in hbase and import it into Atlas
> Format can be JSON or CSV.
> HIVE CASE:
> import-hive.sh -f : This can be JSON or CSV file
> {code:java}
> import-hive.sh -f : This can be JSON or CSV file
> Imports all databases and tables in the file...
> cvs format:
> database1,tbl1,tbl2,tbl3,..
> database2,tbl1,tbl2,tbl3,..
> JSON format:
> {
> "database1" :["tbl1","tbl2","tbl3",..]
> "database2" :["tbl1","tbl2","tbl3",..]
> }{code}
> JSON format:
> { "namespace1" :["tbl1","tbl2","tbl3",..] "namespace2"
> :["tbl1","tbl2","tbl3",..] }
> HBASE CASE:
> {code:java}
> import-hbase.sh [-t ] : This can be JSON or CSV file
> cvs format:
> namespace1,tbl1,tbl2,tbl3,..
> namespace2,tbl1,tbl2,tbl3,..
> JSON format:
> {
> "namespace1" :["tbl1","tbl2","tbl3",..]
> "namespace2" :["tbl1","tbl2","tbl3",..]
> }
> {code:java}
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-2525) Atlas Hbase/Hive hook improvement to provide import from file
[
https://issues.apache.org/jira/browse/ATLAS-2525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramesh Mani updated ATLAS-2525:
---
Description:
Atlas Hbase/Hive hook improvement to provide import from file
Hook script should have another option -f to accept a file which contains the
database/table in hive or namespace/table in hbase and import it into Atlas
Format can be JSON or CSV.
HIVE CASE:
import-hive.sh -f : This can be JSON or CSV file
{code:java}
{code:java}
import-hive.sh -f : This can be JSON or CSV file
Imports all databases and tables in the file...
cvs format:
database1,tbl1,tbl2,tbl3,..
database2,tbl1,tbl2,tbl3,..
JSON format:
{
"database1" :["tbl1","tbl2","tbl3",..]
"database2" :["tbl1","tbl2","tbl3",..]
}{code}
JSON format:
{ "namespace1" :["tbl1","tbl2","tbl3",..] "namespace2"
:["tbl1","tbl2","tbl3",..] }
HBASE CASE:
{code:java}
import-hbase.sh [-t ] : This can be JSON or CSV file
cvs format:
namespace1,tbl1,tbl2,tbl3,..
namespace2,tbl1,tbl2,tbl3,..
JSON format:
{
"namespace1" :["tbl1","tbl2","tbl3",..]
"namespace2" :["tbl1","tbl2","tbl3",..]
}
{code:java}
{code}
was:
Atlas Hbase/Hive hook improvement to provide import from file
Hook script should have another option -f to accept a file which contains the
database/table in hive or namespace/table in hbase and import it into Atlas
Format can be JSON or CSV.
HIVE CASE:
import-hive.sh -f : This can be JSON or CSV file Imports all
databases and tables in the file... cvs format: namespace1,tbl1,tbl2,tbl3,..
namespace2,tbl1,tbl2,tbl3,..
{code:java}
{code:java}
import-hive.sh -f : This can be JSON or CSV file
Imports all databases and tables in the file...
cvs format:
database1,tbl1,tbl2,tbl3,..
database2,tbl1,tbl2,tbl3,..
JSON format:
{
"database1" :["tbl1","tbl2","tbl3",..]
"database2" :["tbl1","tbl2","tbl3",..]
}{code}
JSON format:
{ "namespace1" :["tbl1","tbl2","tbl3",..] "namespace2"
:["tbl1","tbl2","tbl3",..] }
HBASE CASE:
{code:java}
import-hbase.sh [-t ] : This can be JSON or CSV file
cvs format:
namespace1,tbl1,tbl2,tbl3,..
namespace2,tbl1,tbl2,tbl3,..
JSON format:
{
"namespace1" :["tbl1","tbl2","tbl3",..]
"namespace2" :["tbl1","tbl2","tbl3",..]
}
{code:java}
{code}
> Atlas Hbase/Hive hook improvement to provide import from file
> -
>
> Key: ATLAS-2525
> URL: https://issues.apache.org/jira/browse/ATLAS-2525
> Project: Atlas
> Issue Type: Bug
>Affects Versions: trunk, 0.8.2
>Reporter: Ramesh Mani
>Assignee: Ramesh Mani
>Priority: Major
> Fix For: trunk, 0.8.2
>
> Attachments:
> 0001-ATLAS-2525-Atlas-Hbase-Hive-hook-improvement-to-prov.patch
>
>
> Atlas Hbase/Hive hook improvement to provide import from file
> Hook script should have another option -f to accept a file which contains the
> database/table in hive or namespace/table in hbase and import it into Atlas
> Format can be JSON or CSV.
> HIVE CASE:
> import-hive.sh -f : This can be JSON or CSV file
> {code:java}
> {code:java}
> import-hive.sh -f : This can be JSON or CSV file
> Imports all databases and tables in the file...
> cvs format:
> database1,tbl1,tbl2,tbl3,..
> database2,tbl1,tbl2,tbl3,..
> JSON format:
> {
> "database1" :["tbl1","tbl2","tbl3",..]
> "database2" :["tbl1","tbl2","tbl3",..]
> }{code}
> JSON format:
> { "namespace1" :["tbl1","tbl2","tbl3",..] "namespace2"
> :["tbl1","tbl2","tbl3",..] }
> HBASE CASE:
> {code:java}
> import-hbase.sh [-t ] : This can be JSON or CSV file
> cvs format:
> namespace1,tbl1,tbl2,tbl3,..
> namespace2,tbl1,tbl2,tbl3,..
> JSON format:
> {
> "namespace1" :["tbl1","tbl2","tbl3",..]
> "namespace2" :["tbl1","tbl2","tbl3",..]
> }
> {code:java}
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-2525) Atlas Hbase/Hive hook improvement to provide import from file
[
https://issues.apache.org/jira/browse/ATLAS-2525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramesh Mani updated ATLAS-2525:
---
Attachment: (was:
0001-ATLAS-2525-Atlas-Hbase-Hive-hook-improvement-to-prov.patch)
> Atlas Hbase/Hive hook improvement to provide import from file
> -
>
> Key: ATLAS-2525
> URL: https://issues.apache.org/jira/browse/ATLAS-2525
> Project: Atlas
> Issue Type: Bug
>Affects Versions: trunk, 0.8.2
>Reporter: Ramesh Mani
>Assignee: Ramesh Mani
>Priority: Major
> Fix For: trunk, 0.8.2
>
> Attachments:
> 0001-ATLAS-2525-Atlas-Hbase-Hive-hook-improvement-to-prov.patch
>
>
> Atlas Hbase/Hive hook improvement to provide import from file
> Hook script should have another option -f to accept a file which contains the
> database/table in hive or namespace/table in hbase and import it into Atlas
> Format can be JSON or CSV.
> HIVE CASE:
> import-hive.sh -f : This can be JSON or CSV file Imports all
> databases and tables in the file... cvs format: namespace1,tbl1,tbl2,tbl3,..
> namespace2,tbl1,tbl2,tbl3,..
> {code:java}
> {code:java}
> import-hive.sh -f : This can be JSON or CSV file
> Imports all databases and tables in the file...
> cvs format:
> database1,tbl1,tbl2,tbl3,..
> database2,tbl1,tbl2,tbl3,..
> JSON format:
> {
> "database1" :["tbl1","tbl2","tbl3",..]
> "database2" :["tbl1","tbl2","tbl3",..]
> }{code}
> JSON format:
> { "namespace1" :["tbl1","tbl2","tbl3",..] "namespace2"
> :["tbl1","tbl2","tbl3",..] }
> HBASE CASE:
> {code:java}
> import-hbase.sh [-t ] : This can be JSON or CSV file
> cvs format:
> namespace1,tbl1,tbl2,tbl3,..
> namespace2,tbl1,tbl2,tbl3,..
> JSON format:
> {
> "namespace1" :["tbl1","tbl2","tbl3",..]
> "namespace2" :["tbl1","tbl2","tbl3",..]
> }
> {code:java}
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-2525) Atlas Hbase/Hive hook improvement to provide import from file
[
https://issues.apache.org/jira/browse/ATLAS-2525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramesh Mani updated ATLAS-2525:
---
Attachment: 0001-ATLAS-2525-Atlas-Hbase-Hive-hook-improvement-to-prov.patch
> Atlas Hbase/Hive hook improvement to provide import from file
> -
>
> Key: ATLAS-2525
> URL: https://issues.apache.org/jira/browse/ATLAS-2525
> Project: Atlas
> Issue Type: Bug
>Affects Versions: trunk, 0.8.2
>Reporter: Ramesh Mani
>Assignee: Ramesh Mani
>Priority: Major
> Fix For: trunk, 0.8.2
>
> Attachments:
> 0001-ATLAS-2525-Atlas-Hbase-Hive-hook-improvement-to-prov.patch,
> 0001-ATLAS-2525-Atlas-Hbase-Hive-hook-improvement-to-prov.patch
>
>
> Atlas Hbase/Hive hook improvement to provide import from file
> Hook script should have another option -f to accept a file which contains the
> database/table in hive or namespace/table in hbase and import it into Atlas
> Format can be JSON or CSV.
> HIVE CASE:
> import-hive.sh -f : This can be JSON or CSV file Imports all
> databases and tables in the file... cvs format: namespace1,tbl1,tbl2,tbl3,..
> namespace2,tbl1,tbl2,tbl3,..
> {code:java}
> {code:java}
> import-hive.sh -f : This can be JSON or CSV file
> Imports all databases and tables in the file...
> cvs format:
> database1,tbl1,tbl2,tbl3,..
> database2,tbl1,tbl2,tbl3,..
> JSON format:
> {
> "database1" :["tbl1","tbl2","tbl3",..]
> "database2" :["tbl1","tbl2","tbl3",..]
> }{code}
> JSON format:
> { "namespace1" :["tbl1","tbl2","tbl3",..] "namespace2"
> :["tbl1","tbl2","tbl3",..] }
> HBASE CASE:
> {code:java}
> import-hbase.sh [-t ] : This can be JSON or CSV file
> cvs format:
> namespace1,tbl1,tbl2,tbl3,..
> namespace2,tbl1,tbl2,tbl3,..
> JSON format:
> {
> "namespace1" :["tbl1","tbl2","tbl3",..]
> "namespace2" :["tbl1","tbl2","tbl3",..]
> }
> {code:java}
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-2525) Atlas Hbase/Hive hook improvement to provide import from file
[
https://issues.apache.org/jira/browse/ATLAS-2525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramesh Mani updated ATLAS-2525:
---
Attachment: 0001-ATLAS-2525-Atlas-Hbase-Hive-hook-improvement-to-prov.patch
> Atlas Hbase/Hive hook improvement to provide import from file
> -
>
> Key: ATLAS-2525
> URL: https://issues.apache.org/jira/browse/ATLAS-2525
> Project: Atlas
> Issue Type: Bug
>Affects Versions: trunk, 0.8.2
>Reporter: Ramesh Mani
>Assignee: Ramesh Mani
>Priority: Major
> Fix For: trunk, 0.8.2
>
> Attachments:
> 0001-ATLAS-2525-Atlas-Hbase-Hive-hook-improvement-to-prov.patch
>
>
> Atlas Hbase/Hive hook improvement to provide import from file
> Hook script should have another option -f to accept a file which contains the
> database/table in hive or namespace/table in hbase and import it into Atlas
> Format can be JSON or CSV.
> HIVE CASE:
> import-hive.sh -f : This can be JSON or CSV file Imports all
> databases and tables in the file... cvs format: namespace1,tbl1,tbl2,tbl3,..
> namespace2,tbl1,tbl2,tbl3,..
> {code:java}
> {code:java}
> import-hive.sh -f : This can be JSON or CSV file
> Imports all databases and tables in the file...
> cvs format:
> database1,tbl1,tbl2,tbl3,..
> database2,tbl1,tbl2,tbl3,..
> JSON format:
> {
> "database1" :["tbl1","tbl2","tbl3",..]
> "database2" :["tbl1","tbl2","tbl3",..]
> }{code}
> JSON format:
> { "namespace1" :["tbl1","tbl2","tbl3",..] "namespace2"
> :["tbl1","tbl2","tbl3",..] }
> HBASE CASE:
> {code:java}
> import-hbase.sh [-t ] : This can be JSON or CSV file
> cvs format:
> namespace1,tbl1,tbl2,tbl3,..
> namespace2,tbl1,tbl2,tbl3,..
> JSON format:
> {
> "namespace1" :["tbl1","tbl2","tbl3",..]
> "namespace2" :["tbl1","tbl2","tbl3",..]
> }
> {code:java}
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-2525) Atlas Hbase/Hive hook improvement to provide import from file
[
https://issues.apache.org/jira/browse/ATLAS-2525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramesh Mani updated ATLAS-2525:
---
Affects Version/s: trunk
0.8.2
> Atlas Hbase/Hive hook improvement to provide import from file
> -
>
> Key: ATLAS-2525
> URL: https://issues.apache.org/jira/browse/ATLAS-2525
> Project: Atlas
> Issue Type: Bug
>Affects Versions: trunk, 0.8.2
>Reporter: Ramesh Mani
>Assignee: Ramesh Mani
>Priority: Major
> Fix For: trunk, 0.8.2
>
>
> Atlas Hbase/Hive hook improvement to provide import from file
> Hook script should have another option -f to accept a file which contains the
> database/table in hive or namespace/table in hbase and import it into Atlas
> Format can be JSON or CSV.
> HIVE CASE:
> import-hive.sh -f : This can be JSON or CSV file Imports all
> databases and tables in the file... cvs format: namespace1,tbl1,tbl2,tbl3,..
> namespace2,tbl1,tbl2,tbl3,..
> {code:java}
> {code:java}
> import-hive.sh -f : This can be JSON or CSV file
> Imports all databases and tables in the file...
> cvs format:
> database1,tbl1,tbl2,tbl3,..
> database2,tbl1,tbl2,tbl3,..
> JSON format:
> {
> "database1" :["tbl1","tbl2","tbl3",..]
> "database2" :["tbl1","tbl2","tbl3",..]
> }{code}
> JSON format:
> { "namespace1" :["tbl1","tbl2","tbl3",..] "namespace2"
> :["tbl1","tbl2","tbl3",..] }
> HBASE CASE:
> {code:java}
> import-hbase.sh [-t ] : This can be JSON or CSV file
> cvs format:
> namespace1,tbl1,tbl2,tbl3,..
> namespace2,tbl1,tbl2,tbl3,..
> JSON format:
> {
> "namespace1" :["tbl1","tbl2","tbl3",..]
> "namespace2" :["tbl1","tbl2","tbl3",..]
> }
> {code:java}
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-2525) Atlas Hbase/Hive hook improvement to provide import from file
[
https://issues.apache.org/jira/browse/ATLAS-2525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramesh Mani updated ATLAS-2525:
---
Fix Version/s: 0.8.2
trunk
> Atlas Hbase/Hive hook improvement to provide import from file
> -
>
> Key: ATLAS-2525
> URL: https://issues.apache.org/jira/browse/ATLAS-2525
> Project: Atlas
> Issue Type: Bug
>Affects Versions: trunk, 0.8.2
>Reporter: Ramesh Mani
>Assignee: Ramesh Mani
>Priority: Major
> Fix For: trunk, 0.8.2
>
>
> Atlas Hbase/Hive hook improvement to provide import from file
> Hook script should have another option -f to accept a file which contains the
> database/table in hive or namespace/table in hbase and import it into Atlas
> Format can be JSON or CSV.
> HIVE CASE:
> import-hive.sh -f : This can be JSON or CSV file Imports all
> databases and tables in the file... cvs format: namespace1,tbl1,tbl2,tbl3,..
> namespace2,tbl1,tbl2,tbl3,..
> {code:java}
> {code:java}
> import-hive.sh -f : This can be JSON or CSV file
> Imports all databases and tables in the file...
> cvs format:
> database1,tbl1,tbl2,tbl3,..
> database2,tbl1,tbl2,tbl3,..
> JSON format:
> {
> "database1" :["tbl1","tbl2","tbl3",..]
> "database2" :["tbl1","tbl2","tbl3",..]
> }{code}
> JSON format:
> { "namespace1" :["tbl1","tbl2","tbl3",..] "namespace2"
> :["tbl1","tbl2","tbl3",..] }
> HBASE CASE:
> {code:java}
> import-hbase.sh [-t ] : This can be JSON or CSV file
> cvs format:
> namespace1,tbl1,tbl2,tbl3,..
> namespace2,tbl1,tbl2,tbl3,..
> JSON format:
> {
> "namespace1" :["tbl1","tbl2","tbl3",..]
> "namespace2" :["tbl1","tbl2","tbl3",..]
> }
> {code:java}
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-2525) Atlas Hbase/Hive hook improvement to provide import from file
[
https://issues.apache.org/jira/browse/ATLAS-2525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramesh Mani updated ATLAS-2525:
---
Description:
Atlas Hbase/Hive hook improvement to provide import from file
Hook script should have another option -f to accept a file which contains the
database/table in hive or namespace/table in hbase and import it into Atlas
Format can be JSON or CSV.
HIVE CASE:
import-hive.sh -f : This can be JSON or CSV file Imports all
databases and tables in the file... cvs format: namespace1,tbl1,tbl2,tbl3,..
namespace2,tbl1,tbl2,tbl3,..
{code:java}
{code:java}
import-hive.sh -f : This can be JSON or CSV file
Imports all databases and tables in the file...
cvs format:
database1,tbl1,tbl2,tbl3,..
database2,tbl1,tbl2,tbl3,..
JSON format:
{
"database1" :["tbl1","tbl2","tbl3",..]
"database2" :["tbl1","tbl2","tbl3",..]
}{code}
JSON format:
{ "namespace1" :["tbl1","tbl2","tbl3",..] "namespace2"
:["tbl1","tbl2","tbl3",..] }
HBASE CASE:
{code:java}
import-hbase.sh [-t ] : This can be JSON or CSV file
cvs format:
namespace1,tbl1,tbl2,tbl3,..
namespace2,tbl1,tbl2,tbl3,..
JSON format:
{
"namespace1" :["tbl1","tbl2","tbl3",..]
"namespace2" :["tbl1","tbl2","tbl3",..]
}
{code:java}
{code}
was:
Atlas Hbase/Hive hook improvement to provide import from file
Hook script should have another option -f to accept a file which contains the
database/table in hive or namespace/table in hbase and import it into Atlas
Format can be JSON or CSV.
HIVE CASE:
import-hive.sh -f : This can be JSON or CSV file
Imports all databases and tables in the file...
cvs format:
namespace1,tbl1,tbl2,tbl3,..
namespace2,tbl1,tbl2,tbl3,..
JSON format:
{
"namespace1" :["tbl1","tbl2","tbl3",..]
"namespace2" :["tbl1","tbl2","tbl3",..]
}
HBASE CASE:
{code:java}
Usage 2: import-hbase.sh [-t ] : This can be JSON or CSV file
cvs format:
namespace1,tbl1,tbl2,tbl3,..
namespace2,tbl1,tbl2,tbl3,..
JSON format:
{
"namespace1" :["tbl1","tbl2","tbl3",..]
"namespace2" :["tbl1","tbl2","tbl3",..]
}
{code:java}
{code}
> Atlas Hbase/Hive hook improvement to provide import from file
> -
>
> Key: ATLAS-2525
> URL: https://issues.apache.org/jira/browse/ATLAS-2525
> Project: Atlas
> Issue Type: Bug
>Reporter: Ramesh Mani
>Priority: Major
>
> Atlas Hbase/Hive hook improvement to provide import from file
> Hook script should have another option -f to accept a file which contains the
> database/table in hive or namespace/table in hbase and import it into Atlas
> Format can be JSON or CSV.
> HIVE CASE:
> import-hive.sh -f : This can be JSON or CSV file Imports all
> databases and tables in the file... cvs format: namespace1,tbl1,tbl2,tbl3,..
> namespace2,tbl1,tbl2,tbl3,..
> {code:java}
> {code:java}
> import-hive.sh -f : This can be JSON or CSV file
> Imports all databases and tables in the file...
> cvs format:
> database1,tbl1,tbl2,tbl3,..
> database2,tbl1,tbl2,tbl3,..
> JSON format:
> {
> "database1" :["tbl1","tbl2","tbl3",..]
> "database2" :["tbl1","tbl2","tbl3",..]
> }{code}
> JSON format:
> { "namespace1" :["tbl1","tbl2","tbl3",..] "namespace2"
> :["tbl1","tbl2","tbl3",..] }
> HBASE CASE:
> {code:java}
> import-hbase.sh [-t ] : This can be JSON or CSV file
> cvs format:
> namespace1,tbl1,tbl2,tbl3,..
> namespace2,tbl1,tbl2,tbl3,..
> JSON format:
> {
> "namespace1" :["tbl1","tbl2","tbl3",..]
> "namespace2" :["tbl1","tbl2","tbl3",..]
> }
> {code:java}
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (ATLAS-2525) Atlas Hbase/Hive hook improvement to provide import from file
[
https://issues.apache.org/jira/browse/ATLAS-2525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramesh Mani reassigned ATLAS-2525:
--
Assignee: Ramesh Mani
> Atlas Hbase/Hive hook improvement to provide import from file
> -
>
> Key: ATLAS-2525
> URL: https://issues.apache.org/jira/browse/ATLAS-2525
> Project: Atlas
> Issue Type: Bug
>Reporter: Ramesh Mani
>Assignee: Ramesh Mani
>Priority: Major
>
> Atlas Hbase/Hive hook improvement to provide import from file
> Hook script should have another option -f to accept a file which contains the
> database/table in hive or namespace/table in hbase and import it into Atlas
> Format can be JSON or CSV.
> HIVE CASE:
> import-hive.sh -f : This can be JSON or CSV file Imports all
> databases and tables in the file... cvs format: namespace1,tbl1,tbl2,tbl3,..
> namespace2,tbl1,tbl2,tbl3,..
> {code:java}
> {code:java}
> import-hive.sh -f : This can be JSON or CSV file
> Imports all databases and tables in the file...
> cvs format:
> database1,tbl1,tbl2,tbl3,..
> database2,tbl1,tbl2,tbl3,..
> JSON format:
> {
> "database1" :["tbl1","tbl2","tbl3",..]
> "database2" :["tbl1","tbl2","tbl3",..]
> }{code}
> JSON format:
> { "namespace1" :["tbl1","tbl2","tbl3",..] "namespace2"
> :["tbl1","tbl2","tbl3",..] }
> HBASE CASE:
> {code:java}
> import-hbase.sh [-t ] : This can be JSON or CSV file
> cvs format:
> namespace1,tbl1,tbl2,tbl3,..
> namespace2,tbl1,tbl2,tbl3,..
> JSON format:
> {
> "namespace1" :["tbl1","tbl2","tbl3",..]
> "namespace2" :["tbl1","tbl2","tbl3",..]
> }
> {code:java}
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
