Ok, so we may want to add a little xdmp:sleep() after the document insert
instruction I guess. Thanks for your help.
cheers,
Jakob.
On Tue, May 6, 2014 at 5:53 PM, John Snelson wrote:
> Triple index updates are transactional, so you can see them as soon as
> the inserting transaction has comple
HI.
This might be a starting point for you:
It is a draft guideline of an XML representation of YAML - called YAXML.
http://yaml.org/xml.html
The sample shows the other way around - XML ->xslt -> yaml, but it does
outline how the various parts of a YAML file are represented in XML. So,
if you
MarkLogic does not ingest YAML natively. However, doing a client-side
conversion to XML before inserting should be pretty straightforward and
lossless. What does your current (or planned) ingestion process look like? With
a little more information about your environment, someone might be able to
Triple index updates are transactional, so you can see them as soon as
the inserting transaction has completed. I suspect you're seeing a race
conditions with the inserting transaction.
John
On 06/05/14 16:22, Jakob Fix wrote:
> John,
>
> Maybe a misunderstanding in my message: We're inserting
John,
Maybe a misunderstanding in my message: We're inserting the XML document
which triggers the pre-commit trigger that generates the triple document in
a *separate transaction from the test itself*, in order to be able to query
it. For this to work, we're inserting the document via an HTTP POST
On 06/05/14 15:17, Jakob Fix wrote:
> we are doing xray unit testing for our application, and one of the
> issues we run into occasionally is that even though we know that triples
> have been created and stored as triple documents, they are not always
> (but sometimes) found when executing a sparql
Hello,
we are doing xray unit testing for our application, and one of the issues
we run into occasionally is that even though we know that triples have been
created and stored as triple documents, they are not always (but sometimes)
found when executing a sparql query in the same test. by the way,
November only has 30 days. You need to cleanup your data.
---
Ron Hitchens {r...@overstory.co.uk} +44 7879 358212
On May 6, 2014, at 11:47 AM, amit gope wrote:
> Hello All,
>
> I am running my ingestion on a ML 5.0-4.1. I have this element-range-index
> enabled for a particular field da
Does MarkLogic support YAML for ingestion? Can someone recommend best way to
ingest YAML docs
Sent from my iPhone
___
General mailing list
General@developer.marklogic.com
http://developer.marklogic.com/mailman/listinfo/general
Hi Damon
I am using this particular condition to exclude some of the fragments.
Path range index is not allowing me to use wildcard so I have to supply list of
values instead of specifying a wildcard like *.
Even my stats show when we supply more values it taking more time than expected
or con
Hello All,
I am running my ingestion on a ML 5.0-4.1. I have this element-range-index
enabled for a particular field date. So if I pass the date as
"2014-11-31", it shouts for invalid lexical value.
I know that ML 6.0 onwards we have this option where we can mention the
range index to either "ign
11 matches
Mail list logo
