[
https://issues.apache.org/jira/browse/BEAM-6670?focusedWorklogId=222361&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-222361
]
ASF GitHub Bot logged work on BEAM-6670:
----------------------------------------
Author: ASF GitHub Bot
Created on: 03/Apr/19 15:06
Start Date: 03/Apr/19 15:06
Worklog Time Spent: 10m
Work Description: aromanenko-dev commented on issue #7956: [BEAM-6670]
Add option to disable reshuffling of JdbcIO
URL: https://github.com/apache/beam/pull/7956#issuecomment-479530120
The same, I agree that we should avoid additional "knobs" and we do our best
for that, but about 2x performance improvement seems as a reasonable argument
for me to add this "knob".
I propose to add such feature but we could call it `withForcedFusionBreak()`
which will be `true` by default and it can be turned off in case of reshuffle
phase after.
----------------------------------------------------------------
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: 222361)
Time Spent: 1h (was: 50m)
> 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: 1h
> 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)
