phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chinmay Kulkarni (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-3955) Ensure KEEP_DELETED_CELLS, REPLICATION_SCOPE, and TTL properties stay in sync between the physical data table and index tables
Date Tue, 15 May 2018 21:48:00 GMT

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

Chinmay Kulkarni commented on PHOENIX-3955:
-------------------------------------------

Why do we allow to set different values for KEEP_DELETED_CELLS and REPLICATION_SCOPE across
different column families, but not allow each CF to have its own TTL? I don't understand the
use-case for this. Can we enforce all 3 properties to be the same for all CFs for a table?
We can disallow users to create indexes with their own values for these properties and force
the indexes to have the same value as other CFs of the data table.

Accordingly, we should disallow "ALTER TABLE" to change these 3 properties for specific CFs
and instead apply the modified property to all CFs of the data table and all indexes as well.
What say [~jamestaylor], [~tdsilva]?

> Ensure KEEP_DELETED_CELLS, REPLICATION_SCOPE, and TTL properties stay in sync between
the physical data table and index tables
> ------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: PHOENIX-3955
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-3955
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Samarth Jain
>            Assignee: Chinmay Kulkarni
>            Priority: Major
>
> We need to make sure that indexes inherit the REPLICATION_SCOPE, KEEP_DELETED_CELLS and
TTL properties from the base table. Otherwise we can run into situations where the data was
removed (or not removed) from the data table but was removed (or not removed) from the index.
Or vice-versa. We also need to make sure that any ALTER TABLE SET TTL or ALTER TABLE SET KEEP_DELETED_CELLS
statements propagate the properties to the indexes too.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message