[
https://issues.apache.org/jira/browse/HBASE-12853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey updated HBASE-12853:
--------------------------------
Priority: Major (was: Minor)
Fix Version/s: 2.0.0
This issue has been unassigned, had no fix versipn targetted, and was listed at
Minor priority. I do't find it surprising that there were no updates.
Personally i think this will make a great feature addition that will help us
tackle more workloads. Accordingly, ive chaned it to major and set a goal of
2.0.
Please do not downplay the effort needed by whomever ends up implementing it by
claiming it is trivial. The ASF is a
[do-ocracy|http://www.apache.org/foundation/how-it-works.html#decision-making];
while all contributions are valuable please don't criticize the prioritization
of othrr volunteers when you yourself have not prioritized the feature yourself.
> distributed write pattern to replace ad hoc 'salting'
> -----------------------------------------------------
>
> Key: HBASE-12853
> URL: https://issues.apache.org/jira/browse/HBASE-12853
> Project: HBase
> Issue Type: New Feature
> Reporter: Michael Segel
> Fix For: 2.0.0
>
>
> In reviewing HBASE-11682 (Description of Hot Spotting), one of the issues is
> that while 'salting' alleviated regional hot spotting, it increased the
> complexity required to utilize the data.
> Through the use of coprocessors, it should be possible to offer a method
> which distributes the data on write across the cluster and then manages
> reading the data returning a sort ordered result set, abstracting the
> underlying process.
> On table creation, a flag is set to indicate that this is a parallel table.
> On insert in to the table, if the flag is set to true then a prefix is added
> to the key. e.g. <region server#>- or <region server #|| where the region
> server # is an integer between 1 and the number of region servers defined.
> On read (scan) for each region server defined, a separate scan is created
> adding the prefix. Since each scan will be in sort order, its possible to
> strip the prefix and return the lowest value key from each of the subsets.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
