Hi Rui~
Description of the database is obtained from `CatalogDatabase#getDescription()`
method, which is implement by CatalogDatebaseImpl. Users don’t need to specify
the description.
Best,
Terry Wang
> 2019年11月7日 15:40，Rui Li 写道：
>
> Thanks Terry for driving this forward.
> Got one
Thanks Terry for driving this forward.
Got one question about DESCRIBE DATABASE: the results display comment and
description of a database. While comment can be specified when a database
is created, I don't see how users can specify description of the database?
On Thu, Nov 7, 2019 at 4:16 AM
Hi community， as I know I can use idle state retention time to clear the
flink sql task state,I have a question is that how long the flink sql task
state default ttl is . Thanks
Zhenghua Gao created FLINK-14650:
Summary: Thread safety issue in the piece of code example of
dev/stream/testing document
Key: FLINK-14650
URL: https://issues.apache.org/jira/browse/FLINK-14650
Jark Wu created FLINK-14649:
---
Summary: Flatten all the connector properties keys to make it easy
to configure in DDL
Key: FLINK-14649
URL: https://issues.apache.org/jira/browse/FLINK-14649
Project: Flink
Ruiliang Li created FLINK-14648:
---
Summary: When using udaf, the startup task has a “Cannot determine
simple type name 'com' ” exception
Key: FLINK-14648
URL: https://issues.apache.org/jira/browse/FLINK-14648
Jark Wu created FLINK-14647:
---
Summary: Improve the exception message when required property is
not matched
Key: FLINK-14647
URL: https://issues.apache.org/jira/browse/FLINK-14647
Project: Flink
Jiayi Liao created FLINK-14646:
--
Summary: Check null for key in KeyGroupStreamPartitioner
Key: FLINK-14646
URL: https://issues.apache.org/jira/browse/FLINK-14646
Project: Flink
Issue Type:
Jark Wu created FLINK-14645:
---
Summary: Data types defined in DDL will lose precision and
nullability when converting to properties
Key: FLINK-14645
URL: https://issues.apache.org/jira/browse/FLINK-14645
Jark Wu created FLINK-14644:
---
Summary: Improve CREATE TABLE DDL WITH properties
Key: FLINK-14644
URL: https://issues.apache.org/jira/browse/FLINK-14644
Project: Flink
Issue Type: Improvement
Zhu Zhu created FLINK-14643:
---
Summary: Deprecate metric `fullRestarts`
Key: FLINK-14643
URL: https://issues.apache.org/jira/browse/FLINK-14643
Project: Flink
Issue Type: Bug
Components:
Victor Wong created FLINK-14642:
---
Summary: Flink TupleSerializer and CaseClassSerializer shoud
support copy NULL values
Key: FLINK-14642
URL: https://issues.apache.org/jira/browse/FLINK-14642
Project:
Zhu Zhu created FLINK-14641:
---
Summary: Fix description of metric `fullRestarts`
Key: FLINK-14641
URL: https://issues.apache.org/jira/browse/FLINK-14641
Project: Flink
Issue Type: Bug
Hi,
If you just want to debug, maybe you can do this in UT class in module
flink-runtime :) so that you do not need to handle the dependency problem,
and access problem.
Best,
Congxian
Jark Wu 于2019年11月6日周三 下午3:39写道：
> Btw, user questions should be asked in user@f.a.o or user-zh@f.a.o. The
>
Hi Yun,
Thank you for your detailed explanation,It brings me a lot to research. I
think
1. I should try reduce number of "state.checkpoints.num-retained", maybe to
3, which could decrease amount of shared folder.
2. Does Flink 1.9.0 has the possibility of orphan files? Seems the answer
is yes,
+1 for separate repo right now for all the good discussed
On Wed, Nov 6, 2019 at 3:35 PM Becket Qin wrote:
> +1 on having a separate repository.
>
> I am always an advocate of separate repositories. All the substantial
> benefits of doing that are quite convincing. The only reason we might want
vinoyang created FLINK-14640:
Summary: Change Type of Field currentExecutions from
ConcurrentHashMap to HashMap
Key: FLINK-14640
URL: https://issues.apache.org/jira/browse/FLINK-14640
Project: Flink
hehuiyuan created FLINK-14639:
-
Summary: Fix the document of Metircs that has an error for `User
Scope`
Key: FLINK-14639
URL: https://issues.apache.org/jira/browse/FLINK-14639
Project: Flink
+1 on having a separate repository.
I am always an advocate of separate repositories. All the substantial
benefits of doing that are quite convincing. The only reason we might want
to make Stateful Function in main repo is probably because it looks just
like CEP, Gelly and other libraries that
Bowen Li created FLINK-14638:
Summary: move functions related docs to a new single, unified dir
/dev/table/functions
Key: FLINK-14638
URL: https://issues.apache.org/jira/browse/FLINK-14638
Project: Flink
Thanks.
As Terry and I discussed offline yesterday, we added a new section to
explain the detailed implementation plan.
+1 (binding) from me.
Bowen
On Tue, Nov 5, 2019 at 6:33 PM Terry Wang wrote:
> Hi Bowen:
> Thanks for your feedback.
> Your opinion convinced me and I just remove the
Andrey Zagrebin created FLINK-14637:
---
Summary: Introduce framework off heap memory config
Key: FLINK-14637
URL: https://issues.apache.org/jira/browse/FLINK-14637
Project: Flink
Issue Type:
Gary Yao created FLINK-14636:
Summary: Handle schedule mode
LAZY_FROM_SOURCES_WITH_BATCH_SLOT_REQUEST correctly in DefaultScheduler
Key: FLINK-14636
URL: https://issues.apache.org/jira/browse/FLINK-14636
Stephan Ewen created FLINK-14635:
Summary: Don't use relocated imports in Kinesis End-2-End Tests
Key: FLINK-14635
URL: https://issues.apache.org/jira/browse/FLINK-14635
Project: Flink
Issue
Eric Lee created FLINK-14634:
Summary: Metric Option of 'metrics.scope.delimiter' won't work
probably.
Key: FLINK-14634
URL: https://issues.apache.org/jira/browse/FLINK-14634
Project: Flink
Andrey Zagrebin created FLINK-14633:
---
Summary: Account for netty direct allocations in direct memory
limit (Queryable state)
Key: FLINK-14633
URL: https://issues.apache.org/jira/browse/FLINK-14633
Gary Yao created FLINK-14632:
Summary:
ExecutionGraphSchedulingTest.testSlotReleasingFailsSchedulingOperation deadlocks
Key: FLINK-14632
URL: https://issues.apache.org/jira/browse/FLINK-14632
Project:
Andrey Zagrebin created FLINK-14631:
---
Summary: Account for netty direct allocations in direct memory
limit
Key: FLINK-14631
URL: https://issues.apache.org/jira/browse/FLINK-14631
Project: Flink
Hi Dawid,
In general I agree if we can provide a completely unified way of handling
this registries that would be great but I wonder if that makes sense in the
long term. While the cloudera schema registry only supports Avro at the
moment, it aims to support other formats in the future, and
Are still open questions here?
Or can I treat this discussion as converged in the sense of concluding that:
- we start initially with a separate repository to allow for individual
releases in the early stages
- we later revisit this discussion once the project is a bit further
along and more
Till Rohrmann created FLINK-14630:
-
Summary: Yarn tests no longer create jobmanager log files
Key: FLINK-14630
URL: https://issues.apache.org/jira/browse/FLINK-14630
Project: Flink
Issue
Hi Gyula,
I did not want to discourage this contribution. I do agree we should
treat this connector equally to the confluent's schema registry. I just
wanted to express my uncertainty about general approach to new
connectors contributions. By no means I wanted to discourage this
contribution.
As
Gary Yao created FLINK-14628:
Summary: Wordcount on Docker test (custom fs plugin) fails on
Travis
Key: FLINK-14628
URL: https://issues.apache.org/jira/browse/FLINK-14628
Project: Flink
Issue
Hi Jark,
Thanks for your suggestion!
Change the title and wait for more comments.
Best,
Terry Wang
> 2019年11月6日 15:52，Jark Wu 写道：
>
> Hi Terry,
>
> I would suggest to change the title a bit.
> For example, "Improve & Refactor TableEnvironment APIs".
> Or more specifically, "Improve &
Zili Chen created FLINK-14627:
-
Summary: Refactor ExecutionGraph creation in tests as
TestingExecutionGraphBuilder
Key: FLINK-14627
URL: https://issues.apache.org/jira/browse/FLINK-14627
Project: Flink
35 matches
Mail list logo
