[
https://issues.apache.org/jira/browse/PHOENIX-977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13994754#comment-13994754
]
James Taylor commented on PHOENIX-977:
--------------------------------------
All good ideas, [~cristian_armaselu]. Always best to file separate JIRAs for
separate ideas, though:
1) The custom row key separator is a duplicate of PHOENIX-506.
2) When you drop a view (as opposed to a table), the existing hbase table and
data are left as-is. There's also the phoenix.schema.dropMetaData config
parameter documented here: http://phoenix.incubator.apache.org/tuning.html
which allows you to keep the HBase table meta data around (it will place delete
markers for the data, though). Please open a new JIRA if you'd like an option
to keep both the data and the metadata for a table.
3) We support mapping multiple PTables to the same HBase table through VIEWs.
See http://phoenix.incubator.apache.org/views.html
> custom row key separator
> ------------------------
>
> Key: PHOENIX-977
> URL: https://issues.apache.org/jira/browse/PHOENIX-977
> Project: Phoenix
> Issue Type: Wish
> Reporter: Cristian Armaselu
>
> It would be nice if we can have a custom row key separator stored together
> with the PTable metadata used at table creation time.
> impala doesn't handle very well 0x00 separator
> Also it would be useful to be able to drop a PTable without dropping the
> existing hbase table and data, or at least make it optional.
> Also it would be nice to be able to create multiple PTables mapped to the
> same hbase table since the end goal is to create less table in hbase, bundle
> them together in one big table.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
