[
https://issues.apache.org/jira/browse/BEAM-6670?focusedWorklogId=215509&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-215509
]
ASF GitHub Bot logged work on BEAM-6670:
----------------------------------------
Author: ASF GitHub Bot
Created on: 19/Mar/19 15:11
Start Date: 19/Mar/19 15:11
Worklog Time Spent: 10m
Work Description: iemejia commented on issue #7956: [BEAM-6670] Add
option to disable reshuffling of JdbcIO
URL: https://github.com/apache/beam/pull/7956#issuecomment-474415287
I tend to be against extra knobs but with this one I think it makes sense to
have something like this in place. As we do reshuffle to break fusion, not
reshuffling can make sense too. Of course this should not be the default
behavior.
The idea of inferring automatically this is really nice but not sure if
'quickly' viable. Not sure I have seen if we have something like this in other
place in the code base..
----------------------------------------------------------------
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]
Issue Time Tracking
-------------------
Worklog Id: (was: 215509)
Time Spent: 50m (was: 40m)
> Option to disable reparallelization in JdbcIO.Read
> --------------------------------------------------
>
> Key: BEAM-6670
> URL: https://issues.apache.org/jira/browse/BEAM-6670
> Project: Beam
> Issue Type: Wish
> Components: io-java-jdbc
> Reporter: Mike Pedersen
> Priority: Minor
> Time Spent: 50m
> Remaining Estimate: 0h
>
> I'm doing approx. 20 JDBC queries against a database and then joining them
> together in a group by. Every single one of these queries does a reshuffle,
> which is sort of useless due to them being fed to a CoGroupByKey immediately
> afterwards.
> Reshuffle by default seems sensible by the principle of least surprise, but
> it would be nice to have a way to disable it when it's not necessary. For
> example a "withReshuffle(boolean)" method.
> This should be an easy addition and I am willing to add this if it sounds
> reasonable enough.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
