Suresh Krishnappa created FLINK-4405:
Summary: Implement Blob Server SSL
Key: FLINK-4405
URL: https://issues.apache.org/jira/browse/FLINK-4405
Project: Flink
Issue Type: Sub-task
Suresh Krishnappa created FLINK-4404:
Summary: Implement Data Transfer SSL
Key: FLINK-4404
URL: https://issues.apache.org/jira/browse/FLINK-4404
Project: Flink
Issue Type: Sub-task
Hi,
It’s a cool design, I really like it ! I have two questions here.
The first is whether do we have the complex composite triggers, i.e. nested All
and Any. Such as :
Any(
All(trigger1, trigger2),
Any(trigger3, trigger4)
)
Can the above code work?
Another question is : In
Hi Folks,
I just had an idea that I want to try now. The idea is to give little
HEADS-UP emails roughly at the beginning of each week. I would give a very
short summary of the big points that I want to work on for that week and if
others want to jump in they can also quickly outline what they are
Stephan Ewen created FLINK-4403:
---
Summary: RPC proxy classloading should use Flink class' classloader
Key: FLINK-4403
URL: https://issues.apache.org/jira/browse/FLINK-4403
Project: Flink
Issue
Hi Aljoscha,
Thanks for the feedback!
It is a nice feature to have. The reason it is not included in the FLIP
is that I have not seen somebody asking for something similar in the
mailing list.
A point that I have to add is that it seems (from the user ML) that
most of the times users expect
Aljoschae, exactly.
I'm assuming I don't want to maintain state in the window assigner? What
would you do if you wanted to solve this problem?
On Tue, Aug 16, 2016 at 7:29 AM Aljoscha Krettek
wrote:
> Hi,
> the problem with using session windows is that you don't know which
Ah, I just read the document again and noticed that it might be good to
differentiate between repeatable triggers and non-repeating triggers. I'm
proposing to make most triggers non-repeating with the addition of a
trigger that makes other triggers repeatable.
Example Non-Repeating:
Jamie,
I think you raise a valid concern but I would hesitate to accept the suggestion
that the low-level API be promoted to app developers.
Higher-level abstractions tend to be more constrained and more optimized,
whereas lower-level abstractions tend to be more powerful, be more laborious to
Hi,
the problem with using session windows is that you don't know which one is
the "first element" unless you keep some sort of state in the
WindowAssigner, right? Otherwise, the first element could spawn a window
and the non-first elements could have windows of length 0 that get merged
into the
RWenden created FLINK-4402:
--
Summary: Wrong metrics parameter names in documentation
Key: FLINK-4402
URL: https://issues.apache.org/jira/browse/FLINK-4402
Project: Flink
Issue Type: Bug
Thanks Till!
Kostas
> On Aug 16, 2016, at 3:30 PM, Till Rohrmann wrote:
>
> Cool design doc Klou. It's well described with a lot of details. I like it
> a lot :-) +1 for implementing the trigger DSL.
>
> Cheers,
> Till
>
> On Tue, Aug 16, 2016 at 3:18 PM, Kostas Kloudas
Cool design doc Klou. It's well described with a lot of details. I like it
a lot :-) +1 for implementing the trigger DSL.
Cheers,
Till
On Tue, Aug 16, 2016 at 3:18 PM, Kostas Kloudas wrote:
> Thanks for the feedback Ufuk!
> I will do that.
>
> > On Aug 16, 2016,
Thanks for the feedback Ufuk!
I will do that.
> On Aug 16, 2016, at 1:41 PM, Ufuk Celebi wrote:
>
> Hey Kostas! Thanks for sharing the documents. I think it makes sense
> to merge the two documents by moving the Google doc contents to the
> Wiki. I think they form one unit.
>
Hey Kostas! Thanks for sharing the documents. I think it makes sense
to merge the two documents by moving the Google doc contents to the
Wiki. I think they form one unit.
On Tue, Aug 16, 2016 at 12:34 PM, Kostas Kloudas
wrote:
> Hi all!
>
> I've created a FLIP for
Hi all!
I've created a FLIP for the trigger DSL. This is the triggers
that we want Apache Flink to support out-of-the-box. This proposal
builds on various discussions on the mailing list and aims at
serving as a base for further ones.
If I'm understanding correctly, you want something liked
"tumbling-session" windows. Session windows [1] do exactly what you
describe but are only evaluated after a certain period of inactivity,
but you want to evaluate the window every X minutes after the first
element for a key arrived, right? I
Hi,
I think we have to rethink a bit how the state interfaces work. Having an
interface where you snapshot a type T and restore a type T are not well
suited for dealing with job updates/state updates. For example, let's look
at the current Checkpointed interface. The value that you return is
Ufuk Celebi created FLINK-4401:
--
Summary: Add docs about ordering in streams
Key: FLINK-4401
URL: https://issues.apache.org/jira/browse/FLINK-4401
Project: Flink
Issue Type: Improvement
Hi Renkai,
thanks for the interest in Flink and the Table API/SQL! I would
recommend to maybe have a look into previous Pull Requests for new SQL
features such as INTERSECT [1] to get an overview of layers and classes.
I also recommend the design document [2] that describes the all planned
Hi,
Currently, Flink use Calcite for SQL parsing. So we use the StreamSQL grammer
proposed by Calcite[1] which we have to use the `STREAM` keyword in SQL. For
example, `SELECT *
FROM Orders` is a regular standard SQL and will be translated to a batch job.
If you want to statement a stream
Hi Jamie,
thanks for sharing your thoughts on this! You're raising some interesting
points.
Whether users find the lower-level primitives more intuitive depends on
their background I believe. From what I've seen, if users are coming from
the S4/Storm world and are used to the "compositional" way
Xiaogang Shi created FLINK-4400:
---
Summary: Leadership Election among JobManagers
Key: FLINK-4400
URL: https://issues.apache.org/jira/browse/FLINK-4400
Project: Flink
Issue Type: Sub-task
23 matches
Mail list logo