Should we allow dependent projects (such as Phoenix) to weigh in on this issue
since they are likely going to be the ones that benefit/are effected?
On 4/11/17, 10:17 AM, "York, Zach" wrote:
+1 (non-binding)
This sounds like a good idea to me!
Zach
On
+1 (non-binding)
This sounds like a good idea to me!
Zach
On 4/11/17, 9:48 AM, "saint@gmail.com on behalf of Stack"
wrote:
Let me revive this thread.
Recall, we are stuck on old or particular versions of critical libs. We are
unable to update because our versions will cla
+1
I meant to send this a while ago.
On 4/3/17, 5:43 PM, "James Taylor" wrote:
Hello,
We'd like to start supporting releases of Phoenix that work with the HBase
1.3 branch, but there's a committed fix on which we rely (HBASE-17587) for
Phoenix to function correctly. Is there a t
Thanks for the updates! I will review when I have time.
On 2/17/17, 4:16 PM, "Umesh Agashe" wrote:
Hi,
Here is the doc that summarizes our discussion about why we think top-down
approach requiring radical code changes compared to incremental, phased
(bottom-up) approach will
I would recommend you use the dev-support/submit-patch.py script to create your
patch.
Information can be found here:
http://hbase.apache.org/book.html#submitting.patches.create
Thanks,
Zach
On 1/25/17, 11:34 AM, "Chetan Khatri" wrote:
Hello ,
I have been submitted 3 PR to HBase
