Here are few suggestions based on what I found tricky to understand
1. How do thin client and thick client work or have dependency on each
other? This was clear after you told me and did some more research
2. If I use thin client can I also use thick client? I had to try this out
to be sure. The
The thick client talks directly to HBase. The thin client talks to PQS.
You cannot mix-and-match.
Glad to hear you got it working. How can the documentation be improved
to make this more clear?
On 10/23/18 9:11 PM, Monil Gandhi wrote:
Hello
Update. I was able to figure this out. Thanks for
Hello
Update. I was able to figure this out. Thanks for the initial pointer :)
On Mon, Oct 22, 2018 at 10:54 PM Monil Gandhi wrote:
> Hello,
> Thanks for the earlier reply.
> I am a little confused with documentation and the response from Josh. This
> may be my limited knowledge with Phoenix.
>
Hello,
Thanks for the earlier reply.
I am a little confused with documentation and the response from Josh. This
may be my limited knowledge with Phoenix.
Can I connect to the server with thick client instead of thin for my server
which is running thing client since thick client seems to be
Okay. Will take a look. Thanks
On Wed, Oct 17, 2018 at 8:28 AM Josh Elser wrote:
> The methods that you are invoking assume that the Phoenix JDBC driver
> (the java class org.apache.phoenix.jdbc.PhoenixDriver) is in use. It's
> not, so you get this error.
>
> The Phoenix "thick" JDBC driver is
The methods that you are invoking assume that the Phoenix JDBC driver
(the java class org.apache.phoenix.jdbc.PhoenixDriver) is in use. It's
not, so you get this error.
The Phoenix "thick" JDBC driver is what's running inside of the Phoenix
Query Server, just not in your local JVM. As such,
Hello,
I am trying to collect some metrics on certain queries. Here is the code
that I have
Properties props = new Properties();
props.setProperty(QueryServices.COLLECT_REQUEST_LEVEL_METRICS, "true");
props.setProperty("phoenix.trace.frequency", "always");
try (Connection conn =
