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 "Thomas Mueller (JIRA)" <ji...@apache.org> on 2015/03/09 09:06:38 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=14352662#comment-14352662 ] 

Thomas Mueller commented on OAK-2037:
-------------------------------------

Using JSON is a good idea.

> 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
>            Assignee: Thomas Mueller
>             Fix For: 1.2, 1.1.8
>
>
> 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.3.4#6332)