use separated thread in ffi exporter #788
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
richox
force-pushed
the
dev-ffi-export-thread
branch
8 times, most recently
from
6f6df99 to
16e8235
Compare
richox
force-pushed
the
dev-ffi-export-thread
branch
from
16e8235 to
3d891d0
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
as described in #748, ArrowFFIExporter needs to poll rows iterator by wrapping hadoop
ugi.doAsmethod. current solution wraps each.hasNext()and.next()and introduces extra costs.this pr adds a separated thread for polling rows iterator. so we don't call
doAson each record batch.