[jira] [Created] (STREAMS-677) add support for setting earliest timestamp in TwitterTimelineProviderTask
Steve Blackmon created STREAMS-677: -- Summary: add support for setting earliest timestamp in TwitterTimelineProviderTask Key: STREAMS-677 URL: https://issues.apache.org/jira/browse/STREAMS-677 Project: Streams Issue Type: Task Reporter: Steve Blackmon Assignee: Steve Blackmon add support for setting earliest timestamp in TwitterTimelineProviderTask -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (STREAMS-676) remove unnecessary keying and use GlobalWindow in streams-examples-flink/flink-twitter-collection
Steve Blackmon created STREAMS-676: -- Summary: remove unnecessary keying and use GlobalWindow in streams-examples-flink/flink-twitter-collection Key: STREAMS-676 URL: https://issues.apache.org/jira/browse/STREAMS-676 Project: Streams Issue Type: Task Reporter: Steve Blackmon Assignee: Steve Blackmon remove unnecessary keying and use GlobalWindow in streams-examples-flink/flink-twitter-collection -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (STREAMS-660) Fixup release 0.6.2-SNAPSHOT version strings in poms
[ https://issues.apache.org/jira/browse/STREAMS-660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Blackmon resolved STREAMS-660. Resolution: Fixed > Fixup release 0.6.2-SNAPSHOT version strings in poms > > > Key: STREAMS-660 > URL: https://issues.apache.org/jira/browse/STREAMS-660 > Project: Streams > Issue Type: Improvement >Reporter: Joey Frazee >Assignee: Joey Frazee >Priority: Major > > The version strings in the poms aren't consistent and include > 0.6.2-SNAPSHOT-SNAPSHOT, 0.6.2-SNAPSHOT, and some 0.6.1 stragglers. We should > change these to 0.6.2-SNAPSHOT. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (STREAMS-659) Upgrade to Java 11+
[ https://issues.apache.org/jira/browse/STREAMS-659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Blackmon resolved STREAMS-659. Resolution: Fixed > Upgrade to Java 11+ > --- > > Key: STREAMS-659 > URL: https://issues.apache.org/jira/browse/STREAMS-659 > Project: Streams > Issue Type: Improvement >Reporter: Joey Frazee >Assignee: Joey Frazee >Priority: Major > > It'd be nice if Streams built on more recent (and supported) versions of Java. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (STREAMS-666) ensure rat check passes to prepare for 0.7.0 release
[ https://issues.apache.org/jira/browse/STREAMS-666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Blackmon resolved STREAMS-666. Resolution: Fixed > ensure rat check passes to prepare for 0.7.0 release > > > Key: STREAMS-666 > URL: https://issues.apache.org/jira/browse/STREAMS-666 > Project: Streams > Issue Type: Task >Reporter: Steve Blackmon >Assignee: Steve Blackmon >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (STREAMS-671) flink twitter examples output files do not contain date-time fields
[ https://issues.apache.org/jira/browse/STREAMS-671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Blackmon resolved STREAMS-671. Resolution: Fixed > flink twitter examples output files do not contain date-time fields > --- > > Key: STREAMS-671 > URL: https://issues.apache.org/jira/browse/STREAMS-671 > Project: Streams > Issue Type: Bug >Reporter: Steve Blackmon >Assignee: Steve Blackmon >Priority: Major > > flink twitter examples output files do not contain date-time fields > this is likely a by-product of Flink's default treatment of JodaTime objects > in pojos > add more tests that check pipeline output files and fix the date time issue -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (STREAMS-664) Fix LICENSE
[
https://issues.apache.org/jira/browse/STREAMS-664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Blackmon resolved STREAMS-664.
Resolution: Fixed
> Fix LICENSE
> ---
>
> Key: STREAMS-664
> URL: https://issues.apache.org/jira/browse/STREAMS-664
> Project: Streams
> Issue Type: Task
>Reporter: Steve Blackmon
>Assignee: Steve Blackmon
>Priority: Major
>
> Per email from Justin to dev list 4/11/2020
> {color:#d5dade}- There seems to be a few things missing from LICENSE{color}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (STREAMS-670) new Scala Maven Plugin can fail in some modules due to default incremental compile mode
[ https://issues.apache.org/jira/browse/STREAMS-670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Blackmon resolved STREAMS-670. Resolution: Fixed > new Scala Maven Plugin can fail in some modules due to default incremental > compile mode > --- > > Key: STREAMS-670 > URL: https://issues.apache.org/jira/browse/STREAMS-670 > Project: Streams > Issue Type: Bug >Reporter: Steve Blackmon >Assignee: Steve Blackmon >Priority: Major > > new Scala Maven Plugin can fail in some modules due to default incremental > compile mode > observed repeatedly in streams-processor-fullcontact and a few others that > have both java and scala sources > forcing plugin to always compile 'all' seems to be recommended solution -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (STREAMS-669) make java 8 the default source and target version
[ https://issues.apache.org/jira/browse/STREAMS-669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Blackmon resolved STREAMS-669. Resolution: Fixed > make java 8 the default source and target version > - > > Key: STREAMS-669 > URL: https://issues.apache.org/jira/browse/STREAMS-669 > Project: Streams > Issue Type: Task >Reporter: Steve Blackmon >Assignee: Steve Blackmon >Priority: Major > > after adding java 11 support, IntelliJ sees java 11 as the default version > create a java 8 profile active by default and let maven or user enable java > 11 if they want it -- This message was sent by Atlassian Jira (v8.3.4#803005)
