[jira] [Work logged] (BEAM-6239) Nexmark benchmark for raw sessionization then stream enrichment
[ https://issues.apache.org/jira/browse/BEAM-6239?focusedWorklogId=192642&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-192642 ] ASF GitHub Bot logged work on BEAM-6239: Author: ASF GitHub Bot Created on: 31/Jan/19 03:41 Start Date: 31/Jan/19 03:41 Worklog Time Spent: 10m Work Description: kennknowles commented on pull request #7288: [BEAM-6239] Add SQL sessionize then side input join as a benchmark URL: https://github.com/apache/beam/pull/7288 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 192642) Time Spent: 3h (was: 2h 50m) > Nexmark benchmark for raw sessionization then stream enrichment > --- > > Key: BEAM-6239 > URL: https://issues.apache.org/jira/browse/BEAM-6239 > Project: Beam > Issue Type: New Feature > Components: examples-nexmark >Reporter: Kenneth Knowles >Assignee: Kenneth Knowles >Priority: Major > Fix For: Not applicable > > Time Spent: 3h > Remaining Estimate: 0h > > We have BOUNDED_SIDE_INPUT_JOIN that just enriches a stream. Another use case > is to sessionize first. I am curious about the different in perf, and how > this plays out in SQL. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work logged] (BEAM-6239) Nexmark benchmark for raw sessionization then stream enrichment
[ https://issues.apache.org/jira/browse/BEAM-6239?focusedWorklogId=192641&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-192641 ] ASF GitHub Bot logged work on BEAM-6239: Author: ASF GitHub Bot Created on: 31/Jan/19 03:41 Start Date: 31/Jan/19 03:41 Worklog Time Spent: 10m Work Description: kennknowles commented on issue #7288: [BEAM-6239] Add SQL sessionize then side input join as a benchmark URL: https://github.com/apache/beam/pull/7288#issuecomment-459203486 I don't think this is actually a usefully different benchmark than the other side input join, actually. I need to do some planning about getting coverage here. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 192641) Time Spent: 2h 50m (was: 2h 40m) > Nexmark benchmark for raw sessionization then stream enrichment > --- > > Key: BEAM-6239 > URL: https://issues.apache.org/jira/browse/BEAM-6239 > Project: Beam > Issue Type: New Feature > Components: examples-nexmark >Reporter: Kenneth Knowles >Assignee: Kenneth Knowles >Priority: Major > Fix For: Not applicable > > Time Spent: 2h 50m > Remaining Estimate: 0h > > We have BOUNDED_SIDE_INPUT_JOIN that just enriches a stream. Another use case > is to sessionize first. I am curious about the different in perf, and how > this plays out in SQL. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work logged] (BEAM-6239) Nexmark benchmark for raw sessionization then stream enrichment
[ https://issues.apache.org/jira/browse/BEAM-6239?focusedWorklogId=178301&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-178301 ] ASF GitHub Bot logged work on BEAM-6239: Author: ASF GitHub Bot Created on: 23/Dec/18 02:00 Start Date: 23/Dec/18 02:00 Worklog Time Spent: 10m Work Description: kennknowles commented on pull request #7287: [BEAM-6239] Add session side input join to Nexmark URL: https://github.com/apache/beam/pull/7287 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 178301) Time Spent: 2h 40m (was: 2.5h) > Nexmark benchmark for raw sessionization then stream enrichment > --- > > Key: BEAM-6239 > URL: https://issues.apache.org/jira/browse/BEAM-6239 > Project: Beam > Issue Type: New Feature > Components: examples-nexmark >Reporter: Kenneth Knowles >Assignee: Kenneth Knowles >Priority: Major > Time Spent: 2h 40m > Remaining Estimate: 0h > > We have BOUNDED_SIDE_INPUT_JOIN that just enriches a stream. Another use case > is to sessionize first. I am curious about the different in perf, and how > this plays out in SQL. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work logged] (BEAM-6239) Nexmark benchmark for raw sessionization then stream enrichment
[ https://issues.apache.org/jira/browse/BEAM-6239?focusedWorklogId=177500&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-177500 ] ASF GitHub Bot logged work on BEAM-6239: Author: ASF GitHub Bot Created on: 20/Dec/18 13:59 Start Date: 20/Dec/18 13:59 Worklog Time Spent: 10m Work Description: kennknowles commented on issue #7287: [BEAM-6239] Add session side input join to Nexmark URL: https://github.com/apache/beam/pull/7287#issuecomment-449007778 @echauchot @akedin finally all the unrelated failures green. WDYT? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 177500) Time Spent: 2.5h (was: 2h 20m) > Nexmark benchmark for raw sessionization then stream enrichment > --- > > Key: BEAM-6239 > URL: https://issues.apache.org/jira/browse/BEAM-6239 > Project: Beam > Issue Type: New Feature > Components: examples-nexmark >Reporter: Kenneth Knowles >Assignee: Kenneth Knowles >Priority: Major > Time Spent: 2.5h > Remaining Estimate: 0h > > We have BOUNDED_SIDE_INPUT_JOIN that just enriches a stream. Another use case > is to sessionize first. I am curious about the different in perf, and how > this plays out in SQL. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work logged] (BEAM-6239) Nexmark benchmark for raw sessionization then stream enrichment
[ https://issues.apache.org/jira/browse/BEAM-6239?focusedWorklogId=176616&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-176616 ] ASF GitHub Bot logged work on BEAM-6239: Author: ASF GitHub Bot Created on: 18/Dec/18 17:17 Start Date: 18/Dec/18 17:17 Worklog Time Spent: 10m Work Description: kennknowles commented on issue #7287: [BEAM-6239] Add session side input join to Nexmark URL: https://github.com/apache/beam/pull/7287#issuecomment-448298750 Rebased (w/ squash) just in case the problem was at a particular commit on master. If it happens again I will follow up with bug filing. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 176616) Time Spent: 2h 20m (was: 2h 10m) > Nexmark benchmark for raw sessionization then stream enrichment > --- > > Key: BEAM-6239 > URL: https://issues.apache.org/jira/browse/BEAM-6239 > Project: Beam > Issue Type: New Feature > Components: examples-nexmark >Reporter: Kenneth Knowles >Assignee: Kenneth Knowles >Priority: Major > Time Spent: 2h 20m > Remaining Estimate: 0h > > We have BOUNDED_SIDE_INPUT_JOIN that just enriches a stream. Another use case > is to sessionize first. I am curious about the different in perf, and how > this plays out in SQL. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work logged] (BEAM-6239) Nexmark benchmark for raw sessionization then stream enrichment
[ https://issues.apache.org/jira/browse/BEAM-6239?focusedWorklogId=176612&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-176612 ] ASF GitHub Bot logged work on BEAM-6239: Author: ASF GitHub Bot Created on: 18/Dec/18 17:10 Start Date: 18/Dec/18 17:10 Worklog Time Spent: 10m Work Description: kennknowles commented on issue #7287: [BEAM-6239] Add session side input join to Nexmark URL: https://github.com/apache/beam/pull/7287#issuecomment-448296542 Hmm, getting the same issue with HIFIO. Or maybe the problem is with the Jenkins worker. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 176612) Time Spent: 2h 10m (was: 2h) > Nexmark benchmark for raw sessionization then stream enrichment > --- > > Key: BEAM-6239 > URL: https://issues.apache.org/jira/browse/BEAM-6239 > Project: Beam > Issue Type: New Feature > Components: examples-nexmark >Reporter: Kenneth Knowles >Assignee: Kenneth Knowles >Priority: Major > Time Spent: 2h 10m > Remaining Estimate: 0h > > We have BOUNDED_SIDE_INPUT_JOIN that just enriches a stream. Another use case > is to sessionize first. I am curious about the different in perf, and how > this plays out in SQL. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work logged] (BEAM-6239) Nexmark benchmark for raw sessionization then stream enrichment
[ https://issues.apache.org/jira/browse/BEAM-6239?focusedWorklogId=176312&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-176312 ] ASF GitHub Bot logged work on BEAM-6239: Author: ASF GitHub Bot Created on: 18/Dec/18 02:07 Start Date: 18/Dec/18 02:07 Worklog Time Spent: 10m Work Description: kennknowles commented on issue #7287: [BEAM-6239] Add session side input join to Nexmark URL: https://github.com/apache/beam/pull/7287#issuecomment-448069919 Looks like infrastructure issue that hit while HIFIO test was running. Will re-run to see. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 176312) Time Spent: 1h 50m (was: 1h 40m) > Nexmark benchmark for raw sessionization then stream enrichment > --- > > Key: BEAM-6239 > URL: https://issues.apache.org/jira/browse/BEAM-6239 > Project: Beam > Issue Type: New Feature > Components: examples-nexmark >Reporter: Kenneth Knowles >Assignee: Kenneth Knowles >Priority: Major > Time Spent: 1h 50m > Remaining Estimate: 0h > > We have BOUNDED_SIDE_INPUT_JOIN that just enriches a stream. Another use case > is to sessionize first. I am curious about the different in perf, and how > this plays out in SQL. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work logged] (BEAM-6239) Nexmark benchmark for raw sessionization then stream enrichment
[ https://issues.apache.org/jira/browse/BEAM-6239?focusedWorklogId=176313&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-176313 ] ASF GitHub Bot logged work on BEAM-6239: Author: ASF GitHub Bot Created on: 18/Dec/18 02:07 Start Date: 18/Dec/18 02:07 Worklog Time Spent: 10m Work Description: kennknowles commented on issue #7287: [BEAM-6239] Add session side input join to Nexmark URL: https://github.com/apache/beam/pull/7287#issuecomment-448069940 run java precommit This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 176313) Time Spent: 2h (was: 1h 50m) > Nexmark benchmark for raw sessionization then stream enrichment > --- > > Key: BEAM-6239 > URL: https://issues.apache.org/jira/browse/BEAM-6239 > Project: Beam > Issue Type: New Feature > Components: examples-nexmark >Reporter: Kenneth Knowles >Assignee: Kenneth Knowles >Priority: Major > Time Spent: 2h > Remaining Estimate: 0h > > We have BOUNDED_SIDE_INPUT_JOIN that just enriches a stream. Another use case > is to sessionize first. I am curious about the different in perf, and how > this plays out in SQL. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work logged] (BEAM-6239) Nexmark benchmark for raw sessionization then stream enrichment
[ https://issues.apache.org/jira/browse/BEAM-6239?focusedWorklogId=176307&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-176307 ] ASF GitHub Bot logged work on BEAM-6239: Author: ASF GitHub Bot Created on: 18/Dec/18 01:28 Start Date: 18/Dec/18 01:28 Worklog Time Spent: 10m Work Description: kennknowles commented on issue #7287: [BEAM-6239] Add session side input join to Nexmark URL: https://github.com/apache/beam/pull/7287#issuecomment-448062241 The build did trigger, and it is at https://builds.apache.org/view/A-D/view/Beam/job/beam_PreCommit_Java_Commit/3154/ but not updating the GitHub status. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 176307) Time Spent: 1h 40m (was: 1.5h) > Nexmark benchmark for raw sessionization then stream enrichment > --- > > Key: BEAM-6239 > URL: https://issues.apache.org/jira/browse/BEAM-6239 > Project: Beam > Issue Type: New Feature > Components: examples-nexmark >Reporter: Kenneth Knowles >Assignee: Kenneth Knowles >Priority: Major > Time Spent: 1h 40m > Remaining Estimate: 0h > > We have BOUNDED_SIDE_INPUT_JOIN that just enriches a stream. Another use case > is to sessionize first. I am curious about the different in perf, and how > this plays out in SQL. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work logged] (BEAM-6239) Nexmark benchmark for raw sessionization then stream enrichment
[ https://issues.apache.org/jira/browse/BEAM-6239?focusedWorklogId=176305&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-176305 ] ASF GitHub Bot logged work on BEAM-6239: Author: ASF GitHub Bot Created on: 18/Dec/18 01:16 Start Date: 18/Dec/18 01:16 Worklog Time Spent: 10m Work Description: kennknowles commented on issue #7287: [BEAM-6239] Add session side input join to Nexmark URL: https://github.com/apache/beam/pull/7287#issuecomment-448059897 retest this please This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 176305) Time Spent: 1.5h (was: 1h 20m) > Nexmark benchmark for raw sessionization then stream enrichment > --- > > Key: BEAM-6239 > URL: https://issues.apache.org/jira/browse/BEAM-6239 > Project: Beam > Issue Type: New Feature > Components: examples-nexmark >Reporter: Kenneth Knowles >Assignee: Kenneth Knowles >Priority: Major > Time Spent: 1.5h > Remaining Estimate: 0h > > We have BOUNDED_SIDE_INPUT_JOIN that just enriches a stream. Another use case > is to sessionize first. I am curious about the different in perf, and how > this plays out in SQL. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work logged] (BEAM-6239) Nexmark benchmark for raw sessionization then stream enrichment
[ https://issues.apache.org/jira/browse/BEAM-6239?focusedWorklogId=176043&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-176043 ] ASF GitHub Bot logged work on BEAM-6239: Author: ASF GitHub Bot Created on: 17/Dec/18 14:16 Start Date: 17/Dec/18 14:16 Worklog Time Spent: 10m Work Description: echauchot commented on issue #7287: [BEAM-6239] Add session side input join to Nexmark URL: https://github.com/apache/beam/pull/7287#issuecomment-447860893 > @echauchot yea - I wanted to see how the overheads of side inputs vs sessionization would interact. Since sessionization might be sensitive to how it is buffered and how the output iterable is handled. I see This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 176043) Time Spent: 1h 20m (was: 1h 10m) > Nexmark benchmark for raw sessionization then stream enrichment > --- > > Key: BEAM-6239 > URL: https://issues.apache.org/jira/browse/BEAM-6239 > Project: Beam > Issue Type: New Feature > Components: examples-nexmark >Reporter: Kenneth Knowles >Assignee: Kenneth Knowles >Priority: Major > Time Spent: 1h 20m > Remaining Estimate: 0h > > We have BOUNDED_SIDE_INPUT_JOIN that just enriches a stream. Another use case > is to sessionize first. I am curious about the different in perf, and how > this plays out in SQL. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work logged] (BEAM-6239) Nexmark benchmark for raw sessionization then stream enrichment
[ https://issues.apache.org/jira/browse/BEAM-6239?focusedWorklogId=176010&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-176010 ] ASF GitHub Bot logged work on BEAM-6239: Author: ASF GitHub Bot Created on: 17/Dec/18 13:43 Start Date: 17/Dec/18 13:43 Worklog Time Spent: 10m Work Description: kennknowles commented on issue #7287: [BEAM-6239] Add session side input join to Nexmark URL: https://github.com/apache/beam/pull/7287#issuecomment-447849958 @echauchot yea - I wanted to see how the overheads of side inputs vs sessionization would interact. Since sessionization might be sensitive to how it is buffered and how the output iterable is handled. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 176010) Time Spent: 1h 10m (was: 1h) > Nexmark benchmark for raw sessionization then stream enrichment > --- > > Key: BEAM-6239 > URL: https://issues.apache.org/jira/browse/BEAM-6239 > Project: Beam > Issue Type: New Feature > Components: examples-nexmark >Reporter: Kenneth Knowles >Assignee: Kenneth Knowles >Priority: Major > Time Spent: 1h 10m > Remaining Estimate: 0h > > We have BOUNDED_SIDE_INPUT_JOIN that just enriches a stream. Another use case > is to sessionize first. I am curious about the different in perf, and how > this plays out in SQL. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work logged] (BEAM-6239) Nexmark benchmark for raw sessionization then stream enrichment
[ https://issues.apache.org/jira/browse/BEAM-6239?focusedWorklogId=175932&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-175932 ] ASF GitHub Bot logged work on BEAM-6239: Author: ASF GitHub Bot Created on: 17/Dec/18 09:08 Start Date: 17/Dec/18 09:08 Worklog Time Spent: 10m Work Description: echauchot commented on issue #7287: [BEAM-6239] Add session side input join to Nexmark URL: https://github.com/apache/beam/pull/7287#issuecomment-447771484 @kennknowles, cool ! That makes 3 side-input join queries ! This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 175932) Time Spent: 50m (was: 40m) > Nexmark benchmark for raw sessionization then stream enrichment > --- > > Key: BEAM-6239 > URL: https://issues.apache.org/jira/browse/BEAM-6239 > Project: Beam > Issue Type: New Feature > Components: examples-nexmark >Reporter: Kenneth Knowles >Assignee: Kenneth Knowles >Priority: Major > Time Spent: 50m > Remaining Estimate: 0h > > We have BOUNDED_SIDE_INPUT_JOIN that just enriches a stream. Another use case > is to sessionize first. I am curious about the different in perf, and how > this plays out in SQL. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work logged] (BEAM-6239) Nexmark benchmark for raw sessionization then stream enrichment
[ https://issues.apache.org/jira/browse/BEAM-6239?focusedWorklogId=175933&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-175933 ] ASF GitHub Bot logged work on BEAM-6239: Author: ASF GitHub Bot Created on: 17/Dec/18 09:08 Start Date: 17/Dec/18 09:08 Worklog Time Spent: 10m Work Description: echauchot edited a comment on issue #7287: [BEAM-6239] Add session side input join to Nexmark URL: https://github.com/apache/beam/pull/7287#issuecomment-447771484 @kennknowles, cool ! That makes 3 side-input join queries ! Thanks for your work This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 175933) Time Spent: 1h (was: 50m) > Nexmark benchmark for raw sessionization then stream enrichment > --- > > Key: BEAM-6239 > URL: https://issues.apache.org/jira/browse/BEAM-6239 > Project: Beam > Issue Type: New Feature > Components: examples-nexmark >Reporter: Kenneth Knowles >Assignee: Kenneth Knowles >Priority: Major > Time Spent: 1h > Remaining Estimate: 0h > > We have BOUNDED_SIDE_INPUT_JOIN that just enriches a stream. Another use case > is to sessionize first. I am curious about the different in perf, and how > this plays out in SQL. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work logged] (BEAM-6239) Nexmark benchmark for raw sessionization then stream enrichment
[ https://issues.apache.org/jira/browse/BEAM-6239?focusedWorklogId=175672&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-175672 ] ASF GitHub Bot logged work on BEAM-6239: Author: ASF GitHub Bot Created on: 15/Dec/18 04:42 Start Date: 15/Dec/18 04:42 Worklog Time Spent: 10m Work Description: kennknowles commented on issue #7287: [BEAM-6239] Add session side input join to Nexmark URL: https://github.com/apache/beam/pull/7287#issuecomment-447537032 run java precommit This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 175672) Time Spent: 40m (was: 0.5h) > Nexmark benchmark for raw sessionization then stream enrichment > --- > > Key: BEAM-6239 > URL: https://issues.apache.org/jira/browse/BEAM-6239 > Project: Beam > Issue Type: New Feature > Components: examples-nexmark >Reporter: Kenneth Knowles >Assignee: Kenneth Knowles >Priority: Major > Time Spent: 40m > Remaining Estimate: 0h > > We have BOUNDED_SIDE_INPUT_JOIN that just enriches a stream. Another use case > is to sessionize first. I am curious about the different in perf, and how > this plays out in SQL. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work logged] (BEAM-6239) Nexmark benchmark for raw sessionization then stream enrichment
[ https://issues.apache.org/jira/browse/BEAM-6239?focusedWorklogId=175659&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-175659 ] ASF GitHub Bot logged work on BEAM-6239: Author: ASF GitHub Bot Created on: 15/Dec/18 02:14 Start Date: 15/Dec/18 02:14 Worklog Time Spent: 10m Work Description: kennknowles commented on issue #7287: [BEAM-6239] Add session side input join to Nexmark URL: https://github.com/apache/beam/pull/7287#issuecomment-447529180 R: @akedin @echauchot I know you are a bit busy but tagging you so you see this This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 175659) Time Spent: 0.5h (was: 20m) > Nexmark benchmark for raw sessionization then stream enrichment > --- > > Key: BEAM-6239 > URL: https://issues.apache.org/jira/browse/BEAM-6239 > Project: Beam > Issue Type: New Feature > Components: examples-nexmark >Reporter: Kenneth Knowles >Assignee: Kenneth Knowles >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > We have BOUNDED_SIDE_INPUT_JOIN that just enriches a stream. Another use case > is to sessionize first. I am curious about the different in perf, and how > this plays out in SQL. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work logged] (BEAM-6239) Nexmark benchmark for raw sessionization then stream enrichment
[ https://issues.apache.org/jira/browse/BEAM-6239?focusedWorklogId=175657&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-175657 ] ASF GitHub Bot logged work on BEAM-6239: Author: ASF GitHub Bot Created on: 15/Dec/18 02:12 Start Date: 15/Dec/18 02:12 Worklog Time Spent: 10m Work Description: kennknowles opened a new pull request #7288: [BEAM-6239] Add SQL sessionize then side input join as a benchmark URL: https://github.com/apache/beam/pull/7288 This is my attempt at #7287 in SQL. I believe these features may not be supported by Calcite, and have reached out to their mailing list. Follow this checklist to help us incorporate your contribution quickly and easily: - [x] Format the pull request title like `[BEAM-XXX] Fixes bug in ApproximateQuantiles`, where you replace `BEAM-XXX` with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue. - [x] If this contribution is large, please file an Apache [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). It will help us expedite review of your Pull Request if you tag someone (e.g. `@username`) to look at it. Post-Commit Tests Status (on master branch) Lang | SDK | Apex | Dataflow | Flink | Gearpump | Samza | Spark --- | --- | --- | --- | --- | --- | --- | --- Go | [](https://builds.apache.org/job/beam_PostCommit_Go/lastCompletedBuild/) | --- | --- | --- | --- | --- | --- Java | [](https://builds.apache.org/job/beam_PostCommit_Java/lastCompletedBuild/) | [](https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Apex/lastCompletedBuild/) | [](https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Dataflow/lastCompletedBuild/) | [](https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Flink/lastCompletedBuild/) [](https://builds.apache.org/job/beam_PostCommit_Java_PVR_Flink/lastCompletedBuild/) | [](https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Gearpump/lastCompletedBuild/) | [](https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Samza/lastCompletedBuild/) | [](https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Spark/lastCompletedBuild/) Python | [](https://builds.apache.org/job/beam_PostCommit_Python_Verify/lastCompletedBuild/) | --- | [](https://builds.apache.org/job/beam_PostCommit_Py_VR_Dataflow/lastCompletedBuild/) [](https://builds.apache.org/job/beam_PostCommit_Py_ValCont/lastCompletedBuild/) | [](https://builds.apache.org/job/beam_PostCommit_Python_VR_Flink/lastCompletedBuild/) | --- | --- | --- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 175657) Time Spent: 20m (was: 10m) > Nexmark benchmark for raw sessionization then stream enrichment > --- > > Key: BEAM-6239 > URL: https:
[jira] [Work logged] (BEAM-6239) Nexmark benchmark for raw sessionization then stream enrichment
[ https://issues.apache.org/jira/browse/BEAM-6239?focusedWorklogId=175656&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-175656 ] ASF GitHub Bot logged work on BEAM-6239: Author: ASF GitHub Bot Created on: 15/Dec/18 02:11 Start Date: 15/Dec/18 02:11 Worklog Time Spent: 10m Work Description: kennknowles opened a new pull request #7287: [BEAM-6239] Add session side input join to Nexmark URL: https://github.com/apache/beam/pull/7287 This is a new benchmark of sessionization then a join with a side input. Follow this checklist to help us incorporate your contribution quickly and easily: - [x] Format the pull request title like `[BEAM-XXX] Fixes bug in ApproximateQuantiles`, where you replace `BEAM-XXX` with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue. - [x] If this contribution is large, please file an Apache [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). It will help us expedite review of your Pull Request if you tag someone (e.g. `@username`) to look at it. Post-Commit Tests Status (on master branch) Lang | SDK | Apex | Dataflow | Flink | Gearpump | Samza | Spark --- | --- | --- | --- | --- | --- | --- | --- Go | [](https://builds.apache.org/job/beam_PostCommit_Go/lastCompletedBuild/) | --- | --- | --- | --- | --- | --- Java | [](https://builds.apache.org/job/beam_PostCommit_Java/lastCompletedBuild/) | [](https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Apex/lastCompletedBuild/) | [](https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Dataflow/lastCompletedBuild/) | [](https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Flink/lastCompletedBuild/) [](https://builds.apache.org/job/beam_PostCommit_Java_PVR_Flink/lastCompletedBuild/) | [](https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Gearpump/lastCompletedBuild/) | [](https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Samza/lastCompletedBuild/) | [](https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Spark/lastCompletedBuild/) Python | [](https://builds.apache.org/job/beam_PostCommit_Python_Verify/lastCompletedBuild/) | --- | [](https://builds.apache.org/job/beam_PostCommit_Py_VR_Dataflow/lastCompletedBuild/) [](https://builds.apache.org/job/beam_PostCommit_Py_ValCont/lastCompletedBuild/) | [](https://builds.apache.org/job/beam_PostCommit_Python_VR_Flink/lastCompletedBuild/) | --- | --- | --- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 175656) Time Spent: 10m Remaining Estimate: 0h > Nexmark benchmark for raw sessionization then stream enrichment > --- > > Key: BEAM-6239 > URL: https://issues.apache.org/jira/browse/BEAM-6239 >
