Happy to help get this merged.
Do we want to wait until the 1.15 branch is cut? The change is mostly
trivial (reformatting) but does make changes to the build system.
Seth
On Wed, Mar 9, 2022 at 9:45 AM Francesco Guardiani
wrote:
> Hi all,
> I've been spending some time prototyping a scalafmt
+1
Especially as SQL upgrades are right around the corner, it makes sense to
get our defaults right.
Seth
On Mon, Feb 28, 2022 at 7:14 AM Martijn Visser
wrote:
> +1 for setting this option to disabled by default. I believe failures
> should be brought forward as soon as possible, so they can
+1 non-binding
- built from source
- checked hashes and signatures
- started locally and deployed wordcount / stopped with savepoint /
restarted
- reviewed announcement post
Thanks for managing the release!
Seth
On Fri, Feb 25, 2022 at 7:30 AM Konstantin Knauf wrote:
> Hi everyone,
>
>
Seth Wiesman created FLINK-26374:
Summary: JSON_OBJECT may throw NullPointerException on nullable
column
Key: FLINK-26374
URL: https://issues.apache.org/jira/browse/FLINK-26374
Project: Flink
len,
>
> 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
&
; > >>> >> > > >
> > > >>> >> > > > I think there's potential for confusion here because we're
> > > >>> using the
> > > >>> >> > > > word *function
> > > >>> >> > >
Seth Wiesman created FLINK-26200:
Summary: Redirect statefun directly to docs
Key: FLINK-26200
URL: https://issues.apache.org/jira/browse/FLINK-26200
Project: Flink
Issue Type: Improvement
Hi Galen,
No, that is not currently supported, the current idiomatic way would be to
pass those values to the struct implementing the Statefun interface.
type MyFunc struct { someRuntimeInfo string } func (m *MyFunc) Invoke(ctx
statefun.Context, message statefun.Message) error { } func main() {
+1 (binding)
On Thu, Feb 3, 2022 at 8:39 AM Fabian Paul wrote:
> This connector is really a relict of the past.
>
> +1 (binding)
>
> Best,
> Fabian
>
> On Mon, Jan 31, 2022 at 11:47 AM Martijn Visser
> wrote:
> >
> > Hi everyone,
> >
> > I would like to open up a vote to remove the Twitter
+1 (binding)
On Thu, Feb 3, 2022 at 8:44 AM Fabian Paul wrote:
> Thanks for driving the deprecation efforts.
>
> +1 (binding)
>
> Best,
> Fabian
>
> On Mon, Jan 31, 2022 at 11:47 AM Martijn Visser
> wrote:
> >
> > Hi everyone,
> >
> > I would like to open up a vote to deprecate NiFi in Flink
Hi Jeff,
I think the class you're looking for is StatusWatermarkValve. Note that
this is fairly deep into the runtime stack.
Seth
On Tue, Feb 1, 2022 at 2:34 PM Jeff Carter wrote:
> Thanks, Till.
>
> That definitely helps a bit. I'm still not seeing where there is some idle
> variable that
+1 (non-binding)
- verified checksums and signatures
- built from source and ran e2e tests
- checked dependencies / licenses
- deployed greeter with golang sdk
- reviewed blog post
Cheers,
Seth
On Fri, Jan 28, 2022 at 4:22 AM Igal Shilman wrote:
> +1 (binding)
>
> - verified checksum and
+1
These are already a useful set of features to release to our users.
Seth
On Mon, Jan 24, 2022 at 8:45 AM Till Rohrmann wrote:
> Hi everyone,
>
> We would like to kick off a new StateFun release 3.2.0. The new release
> will include the new JavaScript SDK and some useful major features:
>
>
>> AFAIK state schema evolution should work both for native and canonical
>> savepoints.
Schema evolution does technically work for both formats, it happens after
the code paths have been unified, but the community has up until this point
considered that an unsupported feature. From my
+1 (non-binding)
- Verified signatures
- Checked diff
- Checked site PR
- Build from source and ran e2e tests
Seth
On Mon, Dec 20, 2021 at 10:59 AM Igal Shilman wrote:
> Hi everyone,
>
> Please review and vote on the release candidate #2 for the version 3.1.1 of
> Apache Flink Stateful
Hi Galen,
Sorry for the late reply, a lot of people are on sporadic schedules with
the holidays. A PR would be very welcome! I've gone ahead and assigned you
the Jira. And I'll watch the repo to review your pr.
cheers,
Seth
On Mon, Dec 20, 2021 at 8:24 AM Galen Warren
wrote:
> I just wanted
And I'm happy to help with the release.
On Thu, Dec 16, 2021 at 12:55 PM Seth Wiesman wrote:
> +1
>
> On Thu, Dec 16, 2021 at 12:37 PM Igal Shilman wrote:
>
>> Hi All,
>>
>> Following the recent Apache Flink releases due to the log4j vulnerability,
>> I'd l
+1
On Thu, Dec 16, 2021 at 12:37 PM Igal Shilman wrote:
> Hi All,
>
> Following the recent Apache Flink releases due to the log4j vulnerability,
> I'd like to propose an immediate StateFun release - 3.1.1.
> This release is basically the same as 3.1 but updates the Flink dependency
> to 1.13.3.
+1 (non-binding)
- Checked diff of all versions and verified dep upgrade
- Verified checksum and signatures
- Built 1.14 from source
- checked blog post
Seth
On Wed, Dec 15, 2021 at 10:22 AM Yu Li wrote:
> +1
>
> * Verified checksums and signatures
> * Reviewed website PR
>- Minor: left a
Seth Wiesman created FLINK-25333:
Summary: Harden UID management when constructing statefun universe
Key: FLINK-25333
URL: https://issues.apache.org/jira/browse/FLINK-25333
Project: Flink
Thank you for managing these updates Chesnay!
On Tue, Dec 14, 2021 at 3:51 PM Chesnay Schepler wrote:
> Since the maven artifacts have already been published we will use the
> next patch version for each release, i.e.:
> 1.11.6
> 1.12.7
> 1.13.5
> 1.14.2
>
> (We could technically just update
+1 (non-binding)
- Checked Log4J version and updated license preambles on all releases
- Verified signatures on sources
- Reviewed blog post
Seth
On Mon, Dec 13, 2021 at 1:42 PM Jing Ge wrote:
> +1 LGTM. Many thanks for your effort!
>
> On Mon, Dec 13, 2021 at 8:28 PM Chesnay Schepler
>
+1
I actually thought we had already dropped this FS. If anyone is still
relying on it in production, the file system abstraction in Flink has been
incredibly stable over the years. They should be able to use the 1.14 MapR
FS with later versions of Flink.
Seth
On Wed, Dec 8, 2021 at 10:03 AM
Seth Wiesman created FLINK-24912:
Summary: Migrate state processor API to DataStream API
Key: FLINK-24912
URL: https://issues.apache.org/jira/browse/FLINK-24912
Project: Flink
Issue Type
Seth Wiesman created FLINK-24834:
Summary: Add typed builders to DefaultRollingPolicy
Key: FLINK-24834
URL: https://issues.apache.org/jira/browse/FLINK-24834
Project: Flink
Issue Type
Seth Wiesman created FLINK-24833:
Summary: Prevent use of deprecated APIs in flink-examples
Key: FLINK-24833
URL: https://issues.apache.org/jira/browse/FLINK-24833
Project: Flink
Issue Type
@David Morávek great idea! I've opened a subtask to add
that check after we fix the existing deprecations.
Seth
On Mon, Nov 8, 2021 at 12:55 PM David Morávek wrote:
> Hi Seth, thanks for bringing this up. What do you think about placing a
> safeguard for this? We should be able to setup java
Also, please consider adding new examples if you are developing a new API!
It's a great addition to the documentation, and can help you workshop your
change from a usability perspective.
Seth
On Mon, Nov 8, 2021 at 9:34 AM Seth Wiesman wrote:
> Hi Everyone,
>
> I noticed recently
Seth Wiesman created FLINK-24831:
Summary: Upgrade DataStream Window examples
Key: FLINK-24831
URL: https://issues.apache.org/jira/browse/FLINK-24831
Project: Flink
Issue Type: Sub-task
Seth Wiesman created FLINK-24830:
Summary: Update DataStream WordCount example
Key: FLINK-24830
URL: https://issues.apache.org/jira/browse/FLINK-24830
Project: Flink
Issue Type: Sub-task
Seth Wiesman created FLINK-24829:
Summary: Rename example directories based on API
Key: FLINK-24829
URL: https://issues.apache.org/jira/browse/FLINK-24829
Project: Flink
Issue Type: Sub-task
Hi Everyone,
I noticed recently that many of the example applications in
`flink-examples/` rely on deprecated apis. I am going to work on upgrading
the examples for the current state of master. Going forward, if you
deprecate a public API please try and double check if that API is being
used in
Seth Wiesman created FLINK-24782:
Summary: Create 1.14 release branch for training repo
Key: FLINK-24782
URL: https://issues.apache.org/jira/browse/FLINK-24782
Project: Flink
Issue Type
Seth Wiesman created FLINK-24635:
Summary: Clean up flink-examples
Key: FLINK-24635
URL: https://issues.apache.org/jira/browse/FLINK-24635
Project: Flink
Issue Type: Improvement
Seth Wiesman created FLINK-24593:
Summary: Create Table API Quickstart
Key: FLINK-24593
URL: https://issues.apache.org/jira/browse/FLINK-24593
Project: Flink
Issue Type: Improvement
Seth Wiesman created FLINK-24516:
Summary: Modernize Maven Archetype
Key: FLINK-24516
URL: https://issues.apache.org/jira/browse/FLINK-24516
Project: Flink
Issue Type: Improvement
Seth Wiesman created FLINK-24464:
Summary: Metrics sometimes report negative backlog
Key: FLINK-24464
URL: https://issues.apache.org/jira/browse/FLINK-24464
Project: Flink
Issue Type
Seth Wiesman created FLINK-24373:
Summary: Remove BETA Tag from FLIP-27 Source Docs
Key: FLINK-24373
URL: https://issues.apache.org/jira/browse/FLINK-24373
Project: Flink
Issue Type
+1
On Mon, Sep 20, 2021 at 6:04 AM Chesnay Schepler wrote:
> +1
>
> On 20/09/2021 09:38, Martijn Visser wrote:
> > Hi all,
> >
> > I would like to start a vote on dropping the Scala Shell. This was
> > previously discussed in the mailing list [1]
> >
> > The vote will be open for at least 72
+1
The scala shell requires time and expertise that the contributors cannot
provide. It will be great to let the broader community have the opportunity
to foster and mature the scala shell outside the constraints imposed by the
ASF.
On Thu, Sep 16, 2021 at 9:02 AM Jeff Zhang wrote:
> Hi
Seth Wiesman created FLINK-24303:
Summary: SourceCoordinator exception may fail Session Cluster
Key: FLINK-24303
URL: https://issues.apache.org/jira/browse/FLINK-24303
Project: Flink
Issue
Seth Wiesman created FLINK-24301:
Summary: use Async transport on all statefun playground examples
Key: FLINK-24301
URL: https://issues.apache.org/jira/browse/FLINK-24301
Project: Flink
Seth Wiesman created FLINK-24253:
Summary: Load JdbcDialects via Service Loaders
Key: FLINK-24253
URL: https://issues.apache.org/jira/browse/FLINK-24253
Project: Flink
Issue Type
Seth Wiesman created FLINK-24110:
Summary: Filter null ComponentJsonObjects
Key: FLINK-24110
URL: https://issues.apache.org/jira/browse/FLINK-24110
Project: Flink
Issue Type: Improvement
Seth Wiesman created FLINK-24109:
Summary: Correct egress string serialization
Key: FLINK-24109
URL: https://issues.apache.org/jira/browse/FLINK-24109
Project: Flink
Issue Type: Improvement
+1 (non-binding)
- verified signatures and hashes
- Checked licenses
- ran mvn clean install -Prun-e2e-tests
- ran golang greeter and showcase from the playground [1]
Seth
[1] https://github.com/apache/flink-statefun-playground/pull/12
On Wed, Aug 25, 2021 at 9:44 AM Igal Shilman wrote:
> +1
Seth Wiesman created FLINK-23976:
Summary: Add additional availability timing metrics to Job
lifecycle events
Key: FLINK-23976
URL: https://issues.apache.org/jira/browse/FLINK-23976
Project: Flink
Seth Wiesman created FLINK-23951:
Summary: Add golang examples to playground
Key: FLINK-23951
URL: https://issues.apache.org/jira/browse/FLINK-23951
Project: Flink
Issue Type: Improvement
-1
There is an issue with the `go.mod` file which prevents it from properly
being released. I have opened a PR[1] .
This should not affect testing, this fix is only required to actually
publish the release.
[1] https://github.com/apache/flink-statefun/pull/260
On Mon, Aug 23, 2021 at 10:38 AM
Seth Wiesman created FLINK-23927:
Summary: Fix go.mod file for SDK release
Key: FLINK-23927
URL: https://issues.apache.org/jira/browse/FLINK-23927
Project: Flink
Issue Type: Bug
Seth Wiesman created FLINK-23878:
Summary: Minor improvements to golang sdk
Key: FLINK-23878
URL: https://issues.apache.org/jira/browse/FLINK-23878
Project: Flink
Issue Type: Improvement
+1 for the release
On Mon, Aug 16, 2021 at 8:25 AM Gordon Tai (戴資力) wrote:
> Hi Igal,
>
> Thanks a lot for starting this discussion!
>
> The list of features sounds like this will be a great release. As the list
> is already quite packed with major features, +1 to feature freeze on August
>
Seth Wiesman created FLINK-23728:
Summary: Support new state backend factory stack in State
Processor API
Key: FLINK-23728
URL: https://issues.apache.org/jira/browse/FLINK-23728
Project: Flink
Seth Wiesman created FLINK-23547:
Summary: StateFun does not execute integration tests
Key: FLINK-23547
URL: https://issues.apache.org/jira/browse/FLINK-23547
Project: Flink
Issue Type: Bug
Seth Wiesman created FLINK-23520:
Summary: Improve StateFun <-> DataStream Interop
Key: FLINK-23520
URL: https://issues.apache.org/jira/browse/FLINK-23520
Project: Flink
Issu
+1 (binding)
Seth
On Fri, Jul 23, 2021 at 7:31 AM Arvid Heise wrote:
> +1 (binding)
>
> On Wed, Jul 21, 2021 at 1:55 PM Piotr Nowojski
> wrote:
>
> > Hi everyone,
> >
> > I would like to start a vote on the FLIP-182 [1] which was discussed in
> > this
> > thread [2].
> > The vote will be open
Seth Wiesman created FLINK-23439:
Summary: Update "Local Installation" Page
Key: FLINK-23439
URL: https://issues.apache.org/jira/browse/FLINK-23439
Project: Flink
Issue Type: I
I will not need to port my latest additions to table connectors then.
>
> Best
>
> Etienne
>
> On 08/07/2021 17:28, Seth Wiesman wrote:
> > Hi Etienne,
> >
> > The `toDataStream` method supports converting to concrete Java types, not
> > just Row, which can include
+1
In my opinion, this limitation is perfectly fine for the MVP. Watermark
alignment is a long-standing issue and this already moves the ball so far
forward.
I don't expect this will cause many issues in practice, as I understand it
the FileSource always processes one split at a time, and in my
Hi Etienne,
The `toDataStream` method supports converting to concrete Java types, not
just Row, which can include your Avro specific-records. See example 2:
https://ci.apache.org/projects/flink/flink-docs-master/docs/dev/table/data_stream_api/#examples-for-todatastream
On Thu, Jul 8, 2021 at
Sorry if this is a naive question, I don't have any real Mesos experience.
Is it possible to deploy a standalone cluster on top of Mesos in the same
way you can with Kubernetes? If so, and there is still Mesos demand from
the community, we could document that process as the recommended deployment
+1 to the release.
It would be great if we could get FLINK-23073 into 1.13.2. There's already
an open PR and it unblocks upgrading the table API walkthrough in
apache/flink-playgrounds to 1.13.
Seth
On Mon, Jun 21, 2021 at 6:28 AM Yun Tang wrote:
> Hi Dawid,
>
> Thanks for driving this
Seth Wiesman created FLINK-23073:
Summary: Fix space handling in CSV timestamp parser
Key: FLINK-23073
URL: https://issues.apache.org/jira/browse/FLINK-23073
Project: Flink
Issue Type: Bug
Seth Wiesman created FLINK-22947:
Summary: Reduce DataSet visibility in documentation
Key: FLINK-22947
URL: https://issues.apache.org/jira/browse/FLINK-22947
Project: Flink
Issue Type
Seth Wiesman created FLINK-22906:
Summary: Add build time to Flink documentation
Key: FLINK-22906
URL: https://issues.apache.org/jira/browse/FLINK-22906
Project: Flink
Issue Type
Hi Everyone,
+1 for the Release Managers. Thank you all for volunteering.
@Till Rohrmann A common sentiment that I have heard
from many users is that upgrading off of 1.9 was very difficult. In
particular, a lot of people struggled to understand the new memory model.
Many users who required
Seth Wiesman created FLINK-22563:
Summary: Add migration guide for new StateBackend interfaces
Key: FLINK-22563
URL: https://issues.apache.org/jira/browse/FLINK-22563
Project: Flink
Issue
Seth Wiesman created FLINK-22554:
Summary: Support Kafka Topic Patterns in Kafka Ingress
Key: FLINK-22554
URL: https://issues.apache.org/jira/browse/FLINK-22554
Project: Flink
Issue Type
Seth Wiesman created FLINK-22242:
Summary: Improve missing attribute error on
GeneratedAddressedScopedStorage
Key: FLINK-22242
URL: https://issues.apache.org/jira/browse/FLINK-22242
Project: Flink
+1 (non-binding)
- Built from source and executed end to end tests
- Checked licenses and signatures
- Deployed remote Java SDK to gke cluster
- Took savepoint and statefully rescaled
Seth
On Thu, Apr 1, 2021 at 9:05 AM Konstantin Knauf wrote:
> +1 (non-binding)
>
> - mvn clean install
Seth Wiesman created FLINK-22052:
Summary: Add FLIP-142 changes to PyFlink
Key: FLINK-22052
URL: https://issues.apache.org/jira/browse/FLINK-22052
Project: Flink
Issue Type: Sub-task
Seth Wiesman created FLINK-21724:
Summary: Remove type annotation from python message.as_type
Key: FLINK-21724
URL: https://issues.apache.org/jira/browse/FLINK-21724
Project: Flink
Issue
Seth Wiesman created FLINK-21719:
Summary: Update statefun developer docs for new protocol
Key: FLINK-21719
URL: https://issues.apache.org/jira/browse/FLINK-21719
Project: Flink
Issue Type
Cool feature +1
There is a subsection called monitoring in the operations section of the
docs. It would fit nicely there.
Seth
On Tue, Mar 2, 2021 at 4:23 PM Alexander Fedulov
wrote:
> Hi Piotr,
>
> Thanks for the comments - all valid points.
> We should definitely document how the Flame
Strong +1
Having two planners is confusing to users and the diverging semantics make
it difficult to provide useful learning material. It is time to rip the
bandage off.
Seth
On Fri, Feb 26, 2021 at 12:54 AM Kurt Young wrote:
> change.>
>
> Hi Timo,
>
> First of all I want to thank you for
Seth Wiesman created FLINK-21489:
Summary: Hugo docs add two anchor links to headers
Key: FLINK-21489
URL: https://issues.apache.org/jira/browse/FLINK-21489
Project: Flink
Issue Type: Bug
Seth Wiesman created FLINK-21422:
Summary: Migrate StateFun docs to hugo
Key: FLINK-21422
URL: https://issues.apache.org/jira/browse/FLINK-21422
Project: Flink
Issue Type: Improvement
Seth Wiesman created FLINK-21384:
Summary: Automatically copy maven dependencies to clipboard on
click
Key: FLINK-21384
URL: https://issues.apache.org/jira/browse/FLINK-21384
Project: Flink
+1 (binding)
On Fri, Feb 12, 2021 at 8:25 AM Jark Wu wrote:
> +1 (binding)
>
> Best,
> Jark
>
> > 2021年2月12日 20:37，Dawid Wysakowicz 写道：
> >
> > +1 (binding)
> >
> > Best,
> >
> > Dawid
> >
> > On 12/02/2021 13:33, Timo Walther wrote:
> >> Hi everyone,
> >>
> >> I'd like to start a vote on
Seth Wiesman created FLINK-21369:
Summary: Document Checkpoint Storage
Key: FLINK-21369
URL: https://issues.apache.org/jira/browse/FLINK-21369
Project: Flink
Issue Type: Improvement
Seth Wiesman created FLINK-21363:
Summary: Fix baseurl in documentation
Key: FLINK-21363
URL: https://issues.apache.org/jira/browse/FLINK-21363
Project: Flink
Issue Type: Bug
tween master/release-1.11/release-1.12 branches we will
> need to remember to remove docs/content?
>
> Best,
> Piotrek
>
> śr., 10 lut 2021 o 16:08 Seth Wiesman napisał(a):
>
> > One thing at a time :)
> >
> > I'm creating tickets now for the ones on th
te? :P )
>
> Regarding the follow-ups raised in the PR, will you go over them and
> create tickets, or...?
>
> On 2/10/2021 3:40 PM, Seth Wiesman wrote:
> > Hi Everyone,
> >
> > I'm happy to say the migration of Flinks documentation to hugo is
> complete!
> &g
Hi Everyone,
I'm happy to say the migration of Flinks documentation to hugo is complete!
There will likely be some continued work over the next weeks to clean up
the css but the documentation freeze is over.
Please carefully read docs/README for details about how to build and work
with our new
Seth Wiesman created FLINK-21341:
Summary: Update state reader to return InputFormat
Key: FLINK-21341
URL: https://issues.apache.org/jira/browse/FLINK-21341
Project: Flink
Issue Type
Reminder
On Thu, Jan 28, 2021 at 9:07 AM Seth Wiesman wrote:
> Hi Everyone,
>
> As part of migrating the flink documentation to Hugo, I need to ask the
> community for a short documentation freeze. This will keep us from losing
> any contributions during the migration.
Hi Everyone,
As part of migrating the flink documentation to Hugo, I need to ask the
community for a short documentation freeze. This will keep us from losing
any contributions during the migration. I am proposing the freeze begin
next week February 2nd with the goal to get the change merged in
Seth Wiesman created FLINK-21193:
Summary: Migrate Flink Docs to Hugo
Key: FLINK-21193
URL: https://issues.apache.org/jira/browse/FLINK-21193
Project: Flink
Issue Type: Improvement
12:07 PM Aljoscha Krettek
> wrote:
>
> > +1
> >
> > Aljoscha
> >
> > On 2021/01/18 08:29, Seth Wiesman wrote:
> > >Hi devs,
> > >
> > >The discussion of the FLIP-157 [1] seems has reached a consensus through
> > >the mailing thread [
Congratulations!
On Wed, Jan 20, 2021 at 3:41 AM hailongwang <18868816...@163.com> wrote:
> Congratulations, Guowei!
>
> Best,
> Hailong
>
> 在 2021-01-20 15:55:24，"Till Rohrmann" 写道：
> >Congrats, Guowei!
> >
> >Cheers,
> >Till
> >
> >On Wed, Jan 20, 2021 at 8:32 AM Matthias Pohl
> >wrote:
> >
Hi Everyone,
I just merged in a PR to make the SQL / Table docs Blink planner only.
Going forward, you do not need to mark something as Blink only or explain
divergent semantics. Simply write the docs as if Blink were the only
planner.
There is a Legacy planner specific page[1]. If you add a
Addendum, 72 hours from now is Thursday the 21st :)
sorry for the mistake.
Seth
On Mon, Jan 18, 2021 at 8:41 AM Timo Walther wrote:
> +1
>
> Thanks for upgrading our docs infrastructure.
>
> Regards,
> Timo
>
> On 18.01.21 15:29, Seth Wiesman wrote:
> > H
Hi devs,
The discussion of the FLIP-157 [1] seems has reached a consensus through
the mailing thread [2]. I would like to start a vote for it.
The vote will be opened until 20th January (72h), unless there is an
objection or no enough votes.
Best,
Seth
[1]
Seth Wiesman created FLINK-20994:
Summary: Add public method to create TableEnvironment in PyFlink
Key: FLINK-20994
URL: https://issues.apache.org/jira/browse/FLINK-20994
Project: Flink
To expand on Till's answer, Flink uses Kryo whenever the type system does
not recognize a given type. If your job works with Kryo fallback disabled,
there should be no usage of Kryo serialization in your snapshots[1]. In
theory, it should be possible to upgrade Kryo using Flink's schema
migration
Great, if there aren't any other concerns I will open this up for a vote on
Monday.
Seth
On Thu, Jan 14, 2021 at 9:03 AM Seth Wiesman wrote:
> Happy to see there is enthusiasm for this change, let me try and answers
> each of these questions.
>
> @Jark Wu Hugo has proper supp
1年1月14日，18:21，Aljoscha Krettek 写道：
> > > >
> > > > +1
> > > >
> > > > The build times on Jekyll have just become to annoying for me. I
> > realize that that is also a function of how we structure our
> documentation,
> > and especia
+1
I would hope this helps attract more early adopters so if there are issues
we can resolve them in time for 1.13.
Seth
On Wed, Jan 13, 2021 at 5:13 AM Dawid Wysakowicz
wrote:
> Hi,
>
> Given that the BATCH execution mode was only released in 1.12 and a
> rather small impact of the suggested
Hi All,
I would like to start a discussion for FLIP-157: Migrating the Flink docs
from Jekyll to Hugo.
This will allow us:
- Proper internationalization
- Working Search
- Sub-second build time ;)
Please take a look and let me know what you think.
Seth
This makes sense, I have some questions about method names.
What do you think about renaming `dropDuplicates` to `deduplicate`? I don't
think that drop is the right word to use for this operation, it implies
records are filtered where this operator actually issues updates and
retractions. Also,
1 - 100 of 317 matches
Mail list logo
