Can’t see any output … what format should it be in?
> On Sep 10, 2015, at 11:55 AM, Steven Jacobs <[email protected]> wrote:
>
> Here is a full output of my problem, in case anyone has new advice:
>
>
>
> On Thu, Sep 10, 2015 at 11:09 AM, Steven Jacobs <[email protected]
> <mailto:[email protected]>> wrote:
> Unfortunately my big blocker is that VXQuery will not run on my machine. It
> seems that no matter what I try, Java still disagrees with me. I have merged
> my code with current master, but I can't test it. I also didn't document it
> well originally, so getting it running is a bit of a precursor to getting
> good documentation on how exactly it works.
> Steven
>
> On Thu, Sep 10, 2015 at 10:41 AM, Till Westmann <[email protected]
> <mailto:[email protected]>> wrote:
> Yes, some description would be nice. Reading this e-mail I’m specifically
> interested in the lifecycle of the data and the indexes.
> So far all lifecycle management happens outside of the query processor and
> the query processor cannot handle side-effecting operations (like
> "create-index”). So I’m wondering how we should do that.
>
> Cheers,
> Till
>
> > On Sep 10, 2015, at 10:11 AM, Preston Carman <[email protected]
> > <mailto:[email protected]>> wrote:
> >
> > Hi Steven,
> >
> > What is the status of the indexing code merge? Also, could you describe the
> > set up? As I understand it, a new expression (such as "create-index")
> > imports a collection of XML documents into the index. The index has key
> > value pairs based on the full path (key) to a element node (value) for each
> > XML document. Is this correct? How are the key and value stored? Are these
> > strings or XDM instances? Once the index is created, you can use a new
> > collection function based on the index (such as "collection-using-index").
> > Please fill in the gaps.
> >
> > Aloha,
> > Preston
>
>
>
