We've been behind on the open source support issues due to a surge in customer feature development and services.  I certainly will get to this as soon as possible.  If you would like to help, maybe you can drill down into the query and see if you can figure out why it is failing.  That would make it easier for us to identify a fix.

My guess is that the filter is being silently dropped during a rewrite of the UNION.  This would be one of the AST optimizers.  If you look at AST2BOpUtility, you can see that it runs the AST optimizers here:

        // Run the AST query rewrites / query optimizers.

        final QueryRoot optimizedQuery = (QueryRoot) ctx.optimizers.optimize(ctx,

                originalQuery, bindingSets);

Probably one of these rewrite stages is responsible for dropping the FILTER.  It would help if you could (a) identify whether the FILTER is being dropped by a query rewrite stage; and (b) which one is dropping the FILTER.


From: Peter Amstutz <>
Reply-To: "[bigdata:discussion]" <>
Date: Monday, April 7, 2014 9:42 AM
To: "[bigdata:discussion]" <>
Subject: [bigdata:discussion] Bigdata graph issues

Hi Bryan,

I hope you can address the issues with UNION and FILTER soon. I am hoping to use Bigdata for the Arvados ( metadata database and have already invested substantial time working out how to build a permissions model. However, I can't build my permission rules without UNION, and I don't think I can ask users to go without FILTER, so this is a showstopper for me.

Bigdata graph issues

Sent from because you indicated interest in

To unsubscribe from further messages, please visit