PS technically, some "flavor" of the dataset still can be attributed and
 passed on in the pipeline, e.g., that's what i do with partitioning kind.
if another operator messes that flavor up, this gets noted in the
carry-over property (that's how optimizer knows if operands in a binary
logical operator are coming in identically partitioned or not, for
example). similar thing can be done to "sorted-ness" flavor and being
tracked around, and operators that break "sorted-ness" would note that also
on the tree nodes, but that only makes sense if we have "consumer"
operators that care about sortedness, of which we have none at the moment
(it possible that we will, perhaps). I am just saying this problem may
benefit from some more broad thinking of the issue in optimization tree
sense, i.e., why we do it, which things will use it and which things will
preserve/mess it up etc.

On Tue, Sep 5, 2017 at 3:01 PM, Dmitriy Lyubimov <[EMAIL PROTECTED]> wrote:
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