[jira] [Assigned] (PHOENIX-5117) Return the count of rows scanned in HBase
[ https://issues.apache.org/jira/browse/PHOENIX-5117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tanuj Khurana reassigned PHOENIX-5117: -- Assignee: Tanuj Khurana (was: Chen Feng) > Return the count of rows scanned in HBase > - > > Key: PHOENIX-5117 > URL: https://issues.apache.org/jira/browse/PHOENIX-5117 > Project: Phoenix > Issue Type: New Feature >Affects Versions: 4.14.1 >Reporter: Chen Feng >Assignee: Tanuj Khurana >Priority: Minor > Fix For: 5.3.0 > > Attachments: PHOENIX-5117-4.x-HBase-1.4-v1.patch, > PHOENIX-5117-4.x-HBase-1.4-v2.patch, PHOENIX-5117-4.x-HBase-1.4-v3.patch, > PHOENIX-5117-4.x-HBase-1.4-v4.patch, PHOENIX-5117-4.x-HBase-1.4-v5.patch, > PHOENIX-5117-4.x-HBase-1.4-v6.patch, PHOENIX-5117-v1.patch > > > HBASE-5980 provides the ability to return the number of rows scanned. Such > metrics should also be returned by Phoenix. > HBASE-21815 is acquired. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (PHOENIX-7170) Conditional TTL
[ https://issues.apache.org/jira/browse/PHOENIX-7170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viraj Jasani reassigned PHOENIX-7170: - Assignee: Viraj Jasani > Conditional TTL > --- > > Key: PHOENIX-7170 > URL: https://issues.apache.org/jira/browse/PHOENIX-7170 > Project: Phoenix > Issue Type: New Feature >Reporter: Kadir Ozdemir >Assignee: Viraj Jasani >Priority: Major > > Deleting rows using delete markers require running delete queries to insert > them, one for each row to be deleted. Often applications need to run periodic > jobs to issue delete queries to insert delete markers. Deleting rows using > TTL is more performance optimized compared to adding delete markers in > Phoenix since TTL works without inserting delete markers. Phoenix currently > supports table and view (level) TTL. It is desirable to have a conditional > TTL feature to extend the TTL future to expire a subset of rows of a table or > updatable view using a different TTL value. > A condition TTL can be set using a CASE statement in CREATE and ALTER > statements by adding TTL=. For example, > TTL = CASE WHEN ID IS BETWEEN 1 AND 100 THEN <10 days> WHEN ID IS BETWEEN 101 > AND 200 <7 days> ELSE <5 days> END > The compaction scanner (CompactionScanner) in Phoenix can evaluate the case > statement on a row and decide if the row should be removed. Similarly, on the > read path TTLRegionScanner can mask the rows using the case statement. The > TTL case statement can be stored in SYSCAT in header rows. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (PHOENIX-7177) some IT testcases depending on TaskRegionEnvironment can't run on distributed HBaseCluster
[ https://issues.apache.org/jira/browse/PHOENIX-7177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anchal Kejriwal updated PHOENIX-7177: - Issue Type: Improvement (was: Bug) > some IT testcases depending on TaskRegionEnvironment can't run on distributed > HBaseCluster > -- > > Key: PHOENIX-7177 > URL: https://issues.apache.org/jira/browse/PHOENIX-7177 > Project: Phoenix > Issue Type: Improvement >Reporter: Anchal Kejriwal >Assignee: Anchal Kejriwal >Priority: Major > Labels: test > > Reason: Because of initialisation of TaskRegionEnvironment in internal API > call which needs miniCluster to run testcases > Example testcase: ReadIsolationLevelIT -- This message was sent by Atlassian Jira (v8.20.10#820010)
