[
https://issues.apache.org/jira/browse/HIVE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13008917#comment-13008917
]
Edward Capriolo commented on HIVE-1434:
---------------------------------------
I am not at all happy with this being a blocker. First off let me point out
that I seem to ALWAYS get held to a higher standard then everyone else. For
example, https://issues.apache.org/jira/browse/HIVE-1335 it was insisted that I
use IVY. Yet with https://issues.apache.org/jira/browse/HIVE-1235 obviously no
such rule was enforced here.
As you pointed out:
{quote}
The HBase problems were part of what caused Hive continuous integration to go
broken for many weeks. The failure frequency was very high due to conflicts
from unrelated port-hungry services being run on committer dev boxes.
{quote}
So in other words, the hbase-handler was allowed to go +1 and break the
hudson/jenkins for weeks, until someone got around to finding a solution, but
now this same reason this will go -1 and not get committed.
Upstream Hadoop !!NEVER!! completes a full 'ant test' successfully. While this
is not an ideal situation it is a fact.
Also the one week lag time between patch-available and review just to find one
new blocker at a time is getting old. I think I have seen 15 issues get
reviewed and committed since this went patch_available.
> Cassandra Storage Handler
> -------------------------
>
> Key: HIVE-1434
> URL: https://issues.apache.org/jira/browse/HIVE-1434
> Project: Hive
> Issue Type: New Feature
> Affects Versions: 0.7.0
> Reporter: Edward Capriolo
> Assignee: Edward Capriolo
> Attachments: cas-handle.tar.gz, cass_handler.diff, hive-1434-1.txt,
> hive-1434-2-patch.txt, hive-1434-2011-02-26.patch.txt,
> hive-1434-2011-03-07.patch.txt, hive-1434-2011-03-07.patch.txt,
> hive-1434-2011-03-14.patch.txt, hive-1434-3-patch.txt, hive-1434-4-patch.txt,
> hive-1434-5.patch.txt, hive-1434.2011-02-27.diff.txt,
> hive-cassandra.2011-02-25.txt, hive.diff
>
>
> Add a cassandra storage handler.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
