The Number represents the XMark query number. Query 18 uses a user defined function. We decided to table this features since I am not sure what is involved in implementing user defined functions.
On Fri, Jul 24, 2015 at 9:01 AM, Shivani Mall <[email protected]> wrote: > Hello everyone, > > Hope you’re having an amazing summer! Here is a great update that I would > like to share. > > 10 out of 20 XMark Queries now run on VXQuery. Rest 10 queries either > produce expected result with some error (as you can see below) or have > identified sources of error, which is great because they can be worked on! > > Please refer to the table below for a detailed analysis on each query. > > VXQuery is just about to take over!!…Almost there [image: 😊] > > Cheers, > Shivani > > > Number Received Expected Result Print Expected Result > (endline vs space- printing issue) Doesn’t Blow up the frame size Error 1 > 13 Yes No Yes None 2 17 Yes No Yes None 3 15 Yes No No Fails for > collection, works for doc (bummer:/ ) 4 16 Yes No No None 5 11 Yes > (on Preston’s Mac fails on my comp) No Yes None 6 12 Yes Yes Yes None > 7 1 Yes Yes Yes None 8 4 Yes Yes Yes None 9 5 Yes Yes Yes None 10 6 > No No Yes Count Function fails 11 7 No No Yes > Count Function fails > 12 14 No > No > Yes > During Dynamic Evaluation Phase Dynamic Type does not match the type 13 > 20 > No > No > Yes > Same as Above 14 2 > Yes > Yes > Yes > None 15 3 > Yes > No > Yes > None 16 9 No > No > Yes > Query Plan needs Optimization > 17 10 > No > No > Yes > Query Plan needs Optimization > 18 8 > No > No > Yes > Preston’s Hyracks Rule 19 19 > No > No > Yes > star(*) needs implementation otherwise gives the right result 20 18 Does > not Need Work Right Now > > > > Sent with Mixmax > <https://mixmax.com/s/79uMSuhLo9LCHg4rC?utm_source=mixmax&utm_medium=email&utm_campaign=signature_link&utm_content=sent_with_mixmax> >
