mmiklavc commented on issue #1483: METRON-2217 Migrate current HBase client from HTableInterface to Table URL: https://github.com/apache/metron/pull/1483#issuecomment-525327794 @tigerquoll thanks for the test script feedback! Ultimately, I think it would be nice to get the blog entries added in our use-cases directory where we can track and maintain them more easily. This is a good first step. > Metron tutorial needs updating from the new Kafka client tools. Step 5 needs to be updated to read Kafka via: ${HDP_HOME}/kafka-broker/bin/kafka-console-consumer.sh --bootstrap-server $BROKERLIST --topic squid --from-beginning Updated > Metron tutorial step 5 global.json additional to support squid needs a comma after last square bracket. Not sure what you mean here - this is a snippet to use as guidance to modify the global.json, not replace it. > Metron tutorial Step 5, no spare workers available to run squid topology. Need to add instructions on adding another supervisor slot port. I added instructions to cleanup resources. I'm going to add the same to my test script here. > Metron tutorial part 2. To "Check if Zookeeper enrichment tag was properly populated" command should be changed to ${METRON_HOME}/bin/zk_load_configs.sh -m DUMP -z $ZOOKEEPER -c ENRICHMENT -n squid Fixed > Metron tutorial part 2, should have instructions to retrigger squid data feed, and directions on how to drive the Rest interface to prove data is being enriched. That tutorial references back to part 1 for instructions, but I added an extra line with the command detail. The Head plugin can be used for searching the ES indexes in this context. > Threatintel tutorial: Dropping of elasticsearch index requires a sudo as their owned by root This series of tutorials assumes full dev - you should be running as root by default in that environment > What commands are you using to query the ES index? Head browser plugin. From the first blog 
---------------------------------------------------------------- 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: [email protected] With regards, Apache Git Services
