@Shengkai
> About the catalog jar hot updates
Currently we do not have a similar requirement, but if the catalog
management interface is opened, this can indeed realize the hot
loading of the catalog jar
> do we need to instantiate the Catalog immediately or defer to the usage
I think this can
ming li created FLINK-31008:
---
Summary: [Flink][Table Store] The Split allocation of the same
bucket in ContinuousFileSplitEnumerator may be out of order
Key: FLINK-31008
URL: https://issues.apache.org/jira/browse/FLINK-
Hi Feng,
It's still easy to conflict and be inconsistent even if we have only one
CatalogProvider, because CatalogProvider only provides readable interfaces
(listCatalogs, getCatalog). For example, you may register a catalog X, but
can't list it because it's not in the external metadata service.
tivanli created FLINK-31007:
---
Summary: The code generated by the IF function throws
NullPointerException
Key: FLINK-31007
URL: https://issues.apache.org/jira/browse/FLINK-31007
Project: Flink
Issu
Hi Dong,
Thanks for the reply. Got your points and it makes sense to me now~
Regards,
Dian
On Thu, Feb 9, 2023 at 3:45 PM Dong Lin wrote:
> Hi Dian,
>
> Thanks for the review! Please see my reply inline.
>
> Regards,
> Dong
>
> On Wed, Feb 8, 2023 at 11:58 AM Dian Fu wrote:
>
> > Hi Dong,
> >
jackylau created FLINK-31006:
Summary: job is not finished when using pipeline mode to run
bounded source like kafka/pulsar
Key: FLINK-31006
URL: https://issues.apache.org/jira/browse/FLINK-31006
Project:
Hi, Ran.
I think it's a little difficult to split the rule into two parts. Because
the ProjectDown and ReadingMetadata both need to reorder the fields. The
ReadingMetadata requires the metadata columns to be at the last and the
ProjectPushDown now is responsible to reorder the columns as the user
Zhu Zhu created FLINK-31005:
---
Summary: Release Testing: Verify FLIP-281 Supports speculative
execution of sinks
Key: FLINK-31005
URL: https://issues.apache.org/jira/browse/FLINK-31005
Project: Flink
Shammon created FLINK-31004:
---
Summary: Introduce data input and output stream for table store
Key: FLINK-31004
URL: https://issues.apache.org/jira/browse/FLINK-31004
Project: Flink
Issue Type: Sub-
weiqinpan created FLINK-31003:
-
Summary: Flink SQL IF / CASE WHEN Funcation incorrect
Key: FLINK-31003
URL: https://issues.apache.org/jira/browse/FLINK-31003
Project: Flink
Issue Type: Bug
Hi Feng.
I think your idea is very interesting!
1. I just wonder after initializing the Catalog, will the Session reuse the
same Catalog instance or build a new one for later usage? If we reuse the
same Catalog, I think it's more like lazy initialization. I am a
little prone to rebuild a new one
Jingsong Lee created FLINK-31002:
Summary: Provide data sampling query
Key: FLINK-31002
URL: https://issues.apache.org/jira/browse/FLINK-31002
Project: Flink
Issue Type: New Feature
Jingsong Lee created FLINK-31001:
Summary: Introduce Hive writer
Key: FLINK-31001
URL: https://issues.apache.org/jira/browse/FLINK-31001
Project: Flink
Issue Type: New Feature
Compo
Shammon created FLINK-31000:
---
Summary: Upgrade test units in flink-table-store-common to junit5
Key: FLINK-31000
URL: https://issues.apache.org/jira/browse/FLINK-31000
Project: Flink
Issue Type: Su
Shammon created FLINK-30999:
---
Summary: Introduce flink-table-store-test-utils for table store
Key: FLINK-30999
URL: https://issues.apache.org/jira/browse/FLINK-30999
Project: Flink
Issue Type: Sub-
+1 (binding)
- Verified legals (license headers and root LICENSE / NOTICE file). AFAICT
no dependencies require explicit acknowledgement in the NOTICE files.
- No binaries in staging area
- Built source with tests
- Verified signatures and hashes
- Web PR changes LGTM
Thanks Martijn!
Cheers,
Gor
Leonid Ilyevsky created FLINK-30998:
---
Summary: Add optional exception handler to
flink-connector-opensearch
Key: FLINK-30998
URL: https://issues.apache.org/jira/browse/FLINK-30998
Project: Flink
Shammon created FLINK-30997:
---
Summary: Refactor tests in connector to extends AbstractTestBase
Key: FLINK-30997
URL: https://issues.apache.org/jira/browse/FLINK-30997
Project: Flink
Issue Type: Sub
Martijn Visser created FLINK-30996:
--
Summary: Sync Kafka 1.17 commits from apache/flink repo to
flink-connector-kafka
Key: FLINK-30996
URL: https://issues.apache.org/jira/browse/FLINK-30996
Project:
Feng Wang created FLINK-30995:
-
Summary: Introduce ByteSerializer for Table Store
Key: FLINK-30995
URL: https://issues.apache.org/jira/browse/FLINK-30995
Project: Flink
Issue Type: New Feature
Feng Wang created FLINK-30993:
-
Summary: Introduce FloatSerializer for Table Store
Key: FLINK-30993
URL: https://issues.apache.org/jira/browse/FLINK-30993
Project: Flink
Issue Type: New Feature
Feng Wang created FLINK-30994:
-
Summary: Introduce DoubleSerializer for Table Store
Key: FLINK-30994
URL: https://issues.apache.org/jira/browse/FLINK-30994
Project: Flink
Issue Type: New Feature
Feng Wang created FLINK-30992:
-
Summary: Introduce ShortSerializer for Table Store
Key: FLINK-30992
URL: https://issues.apache.org/jira/browse/FLINK-30992
Project: Flink
Issue Type: New Feature
Feng Wang created FLINK-30991:
-
Summary: Introduce LongSerializer for Table Store
Key: FLINK-30991
URL: https://issues.apache.org/jira/browse/FLINK-30991
Project: Flink
Issue Type: New Feature
Martijn Visser created FLINK-30990:
--
Summary: Performance of has worsened DownstreamTasks.BATCH
Key: FLINK-30990
URL: https://issues.apache.org/jira/browse/FLINK-30990
Project: Flink
Issue T
FYI, the original mail never actually made it to the dev mailing list
(maybe got stuck in moderation queue).
On 08/02/2023 18:21, Mohsen Rezaei wrote:
Hi,
I was hoping to resurface this issue given that it affects any application
using the REST endpoints to run/submit jobs, causing confusion o
Thanks for your reply.
@Timo
> 2） avoid the default in-memory catalog and offer their catalog before a
> TableEnvironment session starts
> 3） whether this can be disabled and SHOW CATALOGS can be used for listing
> first without having a default catalog.
Regarding 2 and 3, I think this p
Hi,
I was hoping to resurface this issue given that it affects any application
using the REST endpoints to run/submit jobs, causing confusion on the
actual state of the submitted jobs in a cluster.
I've created a PR against the "master" branch, and I'd like to be able to
port it back to 1.16.2 an
shen created FLINK-30989:
Summary: Configuration table.exec.spill-compression.block-size not
take effect in batch job
Key: FLINK-30989
URL: https://issues.apache.org/jira/browse/FLINK-30989
Project: Flink
yuzelin created FLINK-30988:
---
Summary: Refactor E2E tests to get rid of managed table
Key: FLINK-30988
URL: https://issues.apache.org/jira/browse/FLINK-30988
Project: Flink
Issue Type: Sub-task
hi, yuxia, thanks for your feedback.
The point I am talking about here is that when implementing two interfaces
at the same time, the SupportsProjectionPushDown method can actually be
left blank, just use SupportsProjectionPushDown to mark it,
and then SupportsReadingMetadata can complete the phys
chenyuzhi created FLINK-30987:
-
Summary: output source exception for SocketStreamIterator
Key: FLINK-30987
URL: https://issues.apache.org/jira/browse/FLINK-30987
Project: Flink
Issue Type: Improv
yuzelin created FLINK-30986:
---
Summary: Refactor CreateTableITCase and DropTableITCase to get rid
of managed table
Key: FLINK-30986
URL: https://issues.apache.org/jira/browse/FLINK-30986
Project: Flink
Hi, Ran Tao.
Thanks for bring it up.
TBH, to me, it's not as so confusing.
Is that the fact that the applyReadableMetadata and applyProjection all will
pass producedDataType and the source conneector developer will
need to choose which one as the finnal output type?
As the Java doc of applyRea
ming li created FLINK-30985:
---
Summary: [Flink][table-store] Change the Splits allocation
algorithm of ContinuousFileSplitEnumerator in TableStore to a fair algorithm.
Key: FLINK-30985
URL: https://issues.apache.org/jira
Sergey Nuyanzin created FLINK-30984:
---
Summary: Remove explicit cast required by 3.1.x janino
Key: FLINK-30984
URL: https://issues.apache.org/jira/browse/FLINK-30984
Project: Flink
Issue Ty
luyuan created FLINK-30983:
--
Summary: the security.ssl.algorithms configuration does not take
effect in rest ssl
Key: FLINK-30983
URL: https://issues.apache.org/jira/browse/FLINK-30983
Project: Flink
37 matches
Mail list logo
