That documentation is still the same. Going through the query server doesn't change anything. The important quote there about starting a transaction:
A transaction is started implicitly through the execution of a statement on a transactional table and then finished through either a commit or rollback. On Sat, Mar 26, 2016 at 11:08 PM, F21 <[email protected]> wrote: > Hi James, > > Thanks for the quick reply. The docs does talk about how to use > transactions with phoenix, but doesn't seem to answer my questions > regarding implementing transactions for a phoenix query server client. > > Cheers! > > > On 27/03/2016 5:04 PM, James Taylor wrote: > >> Please read https://phoenix.apache.org/transactions.html and let us know >> if >> it doesn't answer your questions. >> >> Thanks, >> James >> >> On Sat, Mar 26, 2016 at 10:00 PM, F21 <[email protected]> wrote: >> >> Hi guys, >>> >>> As I posted on the Phoenix list a few days ago, I am working on a golang >>> client for the phoenix query service (which uses avatica). >>> >>> In regards to starting a transaction, I see that the protobuf reference >>> contains Commit and Rollback requests, but there isn't any Begin request. >>> >>> Is sending a ConnectionSync request and setting autoCommit to false the >>> correct way to start a transaction? >>> >>> Also, what is the state of autoCommit when I send an Open request to the >>> server? >>> >>> Finally, the Open request allows me to send a map called info. What is >>> suppose to go into this map? >>> >>> Cheers! >>> >>> >
