[
https://issues.apache.org/jira/browse/CALCITE-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser resolved CALCITE-1195.
---------------------------------
Resolution: Fixed
Committed in
https://git-wip-us.apache.org/repos/asf?p=calcite-avatica.git;a=commit;h=0020a547c845cc27f7dc048f2b8ac7cb83dc53e0
I published it at https://calcite.apache.org/avatica/docs/protocol_testing.html
after verifying that it works against the hsqldb avatica-1.10.0 docker image.
While there's always more we can do, this is a bit too broad to get anywhere
more with it. I should try to make more focused doc tickets in the future :)
> Create docs for interacting with Avatica server using json+curl
> ---------------------------------------------------------------
>
> Key: CALCITE-1195
> URL: https://issues.apache.org/jira/browse/CALCITE-1195
> Project: Calcite
> Issue Type: Task
> Components: avatica
> Reporter: Josh Elser
> Assignee: Josh Elser
> Fix For: avatica-1.11.0
>
> Attachments: test_avatica_solr.sh
>
>
> A repeated problem I hear from people is that they are trying to use outdated
> CURL commands with JSON to "test" out the server.
> People will get to {{prepareAndExecute}} and then the query will fail.
> It appears that CALCITE-718 in 1.4.0-incubating changed the semantics of this
> request implementation to require a Statement to already exist in the server
> (by {{CreateStatement}}), whereas previous versions automatically created
> this Statement as a part of the call.
> We can get around this issue by just keep up-to-date docs on what the CURL
> commands to run are for simple actions.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
