[
https://issues.jboss.org/browse/TEIID-1634?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-1634:
---------------------------------------
I was already resolving before seeing Van's comment.
The existing functionality is a little bit of a jack of all trades:
You can specify a directory and get all files under it. Is it an error if the directory
is empty?
You can specify a directory and an extension to filter on. Is it an error if no files
match the extension?
If the path appears to be a directory/file that doesn't exist, is that an error?
For consistency, the answer in all cases is currently no. Changing any of those
situations to an error could be done, but keep in mind it will be a breaking change.
As for a warning, that would not be needed if we're throwing an error as that would
generate generate a warning log. Otherwise it isn't appropriate to log a warning, but
not throw an error.
For file connector-based queries, please provide a DEBUG warning if
no files are found
--------------------------------------------------------------------------------------
Key: TEIID-1634
URL:
https://issues.jboss.org/browse/TEIID-1634
Project: Teiid
Issue Type: Bug
Components: Query Engine
Reporter: Paul Nittel
Assignee: Steven Hawkins
Fix For: 7.4.1
I am writing a query against an XML file. I have a file connector referenced by a dynamic
VDB. As luck would have it, I used an incorrect directory when the data source was
defined. When the query is executed, it appears as though I have no results. (I actually
have no data!) After fiddling with the XML for a while, I realized the error, corrected
it, and went merrily on my way.
Had there been some kind of notification that there were no files to process, I could
have saved a half-hour. So, if a DEBUG message were put in the log file, it may help
someone else (or me again) down the road.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira