[GitHub] [inlong] dockerzhang merged pull request #8189: [INLONG-8188][Manager] Support querying audit information by sink id
dockerzhang merged PR #8189: URL: https://github.com/apache/inlong/pull/8189 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@inlong.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[inlong] branch master updated: [INLONG-8188][Manager] Support querying audit information by sink id (#8189)
This is an automated email from the ASF dual-hosted git repository.
dockerzhang pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/inlong.git
The following commit(s) were added to refs/heads/master by this push:
new 2c378c447e [INLONG-8188][Manager] Support querying audit information
by sink id (#8189)
2c378c447e is described below
commit 2c378c447e4a5916026910a1c50d4e6d24519b26
Author: fuweng11 <76141879+fuwen...@users.noreply.github.com>
AuthorDate: Thu Jun 8 15:20:59 2023 +0800
[INLONG-8188][Manager] Support querying audit information by sink id (#8189)
---
.../client/api/inner/client/AuditClient.java | 69 ++
.../client/api/inner/client/ClientFactory.java | 2 +
.../manager/client/api/service/AuditApi.java | 38
.../inlong/manager/pojo/audit/AuditRequest.java| 3 +
.../service/core/impl/AuditServiceImpl.java| 8 ++-
5 files changed, 118 insertions(+), 2 deletions(-)
diff --git
a/inlong-manager/manager-client/src/main/java/org/apache/inlong/manager/client/api/inner/client/AuditClient.java
b/inlong-manager/manager-client/src/main/java/org/apache/inlong/manager/client/api/inner/client/AuditClient.java
new file mode 100644
index 00..8fab6f371b
--- /dev/null
+++
b/inlong-manager/manager-client/src/main/java/org/apache/inlong/manager/client/api/inner/client/AuditClient.java
@@ -0,0 +1,69 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.inlong.manager.client.api.inner.client;
+
+import org.apache.inlong.manager.client.api.ClientConfiguration;
+import org.apache.inlong.manager.client.api.service.AuditApi;
+import org.apache.inlong.manager.client.api.util.ClientUtils;
+import org.apache.inlong.manager.common.enums.ErrorCodeEnum;
+import org.apache.inlong.manager.common.util.Preconditions;
+import org.apache.inlong.manager.pojo.audit.AuditRequest;
+import org.apache.inlong.manager.pojo.audit.AuditVO;
+import org.apache.inlong.manager.pojo.common.Response;
+
+import java.util.List;
+
+/**
+ * Client for {@link AuditApi}.
+ */
+public class AuditClient {
+
+private final AuditApi auditApi;
+
+public AuditClient(ClientConfiguration configuration) {
+auditApi =
ClientUtils.createRetrofit(configuration).create(AuditApi.class);
+}
+
+/**
+ * Query audit data for list by condition
+ *
+ * @param request The audit request of query condition
+ * @return The result of query
+ */
+public List list(AuditRequest request) {
+Preconditions.expectNotNull(request, "request cannot be null");
+Preconditions.expectNotBlank(request.getInlongGroupId(),
ErrorCodeEnum.INVALID_PARAMETER,
+"inlong group id cannot be empty");
+Preconditions.expectNotBlank(request.getInlongStreamId(),
ErrorCodeEnum.INVALID_PARAMETER,
+"inlong stream id cannot be empty");
+Response> response =
ClientUtils.executeHttpCall(auditApi.list(request));
+ClientUtils.assertRespSuccess(response);
+return response.getData();
+}
+
+/**
+ * Refresh the base item of audit cache.
+ *
+ * @return true if not exception, or false if it has exception
+ */
+public Boolean refreshCache(AuditRequest request) {
+Response response =
ClientUtils.executeHttpCall(auditApi.refreshCache());
+ClientUtils.assertRespSuccess(response);
+return response.getData();
+}
+}
diff --git
a/inlong-manager/manager-client/src/main/java/org/apache/inlong/manager/client/api/inner/client/ClientFactory.java
b/inlong-manager/manager-client/src/main/java/org/apache/inlong/manager/client/api/inner/client/ClientFactory.java
index 2642509672..3b9cbdc3be 100644
---
a/inlong-manager/manager-client/src/main/java/org/apache/inlong/manager/client/api/inner/client/ClientFactory.java
+++
b/inlong-manager/manager-client/src/main/java/org/apache/inlong/manager/client/api/inner/client/ClientFactory.java
@@ -52,6 +52,7 @@ public class ClientFactory {
private final WorkflowApproverClient workflowApproverClient;
private final WorkflowEventClient workflowEventClient;
private final InlongConsumeClient consumeClient;
+pr
[GitHub] [inlong-website] chestnut-c opened a new issue, #770: [Improve][Doc] update design and concept extending data node for manager
chestnut-c opened a new issue, #770: URL: https://github.com/apache/inlong-website/issues/770 ### Description update design and concept extending data node for manager by https://github.com/apache/inlong/pull/8181 ### Are you willing to submit PR? - [X] Yes, I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@inlong.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [inlong-website] chestnut-c opened a new pull request, #771: [INLONG-770][Doc]Update design and concept extending data node for manager
chestnut-c opened a new pull request, #771: URL: https://github.com/apache/inlong-website/pull/771 [INLONG-770][Doc]Update design and concept extending data node for manager - Fixes #770 ### Motivation Update design and concept extending data node for manager by https://github.com/apache/inlong/pull/8181 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@inlong.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [inlong] bluewang opened a new pull request, #8191: [INLONG-8190][Dashboard] PostgreSQL source and Iceberg sink optimization
bluewang opened a new pull request, #8191: URL: https://github.com/apache/inlong/pull/8191 ### Prepare a Pull Request *(Change the title refer to the following example)* - Title Example: [INLONG-XYZ][Component] Title of the pull request *(The following *XYZ* should be replaced by the actual [GitHub Issue](https://github.com/apache/inlong/issues) number)* - Fixes https://github.com/apache/inlong/issues/8190 ### Motivation *Explain here the context, and why you're making that change. What is the problem you're trying to solve?* ### Modifications *Describe the modifications you've done.* ### Verifying this change   -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@inlong.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [inlong] gosonzhang commented on issue #8192: [Bug][DataProxy] The topic name generated by dataproxy is incorrect
gosonzhang commented on issue #8192: URL: https://github.com/apache/inlong/issues/8192#issuecomment-1582339975 @fuweng11, I don't understand, the implementation[1]  is actually directly migrated [2]:  Is there a problem with the previous logic, then why is there no error reported? 1. https://github.com/apache/inlong/blob/master/inlong-dataproxy/dataproxy-source/src/main/java/org/apache/inlong/dataproxy/config/holder/MetaConfigHolder.java#L375 2. https://github.com/apache/inlong/blob/branch-1.7/inlong-dataproxy/dataproxy-source/src/main/java/org/apache/inlong/dataproxy/sink/mq/kafka/KafkaHandler.java#L150 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@inlong.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [inlong] fuweng11 commented on issue #8192: [Bug][DataProxy] The topic name generated by dataproxy is incorrect
fuweng11 commented on issue #8192: URL: https://github.com/apache/inlong/issues/8192#issuecomment-1582345304 > @fuweng11, I don't understand, the implementation[1]  > > is actually directly migrated [2]:  > > Is there a problem with the previous logic, then why is there no error reported? > > 1. https://github.com/apache/inlong/blob/master/inlong-dataproxy/dataproxy-source/src/main/java/org/apache/inlong/dataproxy/config/holder/MetaConfigHolder.java#L375 > 2. https://github.com/apache/inlong/blob/branch-1.7/inlong-dataproxy/dataproxy-source/src/main/java/org/apache/inlong/dataproxy/sink/mq/kafka/KafkaHandler.java#L150 Yes, this problem was not discovered before because if `streamInfo.mqResource` is not set when the stream is created, the manager side will automatically set `streamId` to `streamInfo.mqResource`, and in most cases `streamId` and streamInfo.mqResource` are the same. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@inlong.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [inlong] EMsnap opened a new pull request, #8193: [INLONG-8062][Sort] Add PostgreSQL source connector on flink 1.15
EMsnap opened a new pull request, #8193: URL: https://github.com/apache/inlong/pull/8193 - Fixes #8062 ### Motivation Add PostgreSQL source connector on flink 1.15 ### Modifications *Describe the modifications you've done.* ### Verifying this change Add PostgreSQL source connector on flink 1.15 Please note that the dirty data and the audit is not implemented, these feature will be added after we seperate the flink format from flink1.13 to flink1.15 ### Documentation - Does this pull request introduce a new feature? (yes) - If yes, how is the feature documented? (docs) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@inlong.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [inlong-website] dockerzhang merged pull request #771: [INLONG-770][Doc] Update design and concept extending data node for manager
dockerzhang merged PR #771: URL: https://github.com/apache/inlong-website/pull/771 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@inlong.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [inlong-website] dockerzhang closed issue #770: [Improve][Doc] update design and concept extending data node for manager
dockerzhang closed issue #770: [Improve][Doc] update design and concept extending data node for manager URL: https://github.com/apache/inlong-website/issues/770 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@inlong.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[inlong-website] branch master updated: [INLONG-770][Doc] Update design and concept extending data node for manager (#771)
This is an automated email from the ASF dual-hosted git repository. dockerzhang pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/inlong-website.git The following commit(s) were added to refs/heads/master by this push: new a2e54e369f [INLONG-770][Doc] Update design and concept extending data node for manager (#771) a2e54e369f is described below commit a2e54e369f112b0da57387169c17b0c55992064d Author: chestnufang <65438734+chestnu...@users.noreply.github.com> AuthorDate: Thu Jun 8 19:01:14 2023 +0800 [INLONG-770][Doc] Update design and concept extending data node for manager (#771) Co-authored-by: chestnufang --- docs/design_and_concept/how_to_extend_data_node_for_manager.md| 4 ++-- .../current/design_and_concept/how_to_extend_data_node_for_manager.md | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/design_and_concept/how_to_extend_data_node_for_manager.md b/docs/design_and_concept/how_to_extend_data_node_for_manager.md index 763901fc3e..f821c23451 100644 --- a/docs/design_and_concept/how_to_extend_data_node_for_manager.md +++ b/docs/design_and_concept/how_to_extend_data_node_for_manager.md @@ -16,7 +16,7 @@ This article describes how to extend a new data node through the Manager to prov - Add **SourceType** in `org.apache.inlong.manager.common.consts.SourceType` - Create new package under package path: `org.apache.inlong.manager.common.pojo.source`, develop every entity class needed. - Create Operation class for new data source under package path: `org.apache.inlong.manager.service.source`. -- Transfer data source to **ExtractNode** supported in **Sort**, refer to `org.apache.inlong.manager.pojo.sort.util.ExtractNodeUtils` +- Transfer data source to **ExtractNode** supported in **Sort**, create the implementation class Provider for the `org.apache.inlong.manager.pojo.sort.node.provider.ExtractNodeProvider` interface under the `org.apache.inlong.manager.pojo.sort.node.provider` path, and register it with the `org.apache.inlong.manager.pojo.sort.node.ExtractNodeProviderFactory` ## Extend Load Node @@ -24,4 +24,4 @@ This article describes how to extend a new data node through the Manager to prov - Add **SinkType** in `org.apache.inlong.manager.common.consts.SinkType` - Create new package under package path: `org.apache.inlong.manager.common.pojo.sink`, develop every entity class needed. - Create Operation class for new data source under package path: `org.apache.inlong.manager.service.sink`. -- Transfer data sink to **LoadNode** supported in **Sort**, refer to `org.apache.inlong.manager.pojo.sort.util.LoadNodeUtils` \ No newline at end of file +- Transfer data sink to **LoadNode** supported in **Sort**, create the implementation class Provider for the `org.apache.inlong.manager.pojo.sort.node.provider.LoadNodeProvider` interface under the `org.apache.inlong.manager.pojo.sort.node.provider` path, and register it with the `org.apache.inlong.manager.pojo.sort.node.LoadNodeProviderFactory` \ No newline at end of file diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/design_and_concept/how_to_extend_data_node_for_manager.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/design_and_concept/how_to_extend_data_node_for_manager.md index 7b07d0e935..8e97526d4b 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/design_and_concept/how_to_extend_data_node_for_manager.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/design_and_concept/how_to_extend_data_node_for_manager.md @@ -16,7 +16,7 @@ Inlong 设计初衷即是为了在不同数据源之间创建数据流，截止 - 在常量类`org.apache.inlong.manager.common.consts.SourceType`中同样增加对应常量 - 在`org.apache.inlong.manager.common.pojo.source`路径下创建文件夹，创建对应实体类 - 在`org.apache.inlong.manager.service.source`路径下，创建对应工具类 -- 支持数据源到**ExtractNode**的转换函数，参考 `org.apache.inlong.manager.pojo.sort.util.ExtractNodeUtils` +- 支持数据源到**ExtractNode**的转换函数，在`org.apache.inlong.manager.pojo.sort.node.provider`路径下创建对应实现`org.apache.inlong.manager.pojo.sort.node.provider.ExtractNodeProvider`接口的实体类Provider，并注册到`org.apache.inlong.manager.pojo.sort.node.ExtractNodeProviderFactory` ## 扩展 Load Node @@ -24,4 +24,4 @@ Inlong 设计初衷即是为了在不同数据源之间创建数据流，截止 - 在常量类`org.apache.inlong.manager.common.consts.SinkType`中增加对应常量 - 在`org.apache.inlong.manager.common.pojo.sink`路径下创建文件夹, 创建对应实体类 - 在`org.apache.inlong.manager.service.sink`路径下创建对应工具类 -- 支持数据源到**LoadNode**的转换函数，参考代码 `org.apache.inlong.manager.pojo.sort.util.LoadNodeUtils` \ No newline at end of file +- 支持数据源到**LoadNode**的转换函数，在`org.apache.inlong.manager.pojo.sort.node.provider`路径下创建对应实现`org.apache.inlong.manager.pojo.sort.node.provider.LoadNodeProvider`接口的实体类Provider，并注册到`org.apache.inlong.manager.pojo.sort.node.LoadNodeProviderFactory` \ No newline at end of file
[GitHub] [inlong] gosonzhang merged pull request #8194: [INLONG-8192][DataProxy] The topic name generated by dataproxy is incorrect
gosonzhang merged PR #8194: URL: https://github.com/apache/inlong/pull/8194 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@inlong.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[inlong] branch master updated: [INLONG-8192][DataProxy] The topic name generated by dataproxy is incorrect (#8194)
This is an automated email from the ASF dual-hosted git repository.
gosonzhang pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/inlong.git
The following commit(s) were added to refs/heads/master by this push:
new 6c3d72b0ff [INLONG-8192][DataProxy] The topic name generated by
dataproxy is incorrect (#8194)
6c3d72b0ff is described below
commit 6c3d72b0ffb0064a0147b41b0d774f3570bd6a63
Author: Goson Zhang <4675...@qq.com>
AuthorDate: Thu Jun 8 21:30:54 2023 +0800
[INLONG-8192][DataProxy] The topic name generated by dataproxy is incorrect
(#8194)
---
.../dataproxy/config/holder/MetaConfigHolder.java| 20 ++--
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git
a/inlong-dataproxy/dataproxy-source/src/main/java/org/apache/inlong/dataproxy/config/holder/MetaConfigHolder.java
b/inlong-dataproxy/dataproxy-source/src/main/java/org/apache/inlong/dataproxy/config/holder/MetaConfigHolder.java
index 9c7078ee48..70a07bde2c 100644
---
a/inlong-dataproxy/dataproxy-source/src/main/java/org/apache/inlong/dataproxy/config/holder/MetaConfigHolder.java
+++
b/inlong-dataproxy/dataproxy-source/src/main/java/org/apache/inlong/dataproxy/config/holder/MetaConfigHolder.java
@@ -145,12 +145,9 @@ public class MetaConfigHolder extends ConfigHolder {
}
public boolean updateConfigMap(String inDataMd5, String inDataJsonStr) {
-if (StringUtils.isBlank(inDataMd5) ||
StringUtils.isBlank(inDataJsonStr)) {
-return false;
-}
-if (inDataMd5.equalsIgnoreCase(dataMd5)) {
-LOG.info("Update json {}, but the stored md5sum {} is equals to
changed md5sum {}",
-getFileName(), dataMd5, inDataMd5);
+if (StringUtils.isBlank(inDataMd5)
+|| StringUtils.isBlank(inDataJsonStr)
+|| inDataMd5.equalsIgnoreCase(dataMd5)) {
return false;
}
if (storeConfigToFile(inDataJsonStr)) {
@@ -368,12 +365,15 @@ public class MetaConfigHolder extends ConfigHolder {
}
tenant =
idObject.getParams().getOrDefault(ConfigConstants.KEY_TENANT, "");
nameSpace =
idObject.getParams().getOrDefault(ConfigConstants.KEY_NAMESPACE, "");
+if (StringUtils.isBlank(idObject.getTopic())) {
+// namespace field must exist and value not be empty,
+// otherwise it is an illegal configuration item.
+continue;
+}
if (mqType.equals(CacheType.TUBE)) {
-if (StringUtils.isNotBlank(nameSpace)) {
-topicName = nameSpace;
-}
+topicName = nameSpace;
} else if (mqType.equals(CacheType.KAFKA)) {
-if (StringUtils.isNotBlank(nameSpace)) {
+if (topicName.equals(streamId)) {
topicName =
String.format(Constants.DEFAULT_KAFKA_TOPIC_FORMAT, nameSpace, topicName);
}
}
[GitHub] [inlong] github-actions[bot] commented on issue #8195: no cli example
github-actions[bot] commented on issue #8195: URL: https://github.com/apache/inlong/issues/8195#issuecomment-1582594788 Hello @Madiao, thank you for opening your first issue in InLong 🧡 We will respond as soon as possible ⏳ If this is a bug report, please provide screenshots or error logs for us to reproduce your issue, so we can do our best to fix it. If you have any questions in the meantime, you can also ask us on the [InLong Discussions](https://github.com/apache/inlong/discussions) 🔍 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@inlong.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [inlong] bluewang merged pull request #8191: [INLONG-8190][Dashboard] Change the display name for PostgreSQL's schema
bluewang merged PR #8191: URL: https://github.com/apache/inlong/pull/8191 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@inlong.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[inlong] branch master updated: [INLONG-8190][Dashboard] Change the display name for PostgreSQL's schema (#8191)
This is an automated email from the ASF dual-hosted git repository. lzwang pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/inlong.git The following commit(s) were added to refs/heads/master by this push: new 624ec2e866 [INLONG-8190][Dashboard] Change the display name for PostgreSQL's schema (#8191) 624ec2e866 is described below commit 624ec2e86663f15c600a2ed013213e57014282ea Author: Lizhen <88174078+bluew...@users.noreply.github.com> AuthorDate: Fri Jun 9 10:06:03 2023 +0800 [INLONG-8190][Dashboard] Change the display name for PostgreSQL's schema (#8191) --- inlong-dashboard/src/ui/locales/cn.json | 2 +- inlong-dashboard/src/ui/locales/en.json | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/inlong-dashboard/src/ui/locales/cn.json b/inlong-dashboard/src/ui/locales/cn.json index 05066b71fa..3d98c4c22b 100644 --- a/inlong-dashboard/src/ui/locales/cn.json +++ b/inlong-dashboard/src/ui/locales/cn.json @@ -64,7 +64,7 @@ "meta.Sources.PostgreSQL.Username": "用户", "meta.Sources.PostgreSQL.Password": "密码", "meta.Sources.PostgreSQL.Database": "数据库名", - "meta.Sources.PostgreSQL.SchemaName": "架构名称", + "meta.Sources.PostgreSQL.SchemaName": "模式", "meta.Sources.PostgreSQL.TableName": "表格名称", "meta.Sources.PostgreSQL.TableNameHelp": "支持多个表格名称，以逗号分隔", "meta.Sources.PostgreSQL.decodingPluginName": "解码插件名称", diff --git a/inlong-dashboard/src/ui/locales/en.json b/inlong-dashboard/src/ui/locales/en.json index e53dd76795..b982b5f58e 100644 --- a/inlong-dashboard/src/ui/locales/en.json +++ b/inlong-dashboard/src/ui/locales/en.json @@ -64,7 +64,7 @@ "meta.Sources.PostgreSQL.Username": "Username", "meta.Sources.PostgreSQL.Password": "Password", "meta.Sources.PostgreSQL.Database": "Database", - "meta.Sources.PostgreSQL.SchemaName": "SchemaName", + "meta.Sources.PostgreSQL.SchemaName": "Model", "meta.Sources.PostgreSQL.TableName": "TableName", "meta.Sources.PostgreSQL.TableNameHelp": "Multiple table names are supported, separated by commas", "meta.Sources.PostgreSQL.decodingPluginName": "Decoding Plugin Name",
[GitHub] [inlong] vernedeng opened a new pull request, #8201: [INLONG-8200][Manager] Add tenant permission filter
vernedeng opened a new pull request, #8201: URL: https://github.com/apache/inlong/pull/8201 ### Prepare a Pull Request *(Change the title refer to the following example)* - Title Example: [INLONG-XYZ][Component] Title of the pull request *(The following *XYZ* should be replaced by the actual [GitHub Issue](https://github.com/apache/inlong/issues) number)* - Fixes #8200 - Parent #7914 ### Motivation Fliter out requests which user has no permission to the specific tenant ### Modifications *Describe the modifications you've done.* ### Verifying this change *(Please pick either of the following options)* - [ ] This change is a trivial rework/code cleanup without any test coverage. - [ ] This change is already covered by existing tests, such as: *(please describe tests)* - [ ] This change added tests and can be verified as follows: *(example:)* - *Added integration tests for end-to-end deployment with large payloads (10MB)* - *Extended integration test for recovery after broker failure* ### Documentation - Does this pull request introduce a new feature? (yes / no) - If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented) - If a feature is not applicable for documentation, explain why? - If a feature is not documented yet in this PR, please create a follow-up issue for adding the documentation -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@inlong.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [inlong] chestnut-c opened a new pull request, #8203: [INLONG-8202][Manager] Optimize Provider code to extract public parseFormat class
chestnut-c opened a new pull request, #8203: URL: https://github.com/apache/inlong/pull/8203 [INLONG-8202][Manager] Optimize Provider code to extract public parseFormat class - Fixes #8202 ### Motivation Optimize Provider code to extract public parseFormat class -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@inlong.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
