incubator-stormcrawler: Java topology doesn't read configurations with Storm 2

[x ] Bug report. If you’ve found a bug, please include a test if you can, it makes it a lot easier to fix things. Use the label ‘bug’ on the issue.

I am getting the following :-

16:33:27.858 [Thread-35-spout-executor[12, 12]] ERROR c.d.s.e.p.AbstractSpout - Can't connect to ElasticSearch
java.lang.IllegalArgumentException: hosts must not be null nor empty
        at org.elasticsearch.client.RestClient.builder(RestClient.java:173) ~[stormcrawler-1.0-SNAPSHOT.jar:?]
        at com.digitalpebble.stormcrawler.elasticsearch.ElasticSearchConnection.getClient(ElasticSearchConnection.java:117) ~[stormcrawler-1.0-SNAPSHOT.jar:?]

ElasticSearch is up and running. I cannot find a ‘hosts:’ parameter anywhere and ‘es-conf.yaml’ parameters are set to localhost, or http://locahost:9200

About this issue

Original URL
State: closed
Created 3 years ago
Comments: 22 (13 by maintainers)

Commits related to this issue

READMEs with fix for parsing arguments on command line, fixes #857 — committed to apache/incubator-stormcrawler by jniocheCF 3 years ago
Fix READMEs, see #857 — committed to apache/incubator-stormcrawler by jnioche 3 years ago

Most upvoted comments

insert ‘–’ after ESCrawlTopology

See #774.

sebastian-nagel on Mar 8, 2021

hows that happening ? Is it a bug in storm ?

or a feature? don’t know

as Sebastian pointed out, support for Storm 2 is still experimental. you might be better off using Storm 1

jnioche on Feb 8, 2021

to add to my previous comment: anything starting with ‘-c’ gets removed by Storm 2. great.

jnioche on Feb 8, 2021

Fab, thanks. let me have a look. Judging by the content, the es-conf is the same as the one generated by the archetype

jnioche on Feb 8, 2021