You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lens.apache.org by "Amareshwari Sriramadasu (JIRA)" <ji...@apache.org> on 2015/02/23 09:23:11 UTC

[jira] [Commented] (LENS-340) Using existing storage tables to create facts and dimensions

    [ https://issues.apache.org/jira/browse/LENS-340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14333093#comment-14333093 ] 

Amareshwari Sriramadasu commented on LENS-340:
----------------------------------------------

Accepting an existing name for the storage table should not be major change. 

But accepting existing partitions in the table will be a major issue - because Lens understands some partitions are time partitions and the format for the time partition strings are as per https://github.com/apache/incubator-lens/blob/master/lens-cube/src/main/java/org/apache/lens/cube/metadata/UpdatePeriod.java 

And add/drop partitions should be done through LensServer to understand the availability of time partitions and understanding partitions stats like first partition, last partition and etc.

> Using existing storage tables to create facts and dimensions
> ------------------------------------------------------------
>
>                 Key: LENS-340
>                 URL: https://issues.apache.org/jira/browse/LENS-340
>             Project: Apache Lens
>          Issue Type: New Feature
>            Reporter: Sharad Agarwal
>
> Currently the storage tables need to be created as part of defining facts and dimensions. This is limiting in behaviour.
> For certain cases, storage tables may be pre existing. Data pipelines may be creating and populating storage tables. There should be a way to create facts/dimensions on top of the existing storage tables.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)