[
https://issues.apache.org/jira/browse/HBASE-7236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Shelukhin updated HBASE-7236:
------------------------------------
Attachment: HBASE-7236-PROTOTYPE.patch
After poking around a bit, I think it's a good idea to have direct config key
override.
Justification is that having separately names metadata fields will be hard to
manage given the potential number of fields.
Ditto for JSON serialization - it would require special logic to validate/use
overrides, and shell support would be painful.
Perhaps we can white-list configs that can be overridden this way, too, inside
HTableDescriptor.
Here's the prototype for table level only, and with no shell support and tests
for now.
Technically, this approach already works in Store for column family
(CompoundConfiguration is created with family metadata overriding
Configuration, so if someone adds a key with correct name to family metadata it
will override xml config within Store); however, making it explicit and
separate from miscellaneous metadata would be cleaner imho.
Please comment... Thanks!
> add per-table/per-cf compaction configuration via metadata
> ----------------------------------------------------------
>
> Key: HBASE-7236
> URL: https://issues.apache.org/jira/browse/HBASE-7236
> Project: HBase
> Issue Type: New Feature
> Components: Compaction
> Affects Versions: 0.96.0
> Reporter: Sergey Shelukhin
> Assignee: Sergey Shelukhin
> Attachments: HBASE-7236-PROTOTYPE.patch
>
>
> Regardless of the compaction policy, it makes sense to have separate
> configuration for compactions for different tables and column families, as
> their access patterns and workloads can be different. In particular, for
> tiered compactions that are being ported from 0.89-fb branch it is necessary
> to have, to use it properly.
> We might want to add support for compaction configuration via metadata on
> table/cf.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
