You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2014/08/16 09:15:18 UTC

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

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

Chetan Mehrotra commented on OAK-2037:
--------------------------------------

+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)