It looks like your only option then is to use two separate scripts. It's
not ideal because you have twice the I/O, but it should work.
P.S. make sure to guy reply all so the list is kept in the loop.
On Jan 15, 2015 11:41 PM, Vishnu Viswanath vishnu.viswanat...@gmail.com
wrote:
Thanks Pradeep
Thanks,
Well I think that will be my final option. Right now I am running the script
twice and is ok for my performance requirement. When the amount of data
increases I might have to write a custom store function.
Vishnu Viswanath
On 16-Jan-2015, at 13:51, Pradeep Gollakota
Thanks
SET sets the SOLR collection name. When the STORE is invoked, the data will be
ingested into the collection name set before.
So, the problem must be because the second set is overriding the collection
name and the STORE is failing.
Is there any way to overcome this? Because most of
Just out of curiosity, why are you using SET to set the solr collection?
I'm not sure if you're using an out of the box Load/Store Func, but if I
were to design it, I would use the location of a Load/Store Func to
specify which solr collection to write to.
Is it possible for you to redesign this
Hi All,
I am in indexing data into solr using pig script.
I have two such scripts, and I tried combining these two scripts into a
single one.
i.e., i have script 1 that does
a)SET solr collection info for collection 1
b)LOAD data
c)FILTER data for SOLR collection number 1
What does SET do for Solr? Pig pre-processes all the set commands in the
entire script before executing any query, and values are overwritten if the
same key is set more than once. In your example, you have two set commands.
If you're thinking that different values will be applied in each section,
