cgivre commented on PR #2989:
URL: https://github.com/apache/drill/pull/2989#issuecomment-3831617861

   Hi Mike, Congrats on your retirement!  
   
   If this is acceptable, should we mark this as approved so we can merge it?  
Also, I don;t know if you have anything to do with the Daffodil community, but 
I’d like to publiciize this there as well so people can try it out. 
   
   See inline:
   
   
   > On Feb 1, 2026, at 11:58, Mike Beckerle ***@***.***> wrote:
   > 
   > mbeckerle left a comment (apache/drill#2989)
   > This seems like a practical approach. Whatever the file is, it goes to all 
nodes and on the class path.
   > I'm not sure what the corresponding SQL query would look like to reference 
these ".bin" files. Last I looked at this I think it was taking a file name, 
not a resource/classpath location. Would the location of this magic directory 
of files be something that could be expressed in the query in a common way, or 
would we adapt the code to use that location and expect only the file name of 
the ".bin" file?
   
   In a query like the one below, you could simply include the bin file in the 
query as shown below and it should work. 
   
   ```sql
   SELECT * FROM table(dfs.`data/data06Int.dat` 
   (type => 'daffodil', "
   validationMode => 'true', 
   schemaFile => 'schema.bin', 
   rootName => 'row',
   rootNamespace => null))
   ```
   
   
   > btw. I am retired now (as of Jan 1 2026) so not working on this technology 
very frequently. You can get other support for daffodil via the ***@***.*** 
email list when I am not responding.
   > —
   > Reply to this email directly, view it on GitHub, or unsubscribe.
   > You are receiving this because you were assigned.Message ID: ***@***.***>
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to