[
https://issues.apache.org/jira/browse/CASSANDRA-6091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14168384#comment-14168384
]
mck commented on CASSANDRA-6091:
--------------------------------
[~alexliu68] Any reason we can't (at least to begin with since this is a right
headache) join the splits after the call to describe_splits_ex, as is done in
this [patch|https://github.com/michaelsembwever/cassandra/pull/1/files]?
Although one thing about this patch that i haven't yet understood, when i test
against a single-node cluster i expect rejoinAdjacentSplits(..) to return a
list of one split, token range "-8940796744825771419" to "6948181744525544",
but instead i get that plus two more splits, in total three splits that look
like
1) "-8940796744825771419" to "6948181744525544"
2) "-1" to "-8940796744825771419"
3) "6948181744525544" to "-8940796744825771419"
This is highlighted by the assert statement commented out in ACFIF line 253
Am i doing something wrong or is describe_local_ring?
> Better Vnode support in hadoop/pig
> ----------------------------------
>
> Key: CASSANDRA-6091
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6091
> Project: Cassandra
> Issue Type: Bug
> Components: Hadoop
> Reporter: Alex Liu
> Assignee: Alex Liu
>
> CASSANDRA-6084 shows there are some issues during running hadoop/pig job if
> vnodes are enable. Also the hadoop performance of vnode enabled nodes are
> bad for there are so many splits.
> The idea is to combine vnode splits into a big sudo splits so it work like
> vnode is disable for hadoop/pig job
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
