Another update that I forgot to include! 5) Descendant-or-self function now accepts filter. However, I could not test this because there is no implementation for the rewrite rule yet that bypasses the conversion to child path steps. Once discussed, I will be able to implement this rule and hopefully this particular issue will highly optimize the function descendant-or-self. This is because, as of now, the function returns all the nodes starting from root node according to the descendants function. Then it applies child filter on it. ᐧ
On Wed, Jul 1, 2015 at 11:46 AM, Shivani Mall <[email protected]> wrote: > Hey all, > > Waiting for an official weekly update for all past weeks? Here is one that > extensively covers all that I have been working on these past weeks :) > > 1) Doc Rewrite Rule fixed and updated. > > The issue can be found here: > https://issues.apache.org/jira/browse/VXQUERY-142 > The patch can be found here: https://github.com/apache/vxquery/pull/8 > > This test fixed one of the previous issues caught with the test suite. > More importantly, it made numerous XQTS tests to pass. These failed because > there was the string entered in the doc function to an absolute/relative > path (found in sourceFileMap) was not handled correctly. > > 2) Conversion to Algebricks Rewrite Rule. > > This issue can be found here: > https://issues.apache.org/jira/browse/VXQUERY-160 which blocked > https://issues.apache.org/jira/browse/VXQUERY-161 > The patch can be found here: https://github.com/apache/vxquery/pull/10 > > This issue should also fix Query 8 with Preston's rewrite rules. This > implementation of this rule was not handling general comparisons and value > comparisons in runtime (gt, lt, = < > etc) functions correctly. Again, this > made numerous XQTS Tests to pass. > > 3) Missing Node-Before-After Function > > This issue can be found here: > https://issues.apache.org/jira/browse/VXQUERY-146 > The patch can be found here: https://github.com/shivani1494/vxquery/pull/1 > > This issue fixed the above XMark issue. The implementation of the function > was missing. Made about 50 XQTS tests to pass. > > 4) Curly Braces Error > > The issues can be found here: > https://issues.apache.org/jira/browse/VXQUERY-158 and > https://issues.apache.org/jira/browse/VXQUERY-96 > Issue has been updated with my use cases. The patch is under progress. > This was initially assumed to be an XMark issue. However, as it turned out, > it was not. Nevertheless, once resolved, the patch will likely make more > XQTS tests to pass. > > Preston has exact numbers of all tests passing as a result of patches. I > am sure he can confirm the numbers. > > > Thank you, > Shivani > > > > > > ᐧ > > On Tue, Jun 2, 2015 at 11:39 AM, Shivani Mall <[email protected]> wrote: > >> Hey all, >> >> 1) All this while, I was working on extending my test suite to include a >> log file that displays queries, logical plan, optimized plan and results. I >> have made the changes to the code and will push it today. Also, the file >> should now be available on the ticket that I created last week. >> https://issues.apache.org/jira/browse/VXQUERY-145 >> >> 2) This week I am working to write a Doc rewrite rule that maps an >> expression to a file in the document function. This will also be my >> starting point into writing rewrite rules. >> >> 3)This week we will also be analyzing the query plans to and decide the >> problems we will be dealing with over the next few weeks. >> >> Thank you, >> Shivani >> >> ᐧ >> >> On Tue, May 26, 2015 at 4:45 PM, Shivani Mall <[email protected]> wrote: >> >>> Hey all, >>> >>> This is what I have been doing so far: >>> >>> 1)Code updated to display Logical and Query Plans. However, it needs to >>> be re-architectured before I can push it to github. >>> >>> 2)Creating a log file to display logical and query plans for XMark >>> Queries. Later this week the file can be found here: >>> https://issues.apache.org/jira/browse/VXQUERY-145 >>> >>> Thank you, >>> Shivani >>> >>> ᐧ >>> >>> On Thu, May 21, 2015 at 8:57 PM, Till Westmann <[email protected]> wrote: >>> >>>> Thanks! >>>> Is there a good way to put GH’s pull requests to use? >>>> >>>> Thanks, >>>> Till >>>> >>>> > On May 20, 2015, at 9:42 PM, Steven Jacobs <[email protected]> wrote: >>>> > >>>> > The simplest way (based on the experience with Efi's change) is to add >>>> > the Github >>>> > site as a remote, merge locally with master, then push. >>>> > Steven >>>> > >>>> > On Wednesday, May 20, 2015, Till Westmann <[email protected]> wrote: >>>> > >>>> >> Nice. Thanks! >>>> >> >>>> >> >>>> >> Preston, Steven, is there a particularly easy way to merge changes >>>> that >>>> >> are available on GitHub into our repository? >>>> >> >>>> >> Thanks, >>>> >> Till >>>> >> >>>> >> On 20 May 2015, at 13:51, Shivani Mall wrote: >>>> >> >>>> >> This Week: >>>> >>> >>>> >>> 1)XMark Documentation Completed which can be found here: >>>> >>> >>>> >>> >>>> https://github.com/shivani1494/vxquery/commit/dd7cddd49a471cd5c11588c262037b0276348611 >>>> >>> >>>> >>> 2)Updating Code to show Logical and Optimized Query Plans for XTest >>>> since >>>> >>> this option is currently avaiable only for VXQuery >>>> >>> >>>> >>> ᐧ >>>> >>> >>>> >>> On Wed, May 20, 2015 at 1:51 PM, Shivani Mall <[email protected]> >>>> wrote: >>>> >>> >>>> >>> Last Week: >>>> >>>> >>>> >>>> 1) Completing XMark Documentation. >>>> >>>> >>>> >>>> >>>> >>>> ᐧ >>>> >>>> >>>> >>>> On Mon, May 4, 2015 at 4:51 PM, Shivani Mall <[email protected]> >>>> wrote: >>>> >>>> >>>> >>>> Last week: >>>> >>>>> >>>> >>>>> 1) Understood XQuery Data Model, multiple wrappers around XML >>>> document, >>>> >>>>> SequencePointable, the need for builders and a little bit of data >>>> flow >>>> >>>>> and >>>> >>>>> operators. Thanks to Preston for great explanations! >>>> >>>>> >>>> >>>>> 2)Documentation: SequencePointable structure, byte array break >>>> down of a >>>> >>>>> basic XML Doc. >>>> >>>>> >>>> >>>>> >>>> >>>>> ᐧ >>>> >>>>> >>>> >>>>> >>>> >>>> >>>> >>>> >>>> >>>> >>> >> >
