I don't think you can disable test cases on the fly in JUnit. You will need
to add @Ignore annotation and recompile the test file. Correct me if I am
wrong.
On Thu, Jan 15, 2015 at 6:55 PM, lulynn_2008 lulynn_2...@163.com wrote:
Hi All,
There are multiple tests in one Test* file. Is there a
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
If you're using maven AND using surefire plugin 2.7.3+ AND using Junit 4,
then you can do this by specifying -Dtest=TestClass#methodName
ref:
http://maven.apache.org/surefire/maven-surefire-plugin/examples/single-test.html
On Thu, Jan 15, 2015 at 8:02 PM, Cheolsoo Park piaozhe...@gmail.com
Hi All,
There are multiple tests in one Test* file. Is there a way to just run only one
pointed test?
Thanks
Hi,
I have a hive table with a column which was changed its name. Pig is not
able to load data from this column, it is all empty.
Any ideas how to fix it?
BR,
Patcharee
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,
