Thanks, that worked like a charm.
On Fri, May 19, 2017 at 2:23 PM, Justin Makeig
wrote:
> First, why are you working with "stand-alone [un-sic.] properties
> documents"? Could your implementation be simplified by storing the
> properties in their own documents? There's no real advantage to a
> p
First, why are you working with "stand-alone [un-sic.] properties documents"?
Could your implementation be simplified by storing the properties in their own
documents? There's no real advantage to a properties fragment, other than being
able to access it with the same URI as its related document
I'm doing some work with stand-along properties documents, and I want to be
able to delete them. I know I can delete all the properties with a
xdmp:document-set-properties($uri, ())
but that leaves an empty properties document hanging around. Is there a
way to delete it?
Thanks,
Steve
_
Hi,
I've created a range index on ptype and ran the below queries and I am
getting the difference in count. What could be the reason? Any advice?
// This one is getting lesser results
cts.estimate(cts.andQuery([cts.jsonPropertyRangeQuery('ptype', "=",
"25"),cts.collectionQuery(["COLLECTION-1"])]
I don't see this code anywhere creating any log files nor connecting the out
stream to any logging framework. To see the contents of "out", you'll need to
write them to a file, or print them to standard out, or connect a logging
framework to do that for you. All RequestLogger is trying to do i
We tried different ways:
1.
ByteArrayOutputStream out = new ByteArrayOutputStream();
RequestLogger logger = databaseClient.newLogger(out);
xmlDocumentManager.startLogging(logger);
try {
out.write("Test!".getBytes());
out.flush();
} catch (IOException e) {
e.printStackTrace();
}
Docum