[GitHub] [metron] sardell opened a new pull request #1529: METRON-2281: [UI] Eliminate Create new/merge screen
sardell opened a new pull request #1529: METRON-2281: [UI] Eliminate Create
new/merge screen
URL: https://github.com/apache/metron/pull/1529
## Contributor Comments
Currently in this feature implementation, when the user drags a standalone
parser and drops it to sub-parser of a group, there is a choice with two
options.
One is to merge the standalone parser into the group. Other is to create a
new group out of the two involved parsers. This is only supported by the
backend if we remove the originally grouped parser from its previous group (as
the first step of the transaction) and then create a new one (second step of
the transaction), which does not currently exist.
By eliminating the create new/merge screen, we no longer have to worry about
managing this transactional operation. A user is already able to create a new
group with two ungrouped parsers.
## Pull Request Checklist
Thank you for submitting a contribution to Apache Metron.
Please refer to our [Development
Guidelines](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61332235)
for the complete guide to follow for contributions.
Please refer also to our [Build Verification
Guidelines](https://cwiki.apache.org/confluence/display/METRON/Verifying+Builds?show-miniview)
for complete smoke testing guides.
In order to streamline the review of the contribution we ask you follow
these guidelines and ask you to double check the following:
### For all changes:
- [ ] Is there a JIRA ticket associated with this PR? If not one needs to be
created at [Metron
Jira](https://issues.apache.org/jira/browse/METRON/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel).
- [ ] Does your PR title start with METRON- where is the JIRA
number you are trying to resolve? Pay particular attention to the hyphen "-"
character.
- [ ] Has your PR been rebased against the latest commit within the target
branch (typically master)?
### For code changes:
- [ ] Have you included steps to reproduce the behavior or problem that is
being changed or addressed?
- [ ] Have you included steps or a guide to how the change may be verified
and tested manually?
- [ ] Have you ensured that the full suite of tests and checks have been
executed in the root metron folder via:
```
mvn -q clean integration-test install &&
dev-utilities/build-utils/verify_licenses.sh
```
- [ ] Have you written or updated unit tests and or integration tests to
verify your changes?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] Have you verified the basic functionality of the build by building and
running locally with Vagrant full-dev environment or the equivalent?
### For documentation related changes:
- [ ] Have you ensured that format looks appropriate for the output in which
it is rendered by building and verifying the site-book? If not then run the
following commands and the verify changes via
`site-book/target/site/index.html`:
```
cd site-book
mvn site
```
- [ ] Have you ensured that any documentation diagrams have been updated,
along with their source files, using [draw.io](https://www.draw.io/)? See
[Metron Development
Guidelines](https://cwiki.apache.org/confluence/display/METRON/Development+Guidelines)
for instructions.
Note:
Please ensure that once the PR is submitted, you check travis-ci for build
issues and submit an update to your PR as soon as possible.
It is also recommended that [travis-ci](https://travis-ci.org) is set up for
your personal repository such that your branches are built there before
submitting a pull request.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
[jira] [Created] (METRON-2281) [UI] Eliminate Create new/merge screen
Shane Ardell created METRON-2281: Summary: [UI] Eliminate Create new/merge screen Key: METRON-2281 URL: https://issues.apache.org/jira/browse/METRON-2281 Project: Metron Issue Type: Sub-task Reporter: Shane Ardell When the user drags a standalone parser and drops it to sub-parser of a group there is a choice with two options. One is to "merge" the standalone parser into the group. Other is to "create new" group out of the two involved parsers. This is only supported by the backend if we remove the originally grouped parser from its previous group (as the first step of the transaction) and then create a new one (second step of the transaction). Due to the massive complexities that come with this and the fact that there are other ways to create a new group available to the user (and therefore does not add value to the user), those of us working on this feature have decided to remove it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (METRON-2251) Update with the latest master branch
[ https://issues.apache.org/jira/browse/METRON-2251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell reassigned METRON-2251: Assignee: Shane Ardell > Update with the latest master branch > > > Key: METRON-2251 > URL: https://issues.apache.org/jira/browse/METRON-2251 > Project: Metron > Issue Type: Sub-task >Reporter: Shane Ardell >Assignee: Shane Ardell >Priority: Major > Time Spent: 1h 20m > Remaining Estimate: 0h > > This branch is really out-of-date with the current master branch of Metron. > In addition to resolving conflicts, both UIs are up to Angular 7, which means > we have to update code to accommodate for breaking changes, stricter type > checking, etc. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (METRON-2280) PCAP queries no longer work
Michael Miklavcic created METRON-2280:
-
Summary: PCAP queries no longer work
Key: METRON-2280
URL: https://issues.apache.org/jira/browse/METRON-2280
Project: Metron
Issue Type: Bug
Reporter: Michael Miklavcic
Run a PCAP query and get the following exception
{code:java}
$METRON_HOME/bin/pcap_query.sh fixed -st 20191009 -df "MMdd" -p 6 -rpf 500
Exception in thread "main" java.lang.NoClassDefFoundError:
org/apache/metron/stellar/common/utils/ConversionUtils
at
org.apache.metron.common.configuration.ConfigOption.get(ConfigOption.java:81)
at org.apache.metron.pcap.mr.PcapJob.submit(PcapJob.java:219)
at org.apache.metron.pcap.query.PcapCli.run(PcapCli.java:107)
at org.apache.metron.pcap.query.PcapCli.main(PcapCli.java:55)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.apache.hadoop.util.RunJar.run(RunJar.java:318)
at org.apache.hadoop.util.RunJar.main(RunJar.java:232)
Caused by: java.lang.ClassNotFoundException:
org.apache.metron.stellar.common.utils.ConversionUtils
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
... 10 more
{code}
This appears to have been introduced in
https://github.com/apache/metron/pull/1436 and missed in testing.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[GitHub] [metron] mmiklavc commented on issue #1523: METRON-2232 Upgrade to Hadoop 3.1.1
mmiklavc commented on issue #1523: METRON-2232 Upgrade to Hadoop 3.1.1 URL: https://github.com/apache/metron/pull/1523#issuecomment-540209080 Almost finished with testing. Ran into a Stellar classpath issue in the PCAP query jobs. This looks like another bug that is also in master missed during testing for https://github.com/apache/metron/pull/1436 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [metron] mmiklavc commented on issue #1523: METRON-2232 Upgrade to Hadoop 3.1.1
mmiklavc commented on issue #1523: METRON-2232 Upgrade to Hadoop 3.1.1
URL: https://github.com/apache/metron/pull/1523#issuecomment-540208150
## Testing
Adapted from a few places
* https://gist.github.com/nickwallen/ed67fdc8b399f6db5fa4901b07fc3fff
*
https://cwiki.apache.org/confluence/display/METRON/2016/04/25/Metron+Tutorial+-+Fundamentals+Part+1%3A+Creating+a+New+Telemetry
### Preliminaries
Test using the centos7 development environment.
* Start up the centos7 dev environment.
```
cd metron-deployment/development/centos7
vagrant destroy -f
vagrant up
# ssh into the box as root@node1, pwd=vagrant
```
* Run as root is fine
* Set env vars
```
source /etc/default/metron
```
* Root user needs a home dir in HDFS. You can do that as follows:
```
sudo -u hdfs hdfs dfs -mkdir /user/root
sudo -u hdfs hdfs dfs -chown root:root /user/root
```
* Download the Alexa top 1m data set
```
cd ~/
wget http://s3.amazonaws.com/alexa-static/top-1m.csv.zip
unzip top-1m.csv.zip
```
* Stage import file
```
head -n 1 top-1m.csv > top-10k.csv
hdfs dfs -put top-10k.csv /tmp
```
* Truncate hbase
```
echo "truncate 'enrichment'" | hbase shell
```
### Basic Indexing and Enrichment
Ensure that we can continue to parse, enrich, and index telemetry. Verify
data is flowing through the system, from parsing to indexing
1. Open Ambari and navigate to the Metron service
http://node1:8080/#/main/services/METRON/summary
1. Open the Alerts UI. Verify alerts show up in the main UI - click the
search icon (you may need to wait a moment for them to appear)
1. Go to the Alerts UI and ensure that an ever increasing number of
telemetry from Bro, Snort, and YAF are visible by watching the total alert
count increase over time.
1. Ensure that geoip enrichment is occurring. The telemetry should contain
fields like `enrichments:geo:ip_src_addr:location_point`.
1. Head back to Ambari and select the Kibana service
http://node1:8080/#/main/services/KIBANA/summary
1. Open the Kibana dashboard via the "Metron UI" option in the quick links
1. Verify the dashboard is populating
### Batch Indexing
1. Use the Alerts UI to retrieve a rough count of the number of Bro messages
that have been indexed.
1. Retrieve the number of Bro messages that have been indexed in HDFS.
```
[root@node1 0.7.2]# hdfs dfs -cat /apps/metron/indexing/indexed/bro/* |
wc -l
2785
```
1. The number of messages indexed in HDFS should be close to the number
indexed to the search indices.
### Streaming Enrichments
Adapted from the [Metron Tutorial
Series](https://cwiki.apache.org/confluence/display/METRON/2016/06/16/Metron+Tutorial+-+Fundamentals+Part+6%3A+Streaming+Enrichment).
1. Launch the Stellar REPL.
```
cd $METRON_HOME
$METRON_HOME/bin/stellar -z $ZOOKEEPER
```
1. Define the streaming enrichment and save it as a new source of
telemetry.
```
[Stellar]>>> conf := SHELL_EDIT(conf)
{
"parserClassName": "org.apache.metron.parsers.csv.CSVParser",
"writerClassName":
"org.apache.metron.writer.hbase.SimpleHbaseEnrichmentWriter",
"sensorTopic": "user",
"parserConfig": {
"shew.table": "enrichment",
"shew.cf": "t",
"shew.keyColumns": "ip",
"shew.enrichmentType": "user",
"columns": {
"user": 0,
"ip": 1
}
}
}
[Stellar]>>>
[Stellar]>>> CONFIG_PUT("PARSER", conf, "user")
```
1. Go to the Management UI and start the new parser called 'user'.
1. Create some test telemetry.
```
[Stellar]>>> msgs := ["user1,192.168.1.1", "user2,192.168.1.2",
"user3,192.168.1.3"]
[user1,192.168.1.1, user2,192.168.1.2, user3,192.168.1.3]
[Stellar]>>> KAFKA_PUT("user", msgs)
3
[Stellar]>>> KAFKA_PUT("user", msgs)
3
[Stellar]>>> KAFKA_PUT("user", msgs)
3
```
1. Ensure that the enrichments are persisted in HBase.
```
[Stellar]>>> ENRICHMENT_GET('user', '192.168.1.1', 'enrichment', 't')
{original_string=user1,192.168.1.1,
guid=a6caf3c1-2506-4eb7-b33e-7c05b77cd72c, user=user1, timestamp=1551813589399,
source.type=user}
[Stellar]>>> ENRICHMENT_GET('user', '192.168.1.2', 'enrichment', 't')
{original_string=user2,192.168.1.2,
guid=49e4b8fa-c797-44f0-b041-cfb47983d54a, user=user2, timestamp=1551813589399,
source.type=user}
[Stellar]>>> ENRICHMENT_GET('user', '192.168.1.3', 'enrichment', 't')
{original_string=user3,192.168.1.3,
[GitHub] [metron] anandsubbu commented on issue #1528: METRON-2279 Unable to Index to Solr with Kerberos
anandsubbu commented on issue #1528: METRON-2279 Unable to Index to Solr with Kerberos URL: https://github.com/apache/metron/pull/1528#issuecomment-540197835 +1, thanks for fix @nickwallen ! I spun up a 5 node Solr cluster, kerberized and was able to see data flowing all the way through without a problem. I did run into a different issue in the process where the enrichment topology--which was running on a non-metron node--did not have the kerberos set up properly. I had to `kinit` on all the nodes in order to get the enrichment topology running properly. This issue can be tracked and addressed separately, though. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [metron] sardell closed pull request #1507: METRON-2251: Update with the latest master branch
sardell closed pull request #1507: METRON-2251: Update with the latest master branch URL: https://github.com/apache/metron/pull/1507 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [metron] mmiklavc commented on issue #1507: METRON-2251: Update with the latest master branch
mmiklavc commented on issue #1507: METRON-2251: Update with the latest master branch URL: https://github.com/apache/metron/pull/1507#issuecomment-540160542 Ok, go for it +1. Thanks @sardell This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Updated] (METRON-2278) "Metron on CentOS 6" Documentation is outdated
[ https://issues.apache.org/jira/browse/METRON-2278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Subhash Jha updated METRON-2278: Description: The documentation for installing java with brew is outdated and no longer support the given command. Firstly, When we are setting up the Vagrant on Mojave MacOS, we are getting error for the java installation part. [https://stackoverflow.com/questions/55834845/unable-to-install-java8-with-homebrew] Instead of running brew cask install caskroom/versions/java8 We have to run, brew cask install homebrew/cask-versions/adoptopenjdk8 Last but not least, the guide for installing the specified version of ansible is also incorrect. We should use '==' instead of '=' while specifying the ansible version, i.e. sudo pip install ansible==2.6.5 was: The documentation for installing java with brew is outdated and no longer support the given command. Firstly, When we are setting up the Vagrant on Mojave MacOS, we are getting error for the java installation part. [https://stackoverflow.com/questions/55834845/unable-to-install-java8-with-homebrew] Instead of running brew cask install caskroom/versions/java8 We have to run, brew cask install homebrew/cask-versions/adoptopenjdk8 Last but not least, the guide for installing the specified version of ansible is also incorrect. We should use '==' instead of '=' while specifying the ansible version, i.e. sudo pip install ansible==2.6.5 > "Metron on CentOS 6" Documentation is outdated > -- > > Key: METRON-2278 > URL: https://issues.apache.org/jira/browse/METRON-2278 > Project: Metron > Issue Type: Improvement >Reporter: Subhash Jha >Priority: Minor > > The documentation for installing java with brew is outdated and no longer > support the given command. > Firstly, When we are setting up the Vagrant on Mojave MacOS, we are getting > error for the java installation part. > [https://stackoverflow.com/questions/55834845/unable-to-install-java8-with-homebrew] > Instead of running > brew cask install caskroom/versions/java8 > We have to run, > brew cask install homebrew/cask-versions/adoptopenjdk8 > > Last but not least, the guide for installing the specified version of ansible > is also incorrect. > We should use '==' instead of '=' while specifying the ansible version, i.e. > sudo pip install ansible==2.6.5 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [metron] nickwallen opened a new pull request #1528: METRON-2279 Unable to Index to Solr with Kerberos
nickwallen opened a new pull request #1528: METRON-2279 Unable to Index to Solr with Kerberos URL: https://github.com/apache/metron/pull/1528 On the HDP 3.1 feature branch the indexing topology is unable to index telemetry to Solr when running in a secure/kerberized environment. ### The Problem ``` 2019-10-09 06:32:33.039 o.a.s.util Thread-7-indexingBolt-executor[3 3] [ERROR] Async loop died! java.lang.NoSuchMethodError: org.apache.http.impl.conn.PoolingHttpClientConnectionManager.setValidateAfterInactivity(I)V at org.apache.solr.client.solrj.impl.HttpClientUtil.createClient(HttpClientUtil.java:277) ~[stormjar.jar:?] at org.apache.solr.client.solrj.impl.HttpClientUtil.createClient(HttpClientUtil.java:328) ~[stormjar.jar:?] at org.apache.solr.client.solrj.impl.HttpClientUtil.createClient(HttpClientUtil.java:266) ~[stormjar.jar:?] at org.apache.solr.client.solrj.impl.HttpClientUtil.createClient(HttpClientUtil.java:253) ~[stormjar.jar:?] at org.apache.metron.solr.writer.SolrClientFactory.create(SolrClientFactory.java:49) ~[stormjar.jar:?] at org.apache.metron.solr.writer.SolrWriter.init(SolrWriter.java:171) ~[stormjar.jar:?] at org.apache.metron.writer.bolt.BulkMessageWriterBolt.prepare(BulkMessageWriterBolt.java:239) ~[stormjar.jar:?] at org.apache.storm.daemon.executor$fn__10219$fn__10232.invoke(executor.clj:810) ~[storm-core-1.2.1.3.1.4.0-315.jar:1.2.1.3.1.4.0-315] at org.apache.storm.util$async_loop$fn__1221.invoke(util.clj:482) [storm-core-1.2.1.3.1.4.0-315.jar:1.2.1.3.1.4.0-315] at clojure.lang.AFn.run(AFn.java:22) [clojure-1.7.0.jar:?] at java.lang.Thread.run(Thread.java:745) [?:1.8.0_112] 2019-10-09 06:32:33.166 o.a.s.d.executor Thread-7-indexingBolt-executor[3 3] [ERROR] java.lang.NoSuchMethodError: org.apache.http.impl.conn.PoolingHttpClientConnectionManager.setValidateAfterInactivity(I)V at org.apache.solr.client.solrj.impl.HttpClientUtil.createClient(HttpClientUtil.java:277) ~[stormjar.jar:?] at org.apache.solr.client.solrj.impl.HttpClientUtil.createClient(HttpClientUtil.java:328) ~[stormjar.jar:?] at org.apache.solr.client.solrj.impl.HttpClientUtil.createClient(HttpClientUtil.java:266) ~[stormjar.jar:?] at org.apache.solr.client.solrj.impl.HttpClientUtil.createClient(HttpClientUtil.java:253) ~[stormjar.jar:?] at org.apache.metron.solr.writer.SolrClientFactory.create(SolrClientFactory.java:49) ~[stormjar.jar:?] at org.apache.metron.solr.writer.SolrWriter.init(SolrWriter.java:171) ~[stormjar.jar:?] at org.apache.metron.writer.bolt.BulkMessageWriterBolt.prepare(BulkMessageWriterBolt.java:239) ~[stormjar.jar:?] at org.apache.storm.daemon.executor$fn__10219$fn__10232.invoke(executor.clj:810) ~[storm-core-1.2.1.3.1.4.0-315.jar:1.2.1.3.1.4.0-315] at org.apache.storm.util$async_loop$fn__1221.invoke(util.clj:482) [storm-core-1.2.1.3.1.4.0-315.jar:1.2.1.3.1.4.0-315] at clojure.lang.AFn.run(AFn.java:22) [clojure-1.7.0.jar:?] at java.lang.Thread.run(Thread.java:745) [?:1.8.0_112] OptionsAttachments ``` ### Why? The method [PoolingHttpClientConnectionManager.setValidateAfterInactivity(int)](https://hc.apache.org/httpcomponents-client-ga/httpclient/apidocs/org/apache/http/impl/conn/PoolingHttpClientConnectionManager.html#setValidateAfterInactivity(int)) is only available from org.apache.httpcomponents:httpclient in versions > 4.4. In `metron-solr-storm` we allow org.apache.solr:solr-solrj version 7.4.0 to pull in org.apache.httpcomponents:httpclient version 4.5.3. When executed in a non-kerberized environment this works just fine. Unfortunately, when kerberized Storm pulls in a slew of additional dependencies at runtime from /usr/hdp/current/storm-client/contrib/storm-autocreds/. This includes httpclient-4.3.6.jar, which does not contain the method mentioned above. We need to relocate the httpclient dependency in the Solr uber jar to prevent Storm from trouncing on this dependency at runtime. ## Testing 1. Spin up the centos7 development environment. 1. Switch the indexer to Solr instead of Elasticsearch by [following these instructions](https://github.com/apache/metron/tree/master/metron-platform/metron-solr/metron-solr-common#installing). 1. Ensure that telemetry is being indexed into Solr. 1. Ensure that the telemetry from Solr is visible in the Alerts UI. 1. Kerberize the environment. 1. Ensure that telemetry is being indexed into Solr after the environment has been kerberized. 1. Ensure that the telemetry from Solr is visible in the Alerts UI. ## Pull Request Checklist Thank you for submitting a contribution to Apache Metron. Please refer to our [Development
[jira] [Created] (METRON-2279) Unable to Index to Solr with Kerberos
Nick Allen created METRON-2279:
--
Summary: Unable to Index to Solr with Kerberos
Key: METRON-2279
URL: https://issues.apache.org/jira/browse/METRON-2279
Project: Metron
Issue Type: Sub-task
Reporter: Nick Allen
Assignee: Nick Allen
On the HDP 3.1 feature branch the indexing topology is unable to index
telemetry to Solr when running in a secure/kerberized environment.
{code:java}
2019-10-09 06:32:33.039 o.a.s.util Thread-7-indexingBolt-executor[3 3] [ERROR]
Async loop died!
java.lang.NoSuchMethodError:
org.apache.http.impl.conn.PoolingHttpClientConnectionManager.setValidateAfterInactivity(I)V
at
org.apache.solr.client.solrj.impl.HttpClientUtil.createClient(HttpClientUtil.java:277)
~[stormjar.jar:?]
at
org.apache.solr.client.solrj.impl.HttpClientUtil.createClient(HttpClientUtil.java:328)
~[stormjar.jar:?]
at
org.apache.solr.client.solrj.impl.HttpClientUtil.createClient(HttpClientUtil.java:266)
~[stormjar.jar:?]
at
org.apache.solr.client.solrj.impl.HttpClientUtil.createClient(HttpClientUtil.java:253)
~[stormjar.jar:?]
at
org.apache.metron.solr.writer.SolrClientFactory.create(SolrClientFactory.java:49)
~[stormjar.jar:?]
at org.apache.metron.solr.writer.SolrWriter.init(SolrWriter.java:171)
~[stormjar.jar:?]
at
org.apache.metron.writer.bolt.BulkMessageWriterBolt.prepare(BulkMessageWriterBolt.java:239)
~[stormjar.jar:?]
at
org.apache.storm.daemon.executor$fn__10219$fn__10232.invoke(executor.clj:810)
~[storm-core-1.2.1.3.1.4.0-315.jar:1.2.1.3.1.4.0-315]
at org.apache.storm.util$async_loop$fn__1221.invoke(util.clj:482)
[storm-core-1.2.1.3.1.4.0-315.jar:1.2.1.3.1.4.0-315]
at clojure.lang.AFn.run(AFn.java:22) [clojure-1.7.0.jar:?]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_112]
2019-10-09 06:32:33.166 o.a.s.d.executor Thread-7-indexingBolt-executor[3 3]
[ERROR]
java.lang.NoSuchMethodError:
org.apache.http.impl.conn.PoolingHttpClientConnectionManager.setValidateAfterInactivity(I)V
at
org.apache.solr.client.solrj.impl.HttpClientUtil.createClient(HttpClientUtil.java:277)
~[stormjar.jar:?]
at
org.apache.solr.client.solrj.impl.HttpClientUtil.createClient(HttpClientUtil.java:328)
~[stormjar.jar:?]
at
org.apache.solr.client.solrj.impl.HttpClientUtil.createClient(HttpClientUtil.java:266)
~[stormjar.jar:?]
at
org.apache.solr.client.solrj.impl.HttpClientUtil.createClient(HttpClientUtil.java:253)
~[stormjar.jar:?]
at
org.apache.metron.solr.writer.SolrClientFactory.create(SolrClientFactory.java:49)
~[stormjar.jar:?]
at org.apache.metron.solr.writer.SolrWriter.init(SolrWriter.java:171)
~[stormjar.jar:?]
at
org.apache.metron.writer.bolt.BulkMessageWriterBolt.prepare(BulkMessageWriterBolt.java:239)
~[stormjar.jar:?]
at
org.apache.storm.daemon.executor$fn__10219$fn__10232.invoke(executor.clj:810)
~[storm-core-1.2.1.3.1.4.0-315.jar:1.2.1.3.1.4.0-315]
at org.apache.storm.util$async_loop$fn__1221.invoke(util.clj:482)
[storm-core-1.2.1.3.1.4.0-315.jar:1.2.1.3.1.4.0-315]
at clojure.lang.AFn.run(AFn.java:22) [clojure-1.7.0.jar:?]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_112]
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (METRON-2278) "Metron on CentOS 6" Documentation is outdated
Subhash Jha created METRON-2278: --- Summary: "Metron on CentOS 6" Documentation is outdated Key: METRON-2278 URL: https://issues.apache.org/jira/browse/METRON-2278 Project: Metron Issue Type: Improvement Reporter: Subhash Jha The documentation for installing java with brew is outdated and no longer support the given command. Firstly, When we are setting up the Vagrant on Mojave MacOS, we are getting error for the java installation part. [https://stackoverflow.com/questions/55834845/unable-to-install-java8-with-homebrew] Instead of running brew cask install caskroom/versions/java8 We have to run, brew cask install homebrew/cask-versions/adoptopenjdk8 Last but not least, the guide for installing the specified version of ansible is also incorrect. We should use '==' instead of '=' while specifying the ansible version, i.e. sudo pip install ansible==2.6.5 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [metron] sardell edited a comment on issue #1527: METRON-2276: [UI] Performance: Switching back from manual filtering fires a "full query"
sardell edited a comment on issue #1527: METRON-2276: [UI] Performance: Switching back from manual filtering fires a "full query" URL: https://github.com/apache/metron/pull/1527#issuecomment-539717767 @ruffle1986 100% agree with everything you say, but I also agree with @tiborm that the proposal of this discussion is out of scope for METRON-2276. > I highly recommend to allocate some time to refactor the "search section" I'm on board with that. It's an area of pain for anyone who touches it. Feel free to start a discussion thread proposing how it should be refactored. > I've also heard rumours about getting rid of the query builder and only allow users to type their own lucine queries manually. This has been mentioned offline as an idea between a few of us, but I don't think anything official has been proposed in a discussion thread yet. I guess it comes down to how much value does the query builder bring users. Maybe we can ask in the user mailing list and the Metron Slack channel to gauge out how important that feature is for users. If users don't find it helpful, I would definitely be on-board with getting rid of it. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
