Thanks, Jaanai. For the second question, did you mean the region server logs?
Also, I see that Phoenix has tracing features that we can enable. Could we enable it to get more information or what is it that tracing provides that region server logs cannot? -AT On Thu, Feb 14, 2019 at 8:37 AM Jaanai Zhang <cloud.pos...@gmail.com> wrote: > 1. How do we capture the debug level logs on this jdbc client? Should we >> also enable debug level on the region servers to understand what is >> triggering this error? >> > > You can set the logging level in the log4j configuration file on the > client side, most of the time we can disable the debug level. > > 2. Primary key on that table had a not null constraint and not sure why >> the error was stating null? >> > > This is an error of the server side, perhaps you can find some exceptions > from the log files. > > ---------------------------------------- > Jaanai Zhang > Best regards! > > > > talluri abhishek <abhishektall...@gmail.com> 于2019年2月13日周三 上午11:06写道： > >> Hi All, >> >> I have a `select primary_key from table_name limit 500000` query that >> works most of the time but it returns the below error at times. >> ERROR 212 (22012): Arithmetic error on server. ERROR 212 (22012): >> Arithmetic error on server. null >> We are using a jdbc client to query phoenix and have the following >> questions in mind >> >> 1. How do we capture the debug level logs on this jdbc client? Should we >> also enable debug level on the region servers to understand what is >> triggering this error? >> 2. Primary key on that table had a not null constraint and not sure why >> the error was stating null? >> >> Thanks, >> Abhishek >> >
