drill-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Barclay <dbarc...@maprtech.com>
Subject OK_NEW_SCHEMA: changed schema or maybe just new report?
Date Fri, 02 Oct 2015 18:26:04 GMT
Is OK_NEW_SCHEMA intended to signal that the new schema is actually
changed from any previous schema, or is it intended only to signal
that there's a new (report of the) schema, but the new schema isn't
necessarily different from any previous schema)?


Are callers (of XxxBatch next() methods) that receive OK_NEW_SCHEMA
responsible for checking whether the new schema is the same as the old
schema (or, more generally, can be handled by the caller) and avoiding
throwing a schema-change exception in that case?

Or are callees (XxxBatch next() methods) responsible for not returning
OK_NEW_SCHEMA if the new schema is the same as the previous schema?

(Or is it some combination?)

Thanks,
Daniel
-- 
Daniel Barclay
MapR Technologies

Mime
View raw message