Re: [外部邮件] Re: [外部邮件] Re: [外部邮件] Re: request contributor permissions

Hi, Please give me contributor permissions. My JIRA username is: yanghua . Thanks! 2017-05-05 17:43 GMT+08:00 Till Rohrmann : > Alright, I've given you contributor rights. Welcome to the Flink community > :-) > > On Fri, May 5, 2017 at 11:15 AM, 郭健

Re: [DISCUSS] Feature Freeze

Yes, I second Ufuk, thanks Robert and Aljoscha for the effort. Thanks to the community for hard work on the features. On Fri, May 5, 2017 at 4:03 PM, Ufuk Celebi wrote: > On Fri, May 5, 2017 at 3:59 PM, Stephan Ewen wrote: > > Also, if no release candidate

[jira] [Created] (FLINK-6467) Potential lack of synchronization w.r.t. newSstFiles in RocksDBKeyedStateBackend#releaseResources()

Ted Yu created FLINK-6467: - Summary: Potential lack of synchronization w.r.t. newSstFiles in RocksDBKeyedStateBackend#releaseResources() Key: FLINK-6467 URL: https://issues.apache.org/jira/browse/FLINK-6467

[jira] [Created] (FLINK-6466) Build Hadoop 2.8.0 convenience binaries

Greg Hogan created FLINK-6466: - Summary: Build Hadoop 2.8.0 convenience binaries Key: FLINK-6466 URL: https://issues.apache.org/jira/browse/FLINK-6466 Project: Flink Issue Type: New Feature

[jira] [Created] (FLINK-6465) support FIRST_VALUE and LAST_VALUE on Table API & SQL

Hequn Cheng created FLINK-6465: -- Summary: support FIRST_VALUE and LAST_VALUE on Table API & SQL Key: FLINK-6465 URL: https://issues.apache.org/jira/browse/FLINK-6465 Project: Flink Issue Type:

[jira] [Created] (FLINK-6464) Metric name is not stable

Andrey created FLINK-6464: - Summary: Metric name is not stable Key: FLINK-6464 URL: https://issues.apache.org/jira/browse/FLINK-6464 Project: Flink Issue Type: Bug Affects Versions: 1.2.0

Re: [DISCUSS] Feature Freeze

On Fri, May 5, 2017 at 3:59 PM, Stephan Ewen wrote: > Also, if no release candidate would be created today, it would not make any > difference anyways... If no one tests a RC (if created today) over the weekend it also wouldn't make a difference. ;-) Thanks to all for chiming

Re: [DISCUSS] Feature Freeze

@robert - thanks, I think that is nice. That gives fairness across timezones. Also, if no release candidate would be created today, it would not make any difference anyways... On Fri, May 5, 2017 at 3:44 PM, Robert Metzger wrote: > To quickly clarify: I said Friday 3pm for

Re: [DISCUSS] What is a "Blocker" in our JIRA?

My reference to post-hoc was in regards to release. Concurrent dev and doc is of course ideal but I think anyone running snapshot is aware that docs may be somewhat out of sync. A better link discussing unreleased publication: http://www.apache.org/legal/release-policy.html#publication Our

Re: Official Flink Docker images

Thanks a lot for your efforts! Maybe we can even put a small blog post on the Flink post once its available on docker hub. On Fri, Apr 28, 2017 at 11:00 AM, Ismaël Mejía wrote: > Hello, > > I am absolutely happy to see that this is finally happening! > We have a really neat

Re: [DISCUSS] Feature Freeze

To quickly clarify: I said Friday 3pm for the feature freeze in my Tuesday email, but I decided to actually turn it into a proper *"end of the week" by doing the feature freeze Sunday evening/Monday morning*. On Fri, May 5, 2017 at 11:46 AM, Radu Tudoran wrote: > Sorry

Re: [DISCUSS] What is a "Blocker" in our JIRA?

On Fri, May 5, 2017 at 2:24 PM, Greg Hogan wrote: > -1 to post-hoc documentation and unreleased publication [0] Could you quickly confirm that I understand this correctly: - Post-hoc documentation means not documenting features separately from their initial PRs? - Unreleased

[jira] [Created] (FLINK-6463) Throw exception when NOT-NEXT is after OPTIONAL

Kostas Kloudas created FLINK-6463: - Summary: Throw exception when NOT-NEXT is after OPTIONAL Key: FLINK-6463 URL: https://issues.apache.org/jira/browse/FLINK-6463 Project: Flink Issue Type:

Re: [DISCUSS] What is a "Blocker" in our JIRA?

+1 to restricting use of “blocker" -1 to post-hoc documentation and unreleased publication [0] [0] http://www.apache.org/dev/release-publishing.html > On May 5, 2017, at 5:06 AM, Ufuk Celebi wrote: > > Thanks for this discussion Robert. I agree with your points. +1 > >

[jira] [Created] (FLINK-6462) Add requires over indicators for UDAF

sunjincheng created FLINK-6462: -- Summary: Add requires over indicators for UDAF Key: FLINK-6462 URL: https://issues.apache.org/jira/browse/FLINK-6462 Project: Flink Issue Type: Improvement

[jira] [Created] (FLINK-6461) Port web-related configuration parameters to ConfigOptions

Chesnay Schepler created FLINK-6461: --- Summary: Port web-related configuration parameters to ConfigOptions Key: FLINK-6461 URL: https://issues.apache.org/jira/browse/FLINK-6461 Project: Flink

[jira] [Created] (FLINK-6460) Build Fat Jar failed while building with SBT Assembly flink 1.2.1

Shashank Agarwal created FLINK-6460: --- Summary: Build Fat Jar failed while building with SBT Assembly flink 1.2.1 Key: FLINK-6460 URL: https://issues.apache.org/jira/browse/FLINK-6460 Project: Flink

Re: [DISCUSS] What is a "Blocker" in our JIRA?

I agree with Robert’s suggestion and also vote for unblocking documentation issues. > Am 05.05.2017 um 11:06 schrieb Ufuk Celebi : > > Thanks for this discussion Robert. I agree with your points. +1 > > Regarding the documentation: I also agree with Kostas and others that > it

RE: [DISCUSS] Feature Freeze

Sorry in case I missed something in the discussion of coming up with the list of open threads, but there is also [FLINK-6075] Support Order By for Stream SQL (Support Limit/Top(Sort) for Stream SQL) ...in case you want to consider it (it only needs a review) Best regards, -Original

Re: [外部邮件] Re: [外部邮件] Re: [外部邮件] Re: request contributor permissions

Alright, I've given you contributor rights. Welcome to the Flink community :-) On Fri, May 5, 2017 at 11:15 AM, 郭健 wrote: > Yes, this is my another email. > > 在 17/5/5 16:12，“Till Rohrmann” 写入: > > Hi, > > Aegeaner seems to be associated with

Re: [外部邮件] Re: [外部邮件] Re: [外部邮件] Re: request contributor permissions

Yes, this is my another email. 在 17/5/5 16:12，“Till Rohrmann” 写入: Hi, Aegeaner seems to be associated with westla...@126.com. Is that also your email address? Cheers, Till On Fri, May 5, 2017 at 8:37 AM, 郭健 wrote:

Re: [DISCUSS] What is a "Blocker" in our JIRA?

Thanks for this discussion Robert. I agree with your points. +1 Regarding the documentation: I also agree with Kostas and others that it is very important to have good documentation in place. The good thing about our current doc deployment model is that we can update the docs for a released

Re: [DISCUSS] Feature Freeze

I've checked the release status again, and it seems that some more issues made it into master, while other very big new features are still being finished (incremental checkpointing, retractions, serializer upgrades and automatic buffer management). I'll publish the first, non-voting, testing only

Re: [外部邮件] Re: [外部邮件] Re: request contributor permissions

Hi, Aegeaner seems to be associated with westla...@126.com. Is that also your email address? Cheers, Till On Fri, May 5, 2017 at 8:37 AM, 郭健 wrote: > Any one could give me contributor permission please? > JIRA username: Aegeaner > Email: xih...@gmail.com > > 在 17/5/4

[jira] [Created] (FLINK-6458) Support NOT patterns with preceding OPTIONALS

Kostas Kloudas created FLINK-6458: - Summary: Support NOT patterns with preceding OPTIONALS Key: FLINK-6458 URL: https://issues.apache.org/jira/browse/FLINK-6458 Project: Flink Issue Type:

Re: [DISCUSS] What is a "Blocker" in our JIRA?

I understand the motivation to make documentation equally important as bugs in software, but from my point of view as a release manager, its not easy to keep track of the release status when some blockers are not real blockers (I can't just look at the number in JIRA, but I have to manually go

Re: [外部邮件] Re: [外部邮件] Re: request contributor permissions

Any one could give me contributor permission please? JIRA username: Aegeaner Email: xih...@gmail.com 在 17/5/4 15:48，“郭健” 写入: Request for contributor permission too, my jira username is : Aegeaner Thanks 在 17/5/3 23:57，“Till Rohrmann”