Member since
05-28-2016
14
Posts
5
Kudos Received
0
Solutions
12-28-2016
06:27 PM
I looked through the commit history for 0.10.x (Storm), don't see this line marked as INFO level.
The line is just a constructor initialization message therefore you can ignore it.
... View more
02-16-2017
07:45 PM
Can you explain what does set hive.mv.thread=0 does? I assume it removes parallelism option,does that reduce performance of the insert query.
... View more
11-15-2016
03:43 PM
1 Kudo
You can try what @Rajkumar Singh has recommended. At times, the error is also temporary in nature, so trying to login again to ambari might help, unless you have already tried that.
... View more
06-09-2016
10:27 AM
3 Kudos
what version of hiveserver2 you are running with? it seems that you are trying to connect with old version of thrift client to the newer version of hiveserver2. can you try to check the the libthrift api version of your hive-client vs hive-server. if there is a mismatch then you are not able to connect with hive-server as it is known issue with hive. see this https://issues.apache.org/jira/browse/HIVE-6050
... View more
06-09-2016
06:45 PM
Rajkumar, Have you tried connecting directly with the hive jdbc driver? I'm suspecting it's a jar conflict somewhere. Here's my hive driver config in IntelliJ, obviously took the shotgun approach and added all client jar but the main required are hive-common, hive-jdbc.
... View more
06-02-2016
04:05 PM
my zk nodes were down, restarting zk nodes and nimbus help me.
... View more
06-01-2016
12:17 PM
3 Kudos
if you commit the offset based on timestamp you can start consuming from kafka at next batch cycle like this --commit last consumed
consumer = KafkaConsumer(bootstrap_servers='localhost:9092') tp = TopicPartition(topic, partition)
consumer.seek(tp, end)
consumer.commit()
--now start consuming offset from Kafka when the job restarts at the next batch cycle:
consumer.assign([tp])
start = consumer.committed(tp)
... View more
06-07-2017
09:08 PM
@Andrew Grande, @Rajkumar Singh
I am trying to make the -c work with Flux and the exec-maven-plugin: call mvn compile exec:java -Dexec.args="--local --sleep 400000 --resource /topology.yaml -c foo.bar=1"
, but I get: [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.4.0:java (default-cli) on project StorageTopology: An exception occured while executing the Java class. null: InvocationTargetException: Unrecognized option: -c -> [Help 1] Does this only work with storm jar submission? Can I make it work with the exec maven plugin? Thx, Mauro.
... View more