Is it possible to temporarily disable (in client code) a scan time iterator that's been configured for a table? We want to write an iterator that's enabled by default, but we want to give anyone writing queries the option of disabling it for their query. There are other ways around our problem if this isn't possible, but this way seems the most straightforward.
So, yeah. User configured iterators can override table configured ones. That's probably a bad idea, but I suppose it does work that way now. On Apr 8, 2014 7:22 PM, "David Medinets" <[EMAIL PROTECTED]> wrote:
NEW: Monitor These Apps!
Apache Lucene, Apache Solr and all other Apache Software Foundation project and their respective logos are trademarks of the Apache Software Foundation.
Elasticsearch, Kibana, Logstash, and Beats are trademarks of Elasticsearch BV, registered in the U.S. and in other countries. This site and Sematext Group is in no way affiliated with Elasticsearch BV.
Service operated by Sematext