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

2016-01-20 Thread Thomas Mueller (JIRA)

 [ 
https://issues.apache.org/jira/browse/OAK-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Thomas Mueller updated OAK-2037:

Fix Version/s: (was: 1.4)

> Define standards for plan output
> 
>
> Key: OAK-2037
> URL: https://issues.apache.org/jira/browse/OAK-2037
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: query
>Reporter: Justin Edelson
>Assignee: Thomas Mueller
>Priority: Minor
>  Labels: tooling
>
> 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)


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

2015-11-25 Thread Thomas Mueller (JIRA)

 [ 
https://issues.apache.org/jira/browse/OAK-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Thomas Mueller updated OAK-2037:

Fix Version/s: 1.4

> Define standards for plan output
> 
>
> Key: OAK-2037
> URL: https://issues.apache.org/jira/browse/OAK-2037
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: query
>Reporter: Justin Edelson
>Assignee: Thomas Mueller
>Priority: Minor
>  Labels: tooling
> Fix For: 1.4
>
>
> 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)


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

2015-10-22 Thread Thomas Mueller (JIRA)

 [ 
https://issues.apache.org/jira/browse/OAK-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Thomas Mueller updated OAK-2037:

Fix Version/s: (was: 1.3.9)

> Define standards for plan output
> 
>
> Key: OAK-2037
> URL: https://issues.apache.org/jira/browse/OAK-2037
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: query
>Reporter: Justin Edelson
>Assignee: Thomas Mueller
>Priority: Minor
>  Labels: tooling
>
> 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)


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

2015-09-10 Thread Thomas Mueller (JIRA)

 [ 
https://issues.apache.org/jira/browse/OAK-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Thomas Mueller updated OAK-2037:

Fix Version/s: (was: 1.3.7)
   1.3.9

> Define standards for plan output
> 
>
> Key: OAK-2037
> URL: https://issues.apache.org/jira/browse/OAK-2037
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: query
>Reporter: Justin Edelson
>Assignee: Thomas Mueller
>Priority: Minor
>  Labels: tooling
> Fix For: 1.3.9
>
>
> 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)


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

2015-09-02 Thread Thomas Mueller (JIRA)

 [ 
https://issues.apache.org/jira/browse/OAK-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Thomas Mueller updated OAK-2037:

Fix Version/s: (was: 1.3.6)
   1.3.7

> Define standards for plan output
> 
>
> Key: OAK-2037
> URL: https://issues.apache.org/jira/browse/OAK-2037
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: query
>Reporter: Justin Edelson
>Assignee: Thomas Mueller
>Priority: Minor
>  Labels: tooling
> Fix For: 1.3.7
>
>
> 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)


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

2015-08-07 Thread Thomas Mueller (JIRA)

 [ 
https://issues.apache.org/jira/browse/OAK-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Thomas Mueller updated OAK-2037:

Fix Version/s: (was: 1.3.5)
   1.3.6

 Define standards for plan output
 

 Key: OAK-2037
 URL: https://issues.apache.org/jira/browse/OAK-2037
 Project: Jackrabbit Oak
  Issue Type: Improvement
  Components: query
Reporter: Justin Edelson
Assignee: Thomas Mueller
Priority: Minor
  Labels: tooling
 Fix For: 1.3.6


 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)


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

2015-07-22 Thread Thomas Mueller (JIRA)

 [ 
https://issues.apache.org/jira/browse/OAK-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Thomas Mueller updated OAK-2037:

Fix Version/s: (was: 1.3.4)
   1.3.5

 Define standards for plan output
 

 Key: OAK-2037
 URL: https://issues.apache.org/jira/browse/OAK-2037
 Project: Jackrabbit Oak
  Issue Type: Improvement
  Components: query
Reporter: Justin Edelson
Assignee: Thomas Mueller
Priority: Minor
  Labels: tooling
 Fix For: 1.3.5


 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)


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

2015-07-20 Thread Davide Giannella (JIRA)

 [ 
https://issues.apache.org/jira/browse/OAK-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Davide Giannella updated OAK-2037:
--
Fix Version/s: (was: 1.3.3)
   1.3.4

Bulk move to 1.3.4

 Define standards for plan output
 

 Key: OAK-2037
 URL: https://issues.apache.org/jira/browse/OAK-2037
 Project: Jackrabbit Oak
  Issue Type: Improvement
  Components: query
Reporter: Justin Edelson
Assignee: Thomas Mueller
Priority: Minor
  Labels: tooling
 Fix For: 1.3.4


 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)


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

2015-07-01 Thread Davide Giannella (JIRA)

 [ 
https://issues.apache.org/jira/browse/OAK-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Davide Giannella updated OAK-2037:
--
Fix Version/s: (was: 1.3.2)
   1.3.3

Bulk move to 1.3.3.

 Define standards for plan output
 

 Key: OAK-2037
 URL: https://issues.apache.org/jira/browse/OAK-2037
 Project: Jackrabbit Oak
  Issue Type: Improvement
  Components: query
Reporter: Justin Edelson
Assignee: Thomas Mueller
Priority: Minor
  Labels: tooling
 Fix For: 1.3.3


 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)


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

2015-06-22 Thread Davide Giannella (JIRA)

 [ 
https://issues.apache.org/jira/browse/OAK-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Davide Giannella updated OAK-2037:
--
Fix Version/s: (was: 1.3.1)
   1.3.2

Bulk move to 1.3.2

 Define standards for plan output
 

 Key: OAK-2037
 URL: https://issues.apache.org/jira/browse/OAK-2037
 Project: Jackrabbit Oak
  Issue Type: Improvement
  Components: query
Reporter: Justin Edelson
Assignee: Thomas Mueller
Priority: Minor
  Labels: tooling
 Fix For: 1.3.2


 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)


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

2015-04-29 Thread Michael Marth (JIRA)

 [ 
https://issues.apache.org/jira/browse/OAK-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Marth updated OAK-2037:
---
Priority: Minor  (was: Major)

 Define standards for plan output
 

 Key: OAK-2037
 URL: https://issues.apache.org/jira/browse/OAK-2037
 Project: Jackrabbit Oak
  Issue Type: Improvement
  Components: query
Reporter: Justin Edelson
Assignee: Thomas Mueller
Priority: Minor
  Labels: tooling
 Fix For: 1.3.0


 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)


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

2015-04-29 Thread Michael Marth (JIRA)

 [ 
https://issues.apache.org/jira/browse/OAK-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Marth updated OAK-2037:
---
Labels: tooling  (was: )

 Define standards for plan output
 

 Key: OAK-2037
 URL: https://issues.apache.org/jira/browse/OAK-2037
 Project: Jackrabbit Oak
  Issue Type: Improvement
  Components: query
Reporter: Justin Edelson
Assignee: Thomas Mueller
  Labels: tooling
 Fix For: 1.3.0


 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)


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

2015-03-20 Thread Thomas Mueller (JIRA)

 [ 
https://issues.apache.org/jira/browse/OAK-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Thomas Mueller updated OAK-2037:

Fix Version/s: (was: 1.1.8)
   (was: 1.2)
   1.3.0

 Define standards for plan output
 

 Key: OAK-2037
 URL: https://issues.apache.org/jira/browse/OAK-2037
 Project: Jackrabbit Oak
  Issue Type: Improvement
  Components: query
Reporter: Justin Edelson
Assignee: Thomas Mueller
 Fix For: 1.3.0


 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)


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

2015-03-10 Thread Michael Marth (JIRA)

 [ 
https://issues.apache.org/jira/browse/OAK-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Marth updated OAK-2037:
---
Issue Type: Improvement  (was: Task)

 Define standards for plan output
 

 Key: OAK-2037
 URL: https://issues.apache.org/jira/browse/OAK-2037
 Project: Jackrabbit Oak
  Issue Type: Improvement
  Components: query
Reporter: Justin Edelson
Assignee: Thomas Mueller
 Fix For: 1.1.8, 1.2


 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)


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

2015-02-04 Thread Davide Giannella (JIRA)

 [ 
https://issues.apache.org/jira/browse/OAK-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Davide Giannella updated OAK-2037:
--
Fix Version/s: (was: 1.1.6)
   1.1.7

 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
 Fix For: 1.1.7


 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)


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

2015-01-21 Thread Michael Marth (JIRA)

 [ 
https://issues.apache.org/jira/browse/OAK-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Marth updated OAK-2037:
---
Fix Version/s: 1.1.6

 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
 Fix For: 1.1.6


 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)