I like where Ted is going with this. I do also like Paul’s idea of giving Drill hints as to the schema. — C
> On Aug 15, 2018, at 20:34, Ted Dunning <ted.dunn...@gmail.com> wrote: > > This is a bold statement. > > And there are variants of it that could give users nearly the same > experience that we have now. For instance, if we cache discovered schemas > for old files and discover the schema for any new file that we see (and > cache it) before actually running a query. That gives us pretty much the > flexibility of schema on read without as much of the burden. > > > > On Wed, Aug 15, 2018 at 5:02 PM weijie tong <tongweijie...@gmail.com> wrote: > >> Hi all: >> Hope the statement not seems too dash to you. >> Drill claims be a schema-free distributed SQL engine. It pays lots of >> work to make the execution engine to support it to support JSON file like >> storage format. It is easier to make bugs and let the code logic ugly. I >> wonder do we still insist on this ,since we are designing the metadata >> system with DRILL-6552. >> Traditionally, people is used to design its table schema firstly before >> firing a SQL query. I don't think this saves people too much time. Other >> system like Spark is popular not due to lack the schema claiming. I think >> we should be brave enough to take the right decision whether to still >> insist on this feature which seems not so important but a burden. >> Thanks. >>
