On Tue, Jun 9, 2015 at 11:42 AM, Jason Altekruse <[email protected]> wrote:
> *We do not currently have a shortcut to read files in the directory where > you launched Drill.* > This has made me grumpy in the past, but I really think that Drill got it right here. The real problem is that with a large parallel program running on many machines, "where you launched Drill" is a really messy concept. You can specify work spaces to get essentially the same effect, with noticeably less agility than running a process on a single machine. It might be nice if there were some way to deal with the case of a current directory for the embedded Drill, but supporting that reasonably well would probably have the primary effect of ingraining bad habits. Another nice thought would be to allow session variables to be set and then referenced in the input source definitions. Embedded Drill could set these to current working directory, in parallel cases, users could set this in their script. As nice as that might be, how this is better than [use db] is not clear to me.
