phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Geoffrey Jacoby (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-4344) MapReduce Delete Support
Date Wed, 14 Feb 2018 21:25:00 GMT


Geoffrey Jacoby commented on PHOENIX-4344:

[~jamestaylor] - if I remember right, normal Phoenix deletes already have an issue where deleting
from a base table won't delete from the views – you have to delete from the view to get
it to "do the right thing". Given that, would it be OK to require the user to use the view
name in a DELETE MapReduce query if they want the view and its indexes to be updated? 

This could be changed in the future if Phoenix deletes get smarter about finding and deleting
from child views/indexes. 

For the particular use case that [~akshita.malhotra] and I have in mind for this feature, the
users will definitely know the views they want to delete from. 

> MapReduce Delete Support
> ------------------------
>                 Key: PHOENIX-4344
>                 URL:
>             Project: Phoenix
>          Issue Type: New Feature
>    Affects Versions: 4.12.0
>            Reporter: Geoffrey Jacoby
>            Assignee: Geoffrey Jacoby
>            Priority: Major
> Phoenix already has the ability to use MapReduce for asynchronous handling of long-running
SELECTs. It would be really useful to have this capability for long-running DELETEs, particularly
of tables with indexes where using HBase's own MapReduce integration would be prohibitively

This message was sent by Atlassian JIRA

View raw message