This actually looks like a serious regression. The root cause of this problem is that session options are not getting passed to the fragments.
I think this is caused by DRILL-1163, which introduced the concept of Query Options. With this change, session options were no longer handled properly. On Wed, Oct 8, 2014 at 12:38 AM, mufy <[email protected]> wrote: > Even after updating the value for a session option, the value when queried > reflects the default value. How to know what is the value for the current > session? > > > [root@n69 bin]# ./sqlline -u jdbc:drill:zk=n69:5181,n72:5181,n73:5181 -n > admin -p admin > sqlline version 1.1.6 > > 0: jdbc:drill:zk=n69:5181,n72:5181,n73:5181> alter session set > `exec.errors.verbose`=true; > +------------+------------+ > | ok | summary | > +------------+------------+ > | true | exec.errors.verbose updated. | > +------------+------------+ > 1 row selected (0.185 seconds) > > 0: jdbc:drill:zk=n69:5181,n72:5181,n73:5181> select * from sys.options > where name = 'exec.errors.verbose'; > > +------------+------------+------------+------------+------------+------------+------------+ > | name | kind | type | num_val | string_val | > bool_val | float_val | > > +------------+------------+------------+------------+------------+------------+------------+ > | exec.errors.verbose | BOOLEAN | SYSTEM | null | null | > false | null | > > +------------+------------+------------+------------+------------+------------+------------+ > 1 row selected (0.192 seconds) > > > > --- > Mufeed Usman > My LinkedIn <http://www.linkedin.com/pub/mufeed-usman/28/254/400> | My > Social Cause <http://www.vision2016.org.in/> | My Blogs : LiveJournal > <http://mufeed.livejournal.com> > -- Steven Phillips Software Engineer mapr.com
