Yea, server side has to be on the site.xml.
What about the client side ones?
I tried checking usages of setAutoCommit() function in the phoenix
connection.. but couldnt find it properly.. For now calling it on the
connection directly but would be better if the driver/connections takes
care of it
Also.. in the phoenix code found a constant for
phoenix.query.timeoutMs
but not for
phoenix.connection.autoCommit
So, not sure if its supported. I can see that mutate batch size is being
read from the props in the constructor of phoenix connection though.
* Interface to group together services needed during querying. The
* parameters that may be set in {@link org.apache.hadoop.conf.Configuration}
* are documented here: https://github.com/forcedotcom/phoenix/wiki/Tuning
Found this on top of the org.apache.phoenix.query.QueryServices
It says only hadoop conf is supported...
Regards,
Abhilash L L
Capillary Technologies
M:919886208262
[email protected] | www.capillarytech.com
On Wed, Mar 18, 2015 at 6:43 AM, Fulin Sun <[email protected]> wrote:
> Hi,
> Not sure about that. But if you want to check in for some server-side
> config, you may not want to
> pass those through JDBC props approach.
>
> Thanks,
> Sun.
>
> ------------------------------
> ------------------------------
>
> CertusNet
>
>
> *From:* Abhilash L L <[email protected]>
> *Date:* 2015-03-17 20:09
> *To:* user <[email protected]>
> *Subject:* Connection params on phoenix
> Hello,
>
> Is it possible to pass settings listed here
>
> http://phoenix.apache.org/tuning.html
>
> on the jdbc connection and not have it on the hbase-site.xml?
>
>
> Using this API of the phoenix driver
>
> Connection phoenixConnection =
> PhoenixDriver.INSTANCE.connect(getPhoenixJDBCUrl(), props);
>
> Are we missing anything ?
>
> We are using phoenix 3.0.0-incubating
>
>
> Regards,
> Abhilash L L
> Capillary Technologies
> M:919886208262
> [email protected] | www.capillarytech.com
>
> Email from people at capillarytech.com may not represent official policy
> of Capillary Technologies unless explicitly stated. Please see our
> Corporate-Email-Policy for details.Contents of this email are confidential.
> Please contact the Sender if you have received this email in error.
>
>
--
Email from people at capillarytech.com may not represent official policy of
Capillary Technologies unless explicitly stated. Please see our
Corporate-Email-Policy for details.Contents of this email are confidential.
Please contact the Sender if you have received this email in error.
