Re: DIH use of the ?command=full-import entity= command option

2009-03-15 Thread Shalin Shekhar Mangar
On Fri, Mar 13, 2009 at 9:56 PM, Jon Baer jonb...@gmail.com wrote:

 Bare in mind (and correct me if Im wrong) but a full-import is still a
 full-import no matter what entity you tack onto the param.

 Thus I think clean=false should be appended (a friend starting off in Solr
 was really confused by this + could not understand why it did a delete on
 all documents).

 Im not sure if that is clearly stated in the Wiki ...


Yes it is confusing and even more now that we have preImportDeleteQuery.

For a full-import command, the default is clean=true. If clean=false is
specified, then no cleanup is done (not even pre/postImportDeleteQuery).
Even if there is a pre/postImportDeleteQuery, if the first root entity does
not have a preImportDeleteQuery then all documents are deleted (which I
guess is a bug). For a delta-import command, the default is clean=false (and
no pre/postImportDeleteQuery is run).

I think we should open an issue to figure out and implement an acceptable
behavior before we release 1.4
-- 
Regards,
Shalin Shekhar Mangar.


Re: DIH use of the ?command=full-import entity= command option

2009-03-15 Thread Jon Baer
I think it could be as simple as if you have +1 entities in the param  
that clean=false as well (because you are specifically interested in  
just targeting that entity import) ...


- Jon

On Mar 15, 2009, at 3:07 AM, Shalin Shekhar Mangar wrote:


On Fri, Mar 13, 2009 at 9:56 PM, Jon Baer jonb...@gmail.com wrote:

Bare in mind (and correct me if Im wrong) but a full-import is  
still a

full-import no matter what entity you tack onto the param.

Thus I think clean=false should be appended (a friend starting off  
in Solr
was really confused by this + could not understand why it did a  
delete on

all documents).

Im not sure if that is clearly stated in the Wiki ...



Yes it is confusing and even more now that we have  
preImportDeleteQuery.


For a full-import command, the default is clean=true. If clean=false  
is
specified, then no cleanup is done (not even pre/ 
postImportDeleteQuery).
Even if there is a pre/postImportDeleteQuery, if the first root  
entity does
not have a preImportDeleteQuery then all documents are deleted  
(which I
guess is a bug). For a delta-import command, the default is  
clean=false (and

no pre/postImportDeleteQuery is run).

I think we should open an issue to figure out and implement an  
acceptable

behavior before we release 1.4
--
Regards,
Shalin Shekhar Mangar.




Re: DIH use of the ?command=full-import entity= command option

2009-03-13 Thread Jon Baer
Bare in mind (and correct me if Im wrong) but a full-import is still  
a full-import no matter what entity you tack onto the param.


Thus I think clean=false should be appended (a friend starting off in  
Solr was really confused by this + could not understand why it did a  
delete on all documents).


Im not sure if that is clearly stated in the Wiki ...

- Jon

On Mar 13, 2009, at 1:34 AM, Shalin Shekhar Mangar wrote:

On Fri, Mar 13, 2009 at 10:44 AM, Fergus McMenemie  
fer...@twig.me.ukwrote:



If my data-config.xml contains multiple root level entities
what is the expected action if I call full-import without an
entity=XXX sub-command?

Does it process all entities one after the other or only the
first? (It would be useful IMHO if it only did the first.)



It processes all entities one after the other. If you want to import  
only

one, use the entity parameter.

--
Regards,
Shalin Shekhar Mangar.




DIH use of the ?command=full-import entity= command option

2009-03-12 Thread Fergus McMenemie
Hello,

Can anybody describe the intended purpose, or provide a 
few examples, of how the DIH entity= command option works.

Am I supposed to build a data-conf.xml file which contains
many different alternate entities.. or 

Regards 
-- 

===
Fergus McMenemie   Email:fer...@twig.me.uk
Techmore Ltd   Phone:(UK) 07721 376021

Unix/Mac/Intranets Analyst Programmer
===


Re: DIH use of the ?command=full-import entity= command option

2009-03-12 Thread Paul Libbrecht
Wouldn't an entity be something such as a stream, or DB, a manifest- 
channel?


The name source would be better to me but... there's the sQL data- 
sources.


paul


Le 12-mars-09 à 22:47, Fergus McMenemie a écrit :

Can anybody describe the intended purpose, or provide a
few examples, of how the DIH entity= command option works.

Am I supposed to build a data-conf.xml file which contains
many different alternate entities.. or 




smime.p7s
Description: S/MIME cryptographic signature


Re: DIH use of the ?command=full-import entity= command option

2009-03-12 Thread Shalin Shekhar Mangar
On Fri, Mar 13, 2009 at 3:17 AM, Fergus McMenemie fer...@twig.me.uk wrote:

 Hello,

 Can anybody describe the intended purpose, or provide a
 few examples, of how the DIH entity= command option works.

 Am I supposed to build a data-conf.xml file which contains
 many different alternate entities.. or 


With the entity parameter you can specify the name of any root entity and
import only that one. You can specify multiple entity parameters too. For
example:
/dataimport?command=full-importentity=xentity=y

You may need to specify preImportDeleteQuery separately on each entity to
make sure all documents are not deleted.
-- 
Regards,
Shalin Shekhar Mangar.


Re: DIH use of the ?command=full-import entity= command option

2009-03-12 Thread Fergus McMenemie
If my data-config.xml contains multiple root level entities
what is the expected action if I call full-import without an
entity=XXX sub-command?

Does it process all entities one after the other or only the
first? (It would be useful IMHO if it only did the first.)

On Fri, Mar 13, 2009 at 3:17 AM, Fergus McMenemie fer...@twig.me.uk wrote:

 Hello,

 Can anybody describe the intended purpose, or provide a
 few examples, of how the DIH entity= command option works.

 Am I supposed to build a data-conf.xml file which contains
 many different alternate entities.. or 


With the entity parameter you can specify the name of any root entity and
import only that one. You can specify multiple entity parameters too. For
example:
/dataimport?command=full-importentity=xentity=y

You may need to specify preImportDeleteQuery separately on each entity to
make sure all documents are not deleted.
-- 
Regards,
Shalin Shekhar Mangar.

-- 

===
Fergus McMenemie   Email:fer...@twig.me.uk
Techmore Ltd   Phone:(UK) 07721 376021

Unix/Mac/Intranets Analyst Programmer
===


Re: DIH use of the ?command=full-import entity= command option

2009-03-12 Thread Shalin Shekhar Mangar
On Fri, Mar 13, 2009 at 10:44 AM, Fergus McMenemie fer...@twig.me.ukwrote:

 If my data-config.xml contains multiple root level entities
 what is the expected action if I call full-import without an
 entity=XXX sub-command?

 Does it process all entities one after the other or only the
 first? (It would be useful IMHO if it only did the first.)


It processes all entities one after the other. If you want to import only
one, use the entity parameter.

-- 
Regards,
Shalin Shekhar Mangar.