[
https://issues.apache.org/jira/browse/DRILL-7306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16875630#comment-16875630
]
ASF GitHub Bot commented on DRILL-7306:
---------------------------------------
paul-rogers commented on issue #1813: DRILL-7306: Disable schema-only batch for
new scan framework
URL: https://github.com/apache/drill/pull/1813#issuecomment-506999568
When running the full tests, the following failed in `java-exec`:
```
[ERROR] Errors:
[ERROR]
TestDynamicUDFSupport.testReRegisterTheSameJarWithDifferentContent:600->BaseTestQuery.testRunAndReturn:340
ยป Rpc
```
When running this unit test in Eclipse, two tests failed: `testDropFunction`
and `testSuccessfulRegistrationAfterSeveralRetryAttempts`. Then,
`testConcurrentRemoteRegistryUpdateWithDuplicates` hung forever.
I believe these tests (and one other that I can't recall) seem to fail about
50% of the time on my builds.
The workaround seems to be to rebuild all of Drill. That is, the rough
pattern seems to be that this test will run once after a clean build, but will
fail if run a second time or after a code change. Not sure if this is the exact
pattern; something like this happens.
The result is that it is hard to tell if my code broke something or if the
tests are just flaky. I wonder, is there something we can do to stabilize these
tests? All other tests run fine if I rerun them a second time on the same build
or after I make a small code change.
Anyway, after doing a full rebuild and retest, this commit does pass all
unit tests.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
> Disable "fast schema" batch for new scan framework
> --------------------------------------------------
>
> Key: DRILL-7306
> URL: https://issues.apache.org/jira/browse/DRILL-7306
> Project: Apache Drill
> Issue Type: Bug
> Affects Versions: 1.16.0
> Reporter: Paul Rogers
> Assignee: Paul Rogers
> Priority: Major
> Labels: ready-to-commit
> Fix For: 1.17.0
>
>
> The EVF framework is set up to return a "fast schema" empty batch with only
> schema as its first batch because, when the code was written, it seemed
> that's how we wanted operators to work. However, DRILL-7305 notes that many
> operators cannot handle empty batches.
> Since the empty-batch bugs show that Drill does not, in fact, provide a "fast
> schema" batch, this ticket asks to disable the feature in the new scan
> framework. The feature is disabled with a config option; it can be re-enabled
> if ever it is needed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
