[jira] [Comment Edited] (OAK-2037) Define standards for plan output

["Chetan Mehrotra (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OAK-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14099536#comment-14099536 ] 

Chetan Mehrotra edited comment on OAK-2037 at 8/16/14 7:21 AM:
---------------------------------------------------------------

+1 for introducing some structure. Probably the explain can be a JSON string which would allow tooling/testcase to extract relevant information easily similar to how Mongo exposes the plan details [1]

{code:javascript}
{
  "cursor" : "<Cursor Type and Index>",
  "isMultiKey" : <boolean>,
  "n" : <num>,
  "nscannedObjects" : <num>,
  "nscanned" : <num>,
  "nscannedObjectsAllPlans" : <num>,
  "nscannedAllPlans" : <num>,
  "scanAndOrder" : <boolean>,
  "indexOnly" : <boolean>,
  "nYields" : <num>,
  "nChunkSkips" : <num>,
  "millis" : <num>,
  "indexBounds" : { <index bounds> },
  "allPlans" : [
                 { "cursor" : "<Cursor Type and Index>",
                   "n" : <num>,
                   "nscannedObjects" : <num>,
                   "nscanned" : <num>,
                   "indexBounds" : { <index bounds> }
                 },
                  ...
               ],
  "oldPlan" : {
                "cursor" : "<Cursor Type and Index>",
                "indexBounds" : { <index bounds> }
              }
  "server" : "<host:port>",
  "filterSet" : <boolean>
}


{code}

[1] http://docs.mongodb.org/manual/reference/method/cursor.explain/#cursor.explain


was (Author: chetanm):
+1 for introducing some structure. Probably the explain can be a JSON string which would allow tooling/testcase to extract relevant information easily

> Define standards for plan output
> --------------------------------
>
>                 Key: OAK-2037
>                 URL: https://issues.apache.org/jira/browse/OAK-2037
>             Project: Jackrabbit Oak
>          Issue Type: Task
>          Components: query
>            Reporter: Justin Edelson
>
> Currently, the syntax for the plan output is chaotic as it varies significantly from index to index. Whereas some of this is expected - each index type will have different data to output, Oak should provide some standards about how a plan will appear.



--
This message was sent by Atlassian JIRA
(v6.2#6252)