Ability to more precisely control placement of Hive tables.

Description

Currently, Kylo stores feed results in Hive tables where the database name is determined by the category assigned to the feed. This includes target tables as well as work tables.

A customer would like to have the ability to more precisely control the placement of tables in Hive. Specifically, they would like to be able override the default database name in Hive with another existing Hive database for target tables. They would also like the capability to designate a separate existing Hive database for work tables.

From a business perspective, this will allow the customer to publish target tables separately from work tables with a separate level of security, and it would allow feeds to place tables in already existing databases or applications without the need for databases to have a one to one correspondence to Kylo categories.

Activity

Show:
Mike Martin
March 2, 2018, 1:43 PM

Thanks Sean. That was one of my first JIRA’s and I didn’t think about not including the customer. I actually entered two yesterday, 1733 and 1734. I went back and made sure there are no customer references in either one.

Mike Martin

Michael W. Martin, Ph.D.
Enterprise Data Architect
Think Big, a Teradata Company
910-200-2210
mike.martin@thinkbiganalytics.com<mike.martin@thinkbiganalytics.com>
thinkbiganalytics.com<http://www.teradata.com/>

This e-mail is from Teradata Corporation and may contain information that is confidential or proprietary. If you are not the intended recipient, do not read, copy or distribute the e-mail or any attachments. Instead, please notify the sender and delete the e-mail and any attachments. Thank you.
Please consider the environment before printing.

From: "Sean Felten (Jira)" <jira@kylo-io.atlassian.net>
Date: Friday, March 2, 2018 at 3:14 AM
To: Mike Martin <Mike.Martin@Thinkbiganalytics.com>
Subject: [JIRA] () Ability to more precisely control placement of Hive tables.

[mage removed by sender.]

Sean Felten<https://kylo-io.atlassian.net/secure/ViewProfile.jspa?name=sfelten> updated an issue

Kylo<https://kylo-io.atlassian.net/browse/KYLO> / [tory] <https://kylo-io.atlassian.net/browse/KYLO-1734> KYLO-1734<https://kylo-io.atlassian.net/browse/KYLO-1734>

Ability to more precisely control placement of Hive tables.<https://kylo-io.atlassian.net/browse/KYLO-1734>

Change By:

Sean Felten<https://kylo-io.atlassian.net/secure/ViewProfile.jspa?name=sfelten>

Currently, Kylo stores feed results in Hive tables where the database name is determined by the category assigned to the feed. This includes target tables as well as work tables.

A customer would like to have the ability to more precisely control the placement of tables in Hive. Specifically, they would like to be able override the default database name in Hive with another existing Hive database for target tables. They would also like the capability to designate a separate existing Hive database for work tables.

From a business perspective, this will allow BNSF the customer to publish target tables separately from work tables with a separate level of security, and it would allow feeds to place tables in already existing databases or applications without the need for databases to have a one to one correspondence to Kylo categories.

[dd Comment]<https://kylo-io.atlassian.net/browse/KYLO-1734#add-comment>

Add Comment<https://kylo-io.atlassian.net/browse/KYLO-1734#add-comment>

Get Jira notifications on your phone! Download the Jira Cloud app for Android<https://play.google.com/store/apps/details?id=com.atlassian.android.jira.core&referrer=utm_source%3DNotificationLink%26utm_medium%3DEmail> or iOS<https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailNotificationLink&mt=8>

Assignee

Unassigned

Reporter

Mike Martin

Labels

None

Reviewer

None

Priority

Medium
Configure