You can set boot level start-up options in drill-override.conf [1]. But I don't think we can do the same with the system options. Someone else can comment if there is a workaround.
On why it works for you with drill-embedded, is something I'm trying to understand. I attempted this and couldn't manage to get those options to show up in embedded mode. [1] https://drill.apache.org/docs/start-up-options/ On Fri, Jul 22, 2016 at 1:20 PM, Scott Kinney <[email protected]> wrote: > I have built a drill docker images very much like > https://github.com/bigstepinc/apache-drill/blob/master/Dockerfile > > > I volume mount a drill-override.conf file that looks like: > > drill.exec:{ > cluster-id: drill1, > zk.connect: 192.1.1.1:2181", > sys.store.provider.local.path: "/drill-storage", > store.json.all_text_mode: True, > store.json.read_numbers_as_double: True > } > > it seems to be connecting to the zookeeper (otherwise it would fail right? > i should actually confirm this). > > I know it is picking up my s3 plugin that i volume mount inside > /drill-storage but it's not setting the json all_text_mode and > read_numbers_as_double. > > I have a drill-embeded instance that seems to pick these json setting from > the drill-override file just fine. > > Can you see what I'm doing wrong? > > > > > > ________________________________ > Scott Kinney | DevOps > stem <http://www.stem.com/> | m 510.282.1299 > 100 Rollins Road, Millbrae, California 94030 > > This e-mail and/or any attachments contain Stem, Inc. confidential and > proprietary information and material for the sole use of the intended > recipient(s). Any review, use or distribution that has not been expressly > authorized by Stem, Inc. is strictly prohibited. If you are not the > intended recipient, please contact the sender and delete all copies. Thank > you. >
