You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@asterixdb.apache.org by "Jochen Taeschner (JIRA)" <ji...@apache.org> on 2017/07/24 17:37:00 UTC
[jira] [Updated] (ASTERIXDB-1999) more api documentation
[ https://issues.apache.org/jira/browse/ASTERIXDB-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jochen Taeschner updated ASTERIXDB-1999:
----------------------------------------
Description:
The {{/admin/cluster}} (and child pages) are not documented on the http api page, but very much should be, as it improves the abilities of users to actually check, what config their instance is running, which nodes are involved etc.
The uri is only mentioned on the users mailing list, is there other documentation somewhere, except for the online version on apache (https://ci.apache.org/projects/asterixdb/index.html)? Because that appears to only be of use to end users and for common basic setup, but it doesn't provide any helpful FAQ like:
* how do I terminate a long running query?
* how do I find out, what queries are running?
* how is the Metadata dataverse structured?
Although this information is in probably changing to some extent, it would probably help a lot if there was more information about how to actually administer an asterixdb cluster, without going deep into the source (which I assume admins are not particularly fond of, if the project reaches a certain size and/or complexity) or ask the mailing list (which possibly adds minutes, hours or days of latency).
was:
The {{/admin/cluster}} (and child pages) are not documented on the http api page, but very much should be, as it improves the abilities of users to actually check, what config their instance is running, which nodes are involved etc.
(although, this doesn't include hostname/ip of the nodes for example)
The uri is only mentioned on the users mailing list, is there other documentation somewhere, except for the online version on apache (https://ci.apache.org/projects/asterixdb/index.html)? Because that appears to only be of use to end users and for common basic setup, but it doesn't provide any helpful FAQ like:
* how do I terminate a long running query?
* how do I find out, what queries are running?
* how is the Metadata dataverse structured?
Although this information is in probably changing to some extent, it would probably help a lot if there was more information about how to actually administer an asterixdb cluster, without going deep into the source (which I assume admins are not particularly fond of, if the project reaches a certain size and/or complexity) or ask the mailing list (which possibly adds minutes, hours or days of latency).
> more api documentation
> ----------------------
>
> Key: ASTERIXDB-1999
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-1999
> Project: Apache AsterixDB
> Issue Type: Improvement
> Components: DOC - Documentation
> Reporter: Jochen Taeschner
> Labels: documentation, newbie
>
> The {{/admin/cluster}} (and child pages) are not documented on the http api page, but very much should be, as it improves the abilities of users to actually check, what config their instance is running, which nodes are involved etc.
> The uri is only mentioned on the users mailing list, is there other documentation somewhere, except for the online version on apache (https://ci.apache.org/projects/asterixdb/index.html)? Because that appears to only be of use to end users and for common basic setup, but it doesn't provide any helpful FAQ like:
> * how do I terminate a long running query?
> * how do I find out, what queries are running?
> * how is the Metadata dataverse structured?
> Although this information is in probably changing to some extent, it would probably help a lot if there was more information about how to actually administer an asterixdb cluster, without going deep into the source (which I assume admins are not particularly fond of, if the project reaches a certain size and/or complexity) or ask the mailing list (which possibly adds minutes, hours or days of latency).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)