Re: Cannot get more than 5 columns in result set

That solved it, thanks a bunch! On Monday, April 4, 2016, Jonathan Leech wrote: > !set maxWidth 2000 (or something like that, check the help) > > You can also set your terminal really wide prior to launching sqlline. > > > > > On Apr 4, 2016, at 1:30 PM, Ian Maloney > wrote: > > > > Using Phoen

Re: Cannot get more than 5 columns in result set

Or use a different client, like SQuirrel. On Monday, April 4, 2016, Ian Maloney wrote: > That solved it, thanks a bunch! > > On Monday, April 4, 2016, Jonathan Leech > wrote: > >> !set maxWidth 2000 (or something like that, check the help) >> >> You can also set your terminal really wide prior

Re: Cannot get more than 5 columns in result set

!set outputformat csv OR !set outputformat tsv — Regards, Subbu Manager, Platform Services Metabiota, Inc. (www.metabiota.com ) CONFIDENTIALITY NOTICE: The information contained in this electronic mail (email) transmission (including attachments), is intende

Re: Cannot get more than 5 columns in result set

!set maxWidth 2000 (or something like that, check the help) You can also set your terminal really wide prior to launching sqlline. > On Apr 4, 2016, at 1:30 PM, Ian Maloney wrote: > > Using Phoenix 4.4.0 to query a view created on an HBase 1.1.2 table, using > sqlline(.py), I can only get 5

Cannot get more than 5 columns in result set

Using Phoenix 4.4.0 to query a view created on an HBase 1.1.2 table, using sqlline(.py), I can only get 5 columns in my results I've tried both select * and hard coding columns, I know the other columns are there because when I removed some columns in my hard coding, more showed up so the total was

Phoenix Query Server - proper POST body format

I'm guessing this will be a pretty easy question for someone to answer... I've had success making POST requests to the Query Server by putting the payload in the request header, like so: Key: "request" Value: "{"request": "prepareAndExecute", "sql": "SELECT* FROM

Re: Phoenix transactions not committing.

If you invoked a commit on PQS, it should have flushed any cached values to HBase. The general messages you described in your initial post look correct at a glance. If you have an end-to-end example of this that I can play with, I can help explain what's happening inside of PQS. If you want to

Re: Phoenix jars on http://mvnrepository.com

Hi Pierre, 1.1.2.2.4 is not a version of Apache HBase. Might you be needing to contact a vendor for specific information? Either way, the phoenix shaded client and server (targeted for HBase server) are not attached to the Maven build which means that they are not deployed via Maven as a par

Re: Non-transactional table has transaction-like behavior

Let's think back to before transactions where added to Phoenix. With autoCommit=false, updates to HBase will be batched in the Phoenix driver, eventually flushing on their own or whenever you invoked commit() on the connection. With autoCommit=true, updates to HBase are flushed with every exe