[
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:
[email protected]
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)
