Based on my current understanding, when a trigger fires, all elements that
have been waiting behind a GroupByKey are allowed to continue through the
pipeline. Is it possible to create a custom trigger that fires
independently for each key? For example, instead of a trigger that fires
after 1000 elements total, is it possible to write a trigger that fires for
a specific key once 1000 elements with that key have been found?
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB