Yes, RecordLoader adds an automatic collection that is determined at
startup based on epoch seconds. This gives every RecordLoader batch its
own unique id, which can be very useful in many situations.
I would recommend that you leave this feature alone: in most situations
it doesn't use any significant space, because collections are cheap to
store. I'm very liberal with collections: I add them to documents
whenever I think they might possibly be useful later on.
But perhaps, after thinking about the cheapness of collections and their
potential value, you will still want to omit the RecordLoader batch
collection. If so, please explain your use-case more fully, so that I
can understand why an extra collection on every document is a problem
for you.
thanks,
-- Mike
On 2009-09-05 14:23, Jakob Fix wrote:
Hi,
am I correct to assume that the RecordLoader does add some kind of
default collection to each document it adds to a database? I have
observed that all files added have a collection name like this
"com.marklogic.ps.RecordLoader.1252184760899". I read through the
RecordLoader's README file, and the OUTPUT_COLLECTIONS' default value
is null.
Is there a way not to generate this collection?
the configuration properties in this scenario used are:
CONNECTION_STRING=xcc://admin:[email protected]:8090
INPUT_PATH=c:/users/jakob/downloads/ilibrary-ftp.zip
INPUT_STRIP_PREFIX=ilibrary-ftp/ilibrary-ftp/
OUTPUT_COLLECTIONS=ilibrary
SKIP_EXISTING=true
THREADS=4
MarkLogic version is 4.1-1. RecordLoader is version 2009-09-01.1 on 1.6.0_14
_______________________________________________
General mailing list
[email protected]
http://xqzone.com/mailman/listinfo/general
_______________________________________________
General mailing list
[email protected]
http://xqzone.com/mailman/listinfo/general
