Josh Elser

> I can reproduce this by setFetchSize(0) on the PreparedStatement before executing it. Oof. Getting fetchSize and maxResultSize mixed up is bad. > I found a solution to the setFetchSize...

Thanks for trying to fix this, @LakshSingla I'm not 100% certain anymore, but this may have been an intentional decision previously. Avatica has its own set of JDBC properties which...

(sorry for the wide ping) @virajjasani @gjacoby126 @ChinmaySKulkarni @apurtell have any of your noticed this one in 1.x? The change seems reasonable to me, but I haven't kept up with...

``` jdbc:phoenix+zk:hostname1,2,3...: jdbc:phoenix+hrpc:hostname1,2,3...: ``` What is "hrpc" supposed to stand for in this case? I would think "masters" or "registry" might be more clear? I think the problem here is...

Thanks for publishing this PR, Rahul! For context, we've been running with this change internally. Prior to making this patch, we've been unable to ingest more than ~4TB of data...

This one also broke Apache Phoenix's JDBC (which has extensive semi-colon use). I like Dimitri's suggestion to use quoting to avoid the problematic parsing. I'll see if I can find...

Ha, small world. Yeah, I wrote this before 1.5 was released with the new API calls. You could try updating it to use the new PasswordToken construct (instead of the...

Depending on the version of Hadoop used, you may be missing dependencies that Accumulo marked a provided (or that I marked as provided). commons-collections, commons-configuration, commons-lang and commons-io come to...

Hi @btbytes! Thanks for the changes so far. A couple of things: 1. Have you opened a JIRA issue which captures the changes you'd like to make? We want to...

Great! I've given you karma and assigned PHOENIX-3132 to you. > I was waiting for a response do this PR before I took on more refactoring ;) Hah! Smart :)...