Yun Gao created FLINK-26322:
---
Summary: Test FileSink compaction manually
Key: FLINK-26322
URL: https://issues.apache.org/jira/browse/FLINK-26322
Project: Flink
Issue Type: Sub-task
Matthias Pohl created FLINK-26321:
-
Summary:
KafkaSinkITCase.testWriteRecordsToKafkaWithExactlyOnceGuarantee fails on azure
Key: FLINK-26321
URL: https://issues.apache.org/jira/browse/FLINK-26321
hehuiyuan created FLINK-26320:
-
Summary: Update hive doc for 1 m->1 min
Key: FLINK-26320
URL: https://issues.apache.org/jira/browse/FLINK-26320
Project: Flink
Issue Type: Improvement
Yun Gao created FLINK-26319:
---
Summary: CastFunctionITCase.testFunction failed on azure
Key: FLINK-26319
URL: https://issues.apache.org/jira/browse/FLINK-26319
Project: Flink
Issue Type: Bug
Yun Gao created FLINK-26318:
---
Summary: ChangelogCompatibilityITCase.testRestore failed on azure
Key: FLINK-26318
URL: https://issues.apache.org/jira/browse/FLINK-26318
Project: Flink
Issue Type:
Yun Gao created FLINK-26317:
---
Summary: flink-yarn-tests Exit code 137 returned from process
Key: FLINK-26317
URL: https://issues.apache.org/jira/browse/FLINK-26317
Project: Flink
Issue Type: Bug
Yang Wang created FLINK-26316:
-
Summary: Savepoint restore setting does not take effect when
configured via dynamic config options
Key: FLINK-26316
URL: https://issues.apache.org/jira/browse/FLINK-26316
Janick Wu created FLINK-26315:
-
Summary: Stream job which have multily region would not recover
when connection with zookeeper/hbase lost.
Key: FLINK-26315
URL: https://issues.apache.org/jira/browse/FLINK-26315
Yun Gao created FLINK-26314:
---
Summary: StreamingCompactingFileSinkITCase.testFileSink failed on
azure
Key: FLINK-26314
URL: https://issues.apache.org/jira/browse/FLINK-26314
Project: Flink
Issue
Yunfeng Zhou created FLINK-26313:
Summary: Support Online KMeans in Flink ML
Key: FLINK-26313
URL: https://issues.apache.org/jira/browse/FLINK-26313
Project: Flink
Issue Type: New Feature
Yeah, good point. I wasn't considering that someone else might be
implementing that interface. Practically, I think that's pretty unlikely,
but good question.
On Tue, Feb 22, 2022 at 6:36 PM Austin Cawley-Edwards <
austin.caw...@gmail.com> wrote:
> I think the only complication with adding
I think the only complication with adding `WithContext` to the interface is
that it makes it breaking :/ If it were the concrete implementation, we'd
have more flexibility. I'm not sure what guarantees are on those interfaces
though – @sjwies...@gmail.com, wdyt?
On Tue, Feb 22, 2022 at 4:19 PM
Madhav Kelkar created FLINK-26312:
-
Summary: Doc bug - newly introduced `INITIALIZING` state doesn't
appear internal docs
Key: FLINK-26312
URL: https://issues.apache.org/jira/browse/FLINK-26312
I think I would choose the WithContext method at this point, assuming that
the implementation keeps any instance of the stateful context immutable
(which should be doable). It's the simplest option IMO, simpler than an
adapter approach. Thanks for the suggestion.
My slight preference would be to
>
> What does "SomeOtherFunc" need with the statefun context
>
> I think it's hard to answer this question, in a general sense. Depending
> on what is being done, it might need to read a value from statefun Storage,
> write one back, etc.
To me, this indicates that the context is responsible for
Alexander Fedulov created FLINK-26311:
-
Summary: Test CsvFormat
Key: FLINK-26311
URL: https://issues.apache.org/jira/browse/FLINK-26311
Project: Flink
Issue Type: Improvement
Ahmed Hamdy created FLINK-26310:
---
Summary: [FLIP-171] Add AsyncSinkWriterConfig class
Key: FLINK-26310
URL: https://issues.apache.org/jira/browse/FLINK-26310
Project: Flink
Issue Type:
>
> One place we could look is the `net/http` Request, which has a
> `WithContext` method[1] that seems to expose the behavior we're looking
> for.
>
I considered something similar, too, and upon another look, maybe I
dismissed it too quickly. The concern I had was that an implementation that
Hey,
Sorry for the late response – been off the ML for a few days.
I am not too familiar with other Go libs that use a custom context. One
place we could look is the `net/http` Request, which has a `WithContext`
method[1] that seems to expose the behavior we're looking for. That could
be added
Zichen Liu created FLINK-26309:
--
Summary: Add a polling strategy to determine whether Localstack
test container has started
Key: FLINK-26309
URL: https://issues.apache.org/jira/browse/FLINK-26309
Márton Balassi created FLINK-26308:
--
Summary: Remove need for flink-operator clusterrole
Key: FLINK-26308
URL: https://issues.apache.org/jira/browse/FLINK-26308
Project: Flink
Issue Type:
Thanks Francesco,
The two arguments you posted, further strengthen the need to make it
DISABLED by default.
On Tue, Feb 22, 2022 at 12:10 PM Francesco Guardiani <
france...@ververica.com> wrote:
> Hi all,
> I'm +1 with what everything you said Marios.
>
> I'm gonna add another argument on top
郭元方 created FLINK-26307:
---
Summary: 当事件时间在（Long.MIN_VALUE ，-windowsize）时，不能正确的求到开启窗口的起始时间
Key: FLINK-26307
URL: https://issues.apache.org/jira/browse/FLINK-26307
Project: Flink
Issue Type: Improvement
Hi Marco,
Great to hear that you put some thought into the topic. Judging from
the past we already tried once to support multiple external versions
within one connector (ElasticSearch) and it complicates things a lot.
So if it makes your development easier to create a different module
that should
Roman Khachatryan created FLINK-26306:
-
Summary: Triggered checkpoints can be delayed by discarding shared
state
Key: FLINK-26306
URL: https://issues.apache.org/jira/browse/FLINK-26306
Project:
Zichen Liu created FLINK-26305:
--
Summary: KinesisFirehoseSinkITCase writes duplicates to Localstack
Key: FLINK-26305
URL: https://issues.apache.org/jira/browse/FLINK-26305
Project: Flink
Issue
EDIT: Wrong link before https://issues.apache.org/jira/browse/FLINK-26304
On Tue, Feb 22, 2022 at 4:55 PM Fabian Paul wrote:
>
> Hi Konstantin,
>
> Thanks for all the efforts driving the release. From my side,
> FLINK-26018 can also be seen as some kind of new feature that was
> planned but
Hi Konstantin,
Thanks for all the efforts driving the release. From my side,
FLINK-26018 can also be seen as some kind of new feature that was
planned but never implemented. Of course, it would be great to have it
because it currently blocks the migration from the FlinkKafkaConsumer
to the
Fabian Paul created FLINK-26304:
---
Summary: GlobalCommitter can receive failed committables
Key: FLINK-26304
URL: https://issues.apache.org/jira/browse/FLINK-26304
Project: Flink
Issue Type:
Thanks, Seth.
I'm curious what you would think about an approach that kept everything
as-is, by default, but allowed for a separated context and runtime in the
Invoke method, on an opt-in basis, via an adapter?
On Tue, Feb 22, 2022 at 10:28 AM Seth Wiesman wrote:
> Hi all,
>
> I believe the
Hi all,
I believe the discussion revolved around:
1. fewer parameters
2. better aligned with other language sdks
3. we found precedent in other libraries (apologies this was long enough
ago I cannot remember which ones, I'm looking through old discussions now)
I would in general champion a
Hi Martin,
I took a look at how other plugins have handled the migration and I have the
feeling most oped for a new connector (new module), instead of adding some
more packages to the existing one. Should I take the same route ?
The current connector builds a fat-jar that included version 3.0
Chesnay Schepler created FLINK-26303:
Summary: Print rat-plugin violations to the console
Key: FLINK-26303
URL: https://issues.apache.org/jira/browse/FLINK-26303
Project: Flink
Issue
Chesnay Schepler created FLINK-26302:
Summary: Upgrat rat-plugin to 1.13
Key: FLINK-26302
URL: https://issues.apache.org/jira/browse/FLINK-26302
Project: Flink
Issue Type: Technical Debt
Jing Ge created FLINK-26301:
---
Summary: Test AvroParquet format
Key: FLINK-26301
URL: https://issues.apache.org/jira/browse/FLINK-26301
Project: Flink
Issue Type: Improvement
Components:
Zichen Liu created FLINK-26300:
--
Summary: KinesisFirehoseSinkITCase failed on azure IOException
Key: FLINK-26300
URL: https://issues.apache.org/jira/browse/FLINK-26300
Project: Flink
Issue
Dawid Wysakowicz created FLINK-26299:
Summary: Reintroduce old
JobClient#triggerSavepoint,stopWithSavepoint methods
Key: FLINK-26299
URL: https://issues.apache.org/jira/browse/FLINK-26299
Chesnay Schepler created FLINK-26298:
Summary: [JUnit5 Migration] Module: flink-rpc-core
Key: FLINK-26298
URL: https://issues.apache.org/jira/browse/FLINK-26298
Project: Flink
Issue
Marios Trivyzas created FLINK-26297:
---
Summary: Introduce ExecutionNodeConfig which will be used in all
Exec Nodes
Key: FLINK-26297
URL: https://issues.apache.org/jira/browse/FLINK-26297
Project:
Matthias Pohl created FLINK-26296:
-
Summary: Add missing documentation
Key: FLINK-26296
URL: https://issues.apache.org/jira/browse/FLINK-26296
Project: Flink
Issue Type: Sub-task
Hi Galen,
Thanks for explaining the problems with the current design. I think I've
already learned quite a bit wrt Go thanks to you :-)
>From what you describe it seems indeed a bit restrictive to let the
statefun.Context contain the context.Context w/o giving access to it.
Maybe @Seth
Wiesman
Sergey Nuyanzin created FLINK-26295:
---
Summary: 'HELP ;', 'QUIT ;' and other sql-client commands fail
with CalciteException: Non-query expression encountered in illegal context
Key: FLINK-26295
URL:
Hi all,
I'm +1 with what everything you said Marios.
I'm gonna add another argument on top of that: the "legacy-cast-behavior"
has also a broken type inference, leading to incorrect results or further
errors down in the pipeline[1]. For example, take this:
SELECT COALESCE(CAST('a' AS INT), 0)
Hello all!
I would like to bring back the discussion regarding the
*table.exec.legacy-cast-behaviour*
configuration option which we are introducing with Flink *1.15*. This
option provides the users
with the flexibility to continue using the old (incorrect, according to SQL
standards) behaviour
of
Jing Ge created FLINK-26294:
---
Summary: Using fixed description for ArchUnit rules
Key: FLINK-26294
URL: https://issues.apache.org/jira/browse/FLINK-26294
Project: Flink
Issue Type: Improvement
Jingsong Lee created FLINK-26293:
Summary: Store log offsets in snapshot
Key: FLINK-26293
URL: https://issues.apache.org/jira/browse/FLINK-26293
Project: Flink
Issue Type: Sub-task
46 matches
Mail list logo
