apache/seatunnel

Search before asking I had searched in the feature and found no similar feature requirement. Description Background SeaTunnel cannot be started with a single pip install. Users who work in Python (notebooks, CI jobs, data / AI pipelines) have to download a distribution tarball, unpack it, set SEATUNNEL_HOME, make sure Java is available and install connector plugins by hand before they can run a config. This issue proposes a way for SeaTunnel to be installed and invoked directly from PyPI. What SeaTunnel has today No SeaTunnel package is published on PyPI (seatunnel, apache-seatunnel, seatunnel-cli all return 404). tools/seatunnel-python-sdk (merged in #10184, distribution name seatunnel, version 0.1) is only a REST client (httpx); it needs an already running engine. seatunnel-cli (seatunnel-cli/pyproject.toml, console script seatunnel) needs SEATUNNEL_HOME or a running engine for /run and /check and bundles no engine. It also has its own seatunnel_cli/rest.py that duplicates REST c

Description What happened With schema-changes.enabled = true, a Postgres-CDC → JDBC PostgreSQL job fails on ALTER TABLE ... ADD COLUMN when the new column has a user-defined type whose name needs quoting (upper case, reserved word) or is in a schema that is not on the search_path. The type name of the new column comes from Debezium (Column.typeName(), i.e. pg_type.typname from TypeRegistry), so it is neither quoted nor schema-qualified. PostgresTypeConverter keeps it as sourceType for Types.OTHER (L290, added in #11232), and PostgresDialect.buildAddColumnSQL copies sourceType into the DDL as-is when the source is also Postgres (L381). PostgreSQL folds MyRange to myrange, so the type is not found. Steps CREATE TYPE my_range_lc AS RANGE (subtype = int4); CREATE TYPE "MyRange" AS RANGE (subtype = int4); CREATE TABLE public.t5 (id int PRIMARY KEY, name text); INSERT INTO public.t5 VALUES (1, 'a'); -- start the job below and wait for the snapshot ALTER TABLE public.t5 ADD COLUMN r my_rang

Search before asking I had searched in the issues and found no similar issues. What happened 使用分离模式集群部署服务，集群作业量也就10个之内，每小时调度一次，一段时间之后就会报错 Caused by: java.lang.OutOfMemoryError: Metaspace SeaTunnel Version 2.3.13 SeaTunnel Config 提交作业就会报错，和作业配置无关 Running Command java -Dlog4j2.contextSelector=org.apache.logging.log4j.core.async.AsyncLoggerContextSelector -Dlog4j2.isThreadContextMapInheritable=true -DAsyncLogger.ThreadNameStrategy=UNCACHED -Dhazelcast.logging.type=log4j2 -Dlog4j2.configurationFile=/opt/seatunnel/config/log4j2.properties -Dseatunnel.logs.path=/opt/seatunnel/logs -Dseatunnel.logs.file_name=seatunnel-engine-worker -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/tmp/seatunnel/dump/zeta-server -XX:MaxMetaspaceSize=2g -XX:+UseG1GC -Dseatunnel.config=/opt/seatunnel/config/seatunnel.yaml -Dhazelcast.config=/opt/seatunnel/config/hazelcast-worker.yaml -Xms24G -c

Purpose This is a design discussion, not an implementation proposal. We would like feedback on a cohesive File Connector direction that makes parallel reads correct for structured files and creates a production-safe ingestion contract for images, audio, and video. Alternative designs and a formal STIP are very welcome. Current observations The File Connector already has useful foundations: FileSourceSplit carries a byte range and has fileIdentity and endContentAnchor fields: https://github.com/apache/seatunnel/blob/dev/seatunnel-connectors-v2/connector-file/connector-file-base/src/main/java/org/apache/seatunnel/connectors/seatunnel/file/source/split/FileSourceSplit.java enable_file_split currently plans text-like ranges by finding the next raw row delimiter, while Parquet uses a separate strategy: https://github.com/apache/seatunnel/blob/dev/seatunnel-connectors-v2/connector-file/connector-file-base/src/main/java/org/apache/seatunnel/connectors/seatunnel/file/source/split/AccordingToS

Search before asking I searched the existing feature issues and found no open request covering this enhancement. Description SeaTunnel already provides FieldEncrypt with AES-CBC/AES-GCM and a directly configured key. This issue proposes making it suitable for production use while keeping the implementation provider-neutral and backward compatible. SeaTunnel should offer optional official integrations for common cloud KMS/Vault services and expose the same SPI for custom enterprise providers. The detailed API, ciphertext layout, and provider packaging should be finalized during design review. This issue defines the required capabilities and safety boundaries rather than prescribing a complete implementation. Goals 1. Pluggable key providers and data ciphers Preserve the existing static-key configuration. Keep key acquisition and data encryption as separate extension points: KeyProvider determines where key material comes from, while DataCipher/Encryptor determines how field values a