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

Posted to oak-dev@jackrabbit.apache.org by Thomas Mueller <mu...@adobe.com> on 2017/04/27 09:16:48 UTC

Intent to backport to 1.6: OAK-6116

Severity:

* Affects generated queries (generated using a query builder tool).
* The workaround is to _not_ use path restrictions in the query, which slows down the query.
* Only affects new queries.
* Failure is during the parse phase.

The risk of fixing:

* The change is limited to "union" queries (a new feature in Oak 1.6)
* The change is small
* There are tests
* Already reviewed

Risk of not fixing:

* Breaks the new feature of XPath union queries.
* Having to switch to the "old-style" (restricting the path manually).

Regards,
Thomas

Re: Intent to backport to 1.6: OAK-6116

Posted by Matt Ryan <os...@mvryan.org>.

+1

On Thu, Apr 27, 2017 at 3:25 AM, Vikas Saurabh <vi...@gmail.com>
wrote:

> potentially illegimate +1 to backport from my side (as I was the one
> who reviewed and already +1-ed backporting on the issue itself)
>
> Thanks,
> Vikas
>

Re: Intent to backport to 1.6: OAK-6116

Posted by Vikas Saurabh <vi...@gmail.com>.

potentially illegimate +1 to backport from my side (as I was the one
who reviewed and already +1-ed backporting on the issue itself)

Thanks,
Vikas