Re: FlinkML on slack

2017-06-09 Thread Tao Meng 
Could invite me into slack ?

Stavros Kontopoulos 于2017年6月8日周四 上午3:56写道：

> Hi all,
>
> We took the initiative to create the organization for FlinkML on slack
> (thnx Eron).
> There is now a channel for model-serving
> <
> https://docs.google.com/document/d/1CjWL9aLxPrKytKxUF5c3ohs0ickp0fdEXPsPYPEywsE/edit#
> >.
> Another is coming for flink-jpmml.
> You are invited to join the channels and the efforts. @Gabor @Theo please
> consider adding channels for the other efforts there as well.
>
> FlinkMS on Slack  (https://flinkml.slack.com/)
>
> Details for the efforts here: Flink Roadmap doc
> <
> https://docs.google.com/document/d/1afQbvZBTV15qF3vobVWUjxQc49h3Ud06MIRhahtJ6dw/edit#
> >
>
> Github  (https://github.com/FlinkML)
>
>
> Stavros
>

[jira] [Created] (FLINK-6882) Activate checkstyle for runtime/registration

2017-06-09 Thread Greg Hogan (JIRA) 
Greg Hogan created FLINK-6882:
-

 Summary: Activate checkstyle for runtime/registration
 Key: FLINK-6882
 URL: https://issues.apache.org/jira/browse/FLINK-6882
 Project: Flink
  Issue Type: Improvement
  Components: Local Runtime
Affects Versions: 1.4.0
Reporter: Greg Hogan
Assignee: Greg Hogan
Priority: Trivial
 Fix For: 1.4.0






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: FlinkML on slack

2017-06-09 Thread Theodore Vasiloudis 
Thank you for the guidelines Robert, I've replaced the Flink logo with a
placeholder image.

On Thu, Jun 8, 2017 at 8:24 AM, Robert Metzger  wrote:

> I'm happy to see efforts towards machine learning on Apache Flink within
> the community!
>
> I think its okay to have a GitHub repository for the ML stuff, but there
> are some rules by the ASF you have to follow: https://www.apache.org/
> foundation/marks/faq/#products
>
> As immediate steps, I would remove the Flink logo from the GitHub orga and
> add a disclaimer to the flink-modelserver repo.
> Also, I think it would be helpful to put a disclaimer (maybe into the orga
> description) that it is not an official Apache project.
>
> One last thing: I haven't completely forgotten the "repo split" discussion
> we had a while back. Maybe we could really start by just putting the ML
> library into a separate repo.
> Now that Theo is a committer, it should be easier to commit code from the
> entire ML crew into the repo.
>
>
>
> On Thu, Jun 8, 2017 at 4:32 PM, Stavros Kontopoulos <
> st.kontopou...@gmail.com> wrote:
>
>> @Ted Yu sure.
>>
>> On Thu, Jun 8, 2017 at 5:18 PM, Ted Yu  wrote:
>>
>> > Hi Stavros,
>> > Can you add me as well ?
>> >
>> > Thanks
>> >
>> > On Wed, Jun 7, 2017 at 12:56 PM, Stavros Kontopoulos <
>> > st.kontopou...@gmail.com> wrote:
>> >
>> > > Hi all,
>> > >
>> > > We took the initiative to create the organization for FlinkML on slack
>> > > (thnx Eron).
>> > > There is now a channel for model-serving
>> > > > > > fdEXPsPYPEywsE/edit#>.
>> > > Another is coming for flink-jpmml.
>> > > You are invited to join the channels and the efforts. @Gabor @Theo
>> please
>> > > consider adding channels for the other efforts there as well.
>> > >
>> > > FlinkMS on Slack  (
>> > https://flinkml.slack.com/)
>> > >
>> > > Details for the efforts here: Flink Roadmap doc
>> > > > > > d06MIRhahtJ6dw/edit#>
>> > >
>> > > Github  (https://github.com/FlinkML)
>> > >
>> > >
>> > > Stavros
>> > >
>> >
>>
>
>

[jira] [Created] (FLINK-6881) Creating a table from a POJO and defining a time attribute fails

2017-06-09 Thread Timo Walther (JIRA) 
Timo Walther created FLINK-6881:
---

 Summary: Creating a table from a POJO and defining a time 
attribute fails
 Key: FLINK-6881
 URL: https://issues.apache.org/jira/browse/FLINK-6881
 Project: Flink
  Issue Type: Bug
  Components: Table API & SQL
Reporter: Timo Walther


Creating a table from a DataStream of POJOs fails when the user tries to define 
a rowtime attribute.

There are multiple reasons in {{ExpressionParser}} as well as 
{{StreamTableEnvironment#validateAndExtractTimeAttributes}}.

See also: 
https://stackoverflow.com/questions/8022/apache-flink-1-3-table-api-rowtime-strange-behavior



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (FLINK-6880) Activate checkstyle for runtime/iterative

2017-06-09 Thread Greg Hogan (JIRA) 
Greg Hogan created FLINK-6880:
-

 Summary: Activate checkstyle for runtime/iterative
 Key: FLINK-6880
 URL: https://issues.apache.org/jira/browse/FLINK-6880
 Project: Flink
  Issue Type: Improvement
  Components: Local Runtime
Affects Versions: 1.4.0
Reporter: Greg Hogan
Assignee: Greg Hogan
Priority: Trivial
 Fix For: 1.4.0






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (FLINK-6879) Activate checkstyle for runtime/memory

2017-06-09 Thread Greg Hogan (JIRA) 
Greg Hogan created FLINK-6879:
-

 Summary: Activate checkstyle for runtime/memory
 Key: FLINK-6879
 URL: https://issues.apache.org/jira/browse/FLINK-6879
 Project: Flink
  Issue Type: Improvement
  Components: Local Runtime
Affects Versions: 1.4.0
Reporter: Greg Hogan
Assignee: Greg Hogan
Priority: Trivial
 Fix For: 1.4.0






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: [DISCUSS] GitBox

2017-06-09 Thread Greg Hogan 
Robert has an open PR from March. I’ve found, for example, PRs adding links to 
talks or slides left open for months.

I’d suggest Fluo is to Accumulo as flink-web is to the flink repo, and that 
migration looks to be satisfactory.


> On Jun 9, 2017, at 11:15 AM, Ted Yu  wrote:
> 
> bq. better track the oft-neglected contributions
> 
> Do you have estimate on how many contributions were not paid attention in
> the current infrastructure.
> 
> Looking at #2, it seems Accumulo community hasn't reached consensus yet.
> 
> Cheers
> 
> On Fri, Jun 9, 2017 at 7:54 AM, Greg Hogan  wrote:
> 
>> All,
>> 
>> ASF now has available (and maybe mandatory for new projects or repos)
>> GitBox [0] which enables bi-directional sync to GitHub and links
>> committers' accounts, allowing for greater use of GitHub functionality by
>> contributors and for committers to perform many tasks otherwise requiring
>> INFRA tickets.
>> 
>> I'd like to propose moving flink-web [1] to GitBox, using GitHub issues,
>> and enabling notifications to the mailing lists. Apache Accumulo has
>> recently discussed [2] this topic with a list of benefits after migrating
>> Fluo. By migrating flink-web we can better track the oft-neglected
>> contributions and also test the waters for future migrations (perhaps for
>> the future sub-projects).
>> 
>> [0] https://gitbox.apache.org/
>> [1] https://github.com/apache/flink-web/pulls
>> [2]
>> http://apache-accumulo.1065345.n5.nabble.com/DISCUSS-
>> GitBox-tp21160p21497.html
>> 
>> Greg

[jira] [Created] (FLINK-6878) Activate checkstyle for runtime/query

2017-06-09 Thread Greg Hogan (JIRA) 
Greg Hogan created FLINK-6878:
-

 Summary:  Activate checkstyle for runtime/query
 Key: FLINK-6878
 URL: https://issues.apache.org/jira/browse/FLINK-6878
 Project: Flink
  Issue Type: Improvement
  Components: Local Runtime
Affects Versions: 1.4.0
Reporter: Greg Hogan
Assignee: Greg Hogan
Priority: Trivial
 Fix For: 1.4.0






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: [DISCUSS] GitBox

2017-06-09 Thread Ted Yu 
bq. better track the oft-neglected contributions

Do you have estimate on how many contributions were not paid attention in
the current infrastructure.

Looking at #2, it seems Accumulo community hasn't reached consensus yet.

Cheers

On Fri, Jun 9, 2017 at 7:54 AM, Greg Hogan  wrote:

> All,
>
> ASF now has available (and maybe mandatory for new projects or repos)
> GitBox [0] which enables bi-directional sync to GitHub and links
> committers' accounts, allowing for greater use of GitHub functionality by
> contributors and for committers to perform many tasks otherwise requiring
> INFRA tickets.
>
> I'd like to propose moving flink-web [1] to GitBox, using GitHub issues,
> and enabling notifications to the mailing lists. Apache Accumulo has
> recently discussed [2] this topic with a list of benefits after migrating
> Fluo. By migrating flink-web we can better track the oft-neglected
> contributions and also test the waters for future migrations (perhaps for
> the future sub-projects).
>
> [0] https://gitbox.apache.org/
> [1] https://github.com/apache/flink-web/pulls
> [2]
> http://apache-accumulo.1065345.n5.nabble.com/DISCUSS-
> GitBox-tp21160p21497.html
>
> Greg
>

[DISCUSS] GitBox

2017-06-09 Thread Greg Hogan 
All,

ASF now has available (and maybe mandatory for new projects or repos)
GitBox [0] which enables bi-directional sync to GitHub and links
committers' accounts, allowing for greater use of GitHub functionality by
contributors and for committers to perform many tasks otherwise requiring
INFRA tickets.

I'd like to propose moving flink-web [1] to GitBox, using GitHub issues,
and enabling notifications to the mailing lists. Apache Accumulo has
recently discussed [2] this topic with a list of benefits after migrating
Fluo. By migrating flink-web we can better track the oft-neglected
contributions and also test the waters for future migrations (perhaps for
the future sub-projects).

[0] https://gitbox.apache.org/
[1] https://github.com/apache/flink-web/pulls
[2]
http://apache-accumulo.1065345.n5.nabble.com/DISCUSS-GitBox-tp21160p21497.html

Greg

[jira] [Created] (FLINK-6877) Activate checkstyle for runtime/security

2017-06-09 Thread Greg Hogan (JIRA) 
Greg Hogan created FLINK-6877:
-

 Summary: Activate checkstyle for runtime/security
 Key: FLINK-6877
 URL: https://issues.apache.org/jira/browse/FLINK-6877
 Project: Flink
  Issue Type: Improvement
  Components: Local Runtime
Affects Versions: 1.4.0
Reporter: Greg Hogan
Assignee: Greg Hogan
Priority: Trivial
 Fix For: 1.4.0






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Elasticsearch 5 connector maven artifact

2017-06-09 Thread Dawid Wysakowicz 
Hi devs,

I tried using flink-connector-elasticsearch5_2.10 dependency:

> 
>
> org.apache.flink
>
> flink-connector-elasticsearch5_2.10
>
> 1.3.0
>
> 
>
>
But it seems it was not published with 1.3.0 release. Was it intended? I
filed a JIRA for it: https://issues.apache.org/jira/browse/FLINK-6854


Z pozdrowieniami! / Cheers!

Dawid Wysakowicz

*Data/Software Engineer*

Skype: dawid_wys | Twitter: @OneMoreCoder