[jira] [Updated] (FLINK-35309) Enable Notice file ci check and fix Notice
[ https://issues.apache.org/jira/browse/FLINK-35309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhongqiang Gong updated FLINK-35309: Description: Changes: * Add ci to check Notice file * Fix Notice file issue was: Changes: * * Add ci to check Notice file * Fix Notice file issue > Enable Notice file ci check and fix Notice > --- > > Key: FLINK-35309 > URL: https://issues.apache.org/jira/browse/FLINK-35309 > Project: Flink > Issue Type: Improvement > Components: Flink CDC >Affects Versions: 3.1.0 >Reporter: Zhongqiang Gong >Priority: Blocker > > Changes: > * Add ci to check Notice file > * Fix Notice file issue -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FLINK-35309) Enable Notice file ci check and fix Notice
Zhongqiang Gong created FLINK-35309: --- Summary: Enable Notice file ci check and fix Notice Key: FLINK-35309 URL: https://issues.apache.org/jira/browse/FLINK-35309 Project: Flink Issue Type: Improvement Components: Flink CDC Affects Versions: 3.1.0 Reporter: Zhongqiang Gong Changes: * * Add ci to check Notice file * Fix Notice file issue -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (FLINK-35240) Disable FLUSH_AFTER_WRITE_VALUE to avoid flush per record
[ https://issues.apache.org/jira/browse/FLINK-35240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841301#comment-17841301 ] Zhongqiang Gong edited comment on FLINK-35240 at 4/26/24 5:11 PM: -- [~afedulov] [~robyoung] I opened a pr to patch this issue. Would like help me review? Thank you~ :) was (Author: JIRAUSER301076): [~afedulov] I opened a pr to patch this issue. Would like help me review? Thank you~ :) > Disable FLUSH_AFTER_WRITE_VALUE to avoid flush per record > - > > Key: FLINK-35240 > URL: https://issues.apache.org/jira/browse/FLINK-35240 > Project: Flink > Issue Type: Improvement > Components: Connectors / FileSystem >Reporter: Zhongqiang Gong >Priority: Minor > Labels: pull-request-available > Attachments: image-2024-04-26-00-23-29-975.png, > image-2024-04-26-17-16-07-925.png, image-2024-04-26-17-16-20-647.png, > image-2024-04-26-17-16-30-293.png, screenshot-1.png > > > *Reproduce：* > * According to user email: > https://lists.apache.org/thread/9j5z8hv4vjkd54dkzqy1ryyvm0l5rxhc > * !image-2024-04-26-00-23-29-975.png! > *Analysis：* > * `org.apache.flink.formats.csv.CsvBulkWriter#addElement` will flush per > record. > *Solution：* > * I think maybe we can disable `FLUSH_AFTER_WRITE_VALUE` to avoid flush when > a record added. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-35240) Disable FLUSH_AFTER_WRITE_VALUE to avoid flush per record
[ https://issues.apache.org/jira/browse/FLINK-35240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841301#comment-17841301 ] Zhongqiang Gong commented on FLINK-35240: - [~afedulov] I opened a pr to patch this issue. Would like help me review? Thank you~ :) > Disable FLUSH_AFTER_WRITE_VALUE to avoid flush per record > - > > Key: FLINK-35240 > URL: https://issues.apache.org/jira/browse/FLINK-35240 > Project: Flink > Issue Type: Improvement > Components: Connectors / FileSystem >Reporter: Zhongqiang Gong >Priority: Minor > Labels: pull-request-available > Attachments: image-2024-04-26-00-23-29-975.png, > image-2024-04-26-17-16-07-925.png, image-2024-04-26-17-16-20-647.png, > image-2024-04-26-17-16-30-293.png, screenshot-1.png > > > *Reproduce：* > * According to user email: > https://lists.apache.org/thread/9j5z8hv4vjkd54dkzqy1ryyvm0l5rxhc > * !image-2024-04-26-00-23-29-975.png! > *Analysis：* > * `org.apache.flink.formats.csv.CsvBulkWriter#addElement` will flush per > record. > *Solution：* > * I think maybe we can disable `FLUSH_AFTER_WRITE_VALUE` to avoid flush when > a record added. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (FLINK-35240) Disable FLUSH_AFTER_WRITE_VALUE to avoid flush per record
[ https://issues.apache.org/jira/browse/FLINK-35240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841232#comment-17841232 ] Zhongqiang Gong edited comment on FLINK-35240 at 4/26/24 1:34 PM: -- !screenshot-1.png! [~afedulov] The close methed always be invorked, in close methed will read *AUTO_CLOSE_TARGET* to determine whether to close or not . was (Author: JIRAUSER301076): !screenshot-1.png! The close methed always be invorked, in close methed will read *AUTO_CLOSE_TARGET* to determine whether to close or not . > Disable FLUSH_AFTER_WRITE_VALUE to avoid flush per record > - > > Key: FLINK-35240 > URL: https://issues.apache.org/jira/browse/FLINK-35240 > Project: Flink > Issue Type: Improvement > Components: Connectors / FileSystem >Reporter: Zhongqiang Gong >Priority: Minor > Attachments: image-2024-04-26-00-23-29-975.png, screenshot-1.png > > > *Reproduce：* > * According to user email: > https://lists.apache.org/thread/9j5z8hv4vjkd54dkzqy1ryyvm0l5rxhc > * !image-2024-04-26-00-23-29-975.png! > *Analysis：* > * `org.apache.flink.formats.csv.CsvBulkWriter#addElement` will flush per > record. > *Solution：* > * I think maybe we can disable `FLUSH_AFTER_WRITE_VALUE` to avoid flush when > a record added. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-35240) Disable FLUSH_AFTER_WRITE_VALUE to avoid flush per record
[ https://issues.apache.org/jira/browse/FLINK-35240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841238#comment-17841238 ] Zhongqiang Gong commented on FLINK-35240: - Base on the logic of _writer. close，We can disable FLUSH_PASSED_TO_STREAM too. So we can control flush in CsvBulkWriter. > Disable FLUSH_AFTER_WRITE_VALUE to avoid flush per record > - > > Key: FLINK-35240 > URL: https://issues.apache.org/jira/browse/FLINK-35240 > Project: Flink > Issue Type: Improvement > Components: Connectors / FileSystem >Reporter: Zhongqiang Gong >Priority: Minor > Attachments: image-2024-04-26-00-23-29-975.png, screenshot-1.png > > > *Reproduce：* > * According to user email: > https://lists.apache.org/thread/9j5z8hv4vjkd54dkzqy1ryyvm0l5rxhc > * !image-2024-04-26-00-23-29-975.png! > *Analysis：* > * `org.apache.flink.formats.csv.CsvBulkWriter#addElement` will flush per > record. > *Solution：* > * I think maybe we can disable `FLUSH_AFTER_WRITE_VALUE` to avoid flush when > a record added. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-35240) Disable FLUSH_AFTER_WRITE_VALUE to avoid flush per record
[ https://issues.apache.org/jira/browse/FLINK-35240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841232#comment-17841232 ] Zhongqiang Gong commented on FLINK-35240: - !截图-1.png! The close methed always be invorked, in close methed will read *AUTO_CLOSE_TARGET* to determine whether to close or not . > Disable FLUSH_AFTER_WRITE_VALUE to avoid flush per record > - > > Key: FLINK-35240 > URL: https://issues.apache.org/jira/browse/FLINK-35240 > Project: Flink > Issue Type: Improvement > Components: Connectors / FileSystem >Reporter: Zhongqiang Gong >Priority: Minor > Attachments: image-2024-04-26-00-23-29-975.png, screenshot-1.png > > > *Reproduce：* > * According to user email: > https://lists.apache.org/thread/9j5z8hv4vjkd54dkzqy1ryyvm0l5rxhc > * !image-2024-04-26-00-23-29-975.png! > *Analysis：* > * `org.apache.flink.formats.csv.CsvBulkWriter#addElement` will flush per > record. > *Solution：* > * I think maybe we can disable `FLUSH_AFTER_WRITE_VALUE` to avoid flush when > a record added. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (FLINK-35240) Disable FLUSH_AFTER_WRITE_VALUE to avoid flush per record
[ https://issues.apache.org/jira/browse/FLINK-35240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841232#comment-17841232 ] Zhongqiang Gong edited comment on FLINK-35240 at 4/26/24 1:22 PM: -- !screenshot-1.png! The close methed always be invorked, in close methed will read *AUTO_CLOSE_TARGET* to determine whether to close or not . was (Author: JIRAUSER301076): !截图-1.png! The close methed always be invorked, in close methed will read *AUTO_CLOSE_TARGET* to determine whether to close or not . > Disable FLUSH_AFTER_WRITE_VALUE to avoid flush per record > - > > Key: FLINK-35240 > URL: https://issues.apache.org/jira/browse/FLINK-35240 > Project: Flink > Issue Type: Improvement > Components: Connectors / FileSystem >Reporter: Zhongqiang Gong >Priority: Minor > Attachments: image-2024-04-26-00-23-29-975.png, screenshot-1.png > > > *Reproduce：* > * According to user email: > https://lists.apache.org/thread/9j5z8hv4vjkd54dkzqy1ryyvm0l5rxhc > * !image-2024-04-26-00-23-29-975.png! > *Analysis：* > * `org.apache.flink.formats.csv.CsvBulkWriter#addElement` will flush per > record. > *Solution：* > * I think maybe we can disable `FLUSH_AFTER_WRITE_VALUE` to avoid flush when > a record added. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-35240) Disable FLUSH_AFTER_WRITE_VALUE to avoid flush per record
[ https://issues.apache.org/jira/browse/FLINK-35240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841063#comment-17841063 ] Zhongqiang Gong commented on FLINK-35240: - Welcome [~robyoung] to join this disscussion. And you understand what i want to express. [~afedulov] [~robyoung] I had try to solove this issue on my local. https://github.com/GOODBOY008/flink/commit/4f78be92b5bdebcf92a1e32736434517ccc6f561 > Disable FLUSH_AFTER_WRITE_VALUE to avoid flush per record > - > > Key: FLINK-35240 > URL: https://issues.apache.org/jira/browse/FLINK-35240 > Project: Flink > Issue Type: Improvement > Components: Connectors / FileSystem >Reporter: Zhongqiang Gong >Priority: Minor > Attachments: image-2024-04-26-00-23-29-975.png, screenshot-1.png > > > *Reproduce：* > * According to user email: > https://lists.apache.org/thread/9j5z8hv4vjkd54dkzqy1ryyvm0l5rxhc > * !image-2024-04-26-00-23-29-975.png! > *Analysis：* > * `org.apache.flink.formats.csv.CsvBulkWriter#addElement` will flush per > record. > *Solution：* > * I think maybe we can disable `FLUSH_AFTER_WRITE_VALUE` to avoid flush when > a record added. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-35240) Disable FLUSH_AFTER_WRITE_VALUE to avoid flush per record
[ https://issues.apache.org/jira/browse/FLINK-35240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhongqiang Gong updated FLINK-35240: Attachment: screenshot-1.png > Disable FLUSH_AFTER_WRITE_VALUE to avoid flush per record > - > > Key: FLINK-35240 > URL: https://issues.apache.org/jira/browse/FLINK-35240 > Project: Flink > Issue Type: Improvement > Components: Connectors / FileSystem >Reporter: Zhongqiang Gong >Priority: Minor > Attachments: image-2024-04-26-00-23-29-975.png, screenshot-1.png > > > *Reproduce：* > * According to user email: > https://lists.apache.org/thread/9j5z8hv4vjkd54dkzqy1ryyvm0l5rxhc > * !image-2024-04-26-00-23-29-975.png! > *Analysis：* > * `org.apache.flink.formats.csv.CsvBulkWriter#addElement` will flush per > record. > *Solution：* > * I think maybe we can disable `FLUSH_AFTER_WRITE_VALUE` to avoid flush when > a record added. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-35240) Disable FLUSH_AFTER_WRITE_VALUE to avoid flush per record
[ https://issues.apache.org/jira/browse/FLINK-35240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhongqiang Gong updated FLINK-35240: Description: *Reproduce：* * According to user email: https://lists.apache.org/thread/9j5z8hv4vjkd54dkzqy1ryyvm0l5rxhc * !image-2024-04-26-00-23-29-975.png! *Analysis：* * `org.apache.flink.formats.csv.CsvBulkWriter#addElement` will flush per record. *Solution：* * I think maybe we can disable `FLUSH_AFTER_WRITE_VALUE` to avoid flush when a record added. was: *Reproduce：* * According to user email: https://lists.apache.org/thread/9j5z8hv4vjkd54dkzqy1ryyvm0l5rxhc * !image-2024-04-26-00-23-29-975.png! *Analysis：* * `org.apache.flink.formats.csv.CsvBulkWriter#addElement` will flush per record. *Solution：* ** I think maybe we can disable `FLUSH_AFTER_WRITE_VALUE` to avoid flush when a record added. > Disable FLUSH_AFTER_WRITE_VALUE to avoid flush per record > - > > Key: FLINK-35240 > URL: https://issues.apache.org/jira/browse/FLINK-35240 > Project: Flink > Issue Type: Improvement > Components: Connectors / FileSystem >Reporter: Zhongqiang Gong >Priority: Minor > Attachments: image-2024-04-26-00-23-29-975.png > > > *Reproduce：* > * According to user email: > https://lists.apache.org/thread/9j5z8hv4vjkd54dkzqy1ryyvm0l5rxhc > * !image-2024-04-26-00-23-29-975.png! > *Analysis：* > * `org.apache.flink.formats.csv.CsvBulkWriter#addElement` will flush per > record. > *Solution：* > * I think maybe we can disable `FLUSH_AFTER_WRITE_VALUE` to avoid flush when > a record added. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-35240) Disable FLUSH_AFTER_WRITE_VALUE to avoid flush per record
[ https://issues.apache.org/jira/browse/FLINK-35240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhongqiang Gong updated FLINK-35240: Description: *Reproduce：* * According to user email: https://lists.apache.org/thread/9j5z8hv4vjkd54dkzqy1ryyvm0l5rxhc * !image-2024-04-26-00-23-29-975.png! *Analysis：* * `org.apache.flink.formats.csv.CsvBulkWriter#addElement` will flush per record. *Solution：* ** I think maybe we can disable `FLUSH_AFTER_WRITE_VALUE` to avoid flush when a record added. was: *Reproduce：* * According to user email: https://lists.apache.org/thread/9j5z8hv4vjkd54dkzqy1ryyvm0l5rxhc * !image-2024-04-26-00-23-29-975.png! *Analysis：* * `org.apache.flink.formats.csv.CsvBulkWriter#addElement` will flush per record. * *Solution：* ** I think maybe we can disable `FLUSH_AFTER_WRITE_VALUE` to avoid flush when a record added. > Disable FLUSH_AFTER_WRITE_VALUE to avoid flush per record > - > > Key: FLINK-35240 > URL: https://issues.apache.org/jira/browse/FLINK-35240 > Project: Flink > Issue Type: Improvement > Components: Connectors / FileSystem >Reporter: Zhongqiang Gong >Priority: Minor > Attachments: image-2024-04-26-00-23-29-975.png > > > *Reproduce：* > * According to user email: > https://lists.apache.org/thread/9j5z8hv4vjkd54dkzqy1ryyvm0l5rxhc > * !image-2024-04-26-00-23-29-975.png! > *Analysis：* > * `org.apache.flink.formats.csv.CsvBulkWriter#addElement` will flush per > record. > *Solution：* > ** I think maybe we can disable `FLUSH_AFTER_WRITE_VALUE` to avoid flush when > a record added. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-35240) Disable FLUSH_AFTER_WRITE_VALUE to avoid flush per record
[ https://issues.apache.org/jira/browse/FLINK-35240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhongqiang Gong updated FLINK-35240: Description: *Reproduce：* * According to user email: https://lists.apache.org/thread/9j5z8hv4vjkd54dkzqy1ryyvm0l5rxhc * !image-2024-04-26-00-23-29-975.png! *Analysis：* * `org.apache.flink.formats.csv.CsvBulkWriter#addElement` will flush per record. * *Solution：* ** I think maybe we can disable `FLUSH_AFTER_WRITE_VALUE` to avoid flush when a record added. was: According to user email: https://lists.apache.org/thread/9j5z8hv4vjkd54dkzqy1ryyvm0l5rxhc !image-2024-04-26-00-23-29-975.png! I found `org.apache.flink.formats.csv.CsvBulkWriter#addElement` will flush per record. I think maybe we can disable `FLUSH_AFTER_WRITE_VALUE` to avoid flush when a record added. > Disable FLUSH_AFTER_WRITE_VALUE to avoid flush per record > - > > Key: FLINK-35240 > URL: https://issues.apache.org/jira/browse/FLINK-35240 > Project: Flink > Issue Type: Improvement > Components: Connectors / FileSystem >Reporter: Zhongqiang Gong >Priority: Minor > Attachments: image-2024-04-26-00-23-29-975.png > > > *Reproduce：* > * According to user email: > https://lists.apache.org/thread/9j5z8hv4vjkd54dkzqy1ryyvm0l5rxhc > * !image-2024-04-26-00-23-29-975.png! > *Analysis：* > * `org.apache.flink.formats.csv.CsvBulkWriter#addElement` will flush per > record. > * > *Solution：* > ** I think maybe we can disable `FLUSH_AFTER_WRITE_VALUE` to avoid flush when > a record added. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-35240) Disable FLUSH_AFTER_WRITE_VALUE to avoid flush per record
[ https://issues.apache.org/jira/browse/FLINK-35240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17840869#comment-17840869 ] Zhongqiang Gong commented on FLINK-35240: - [~afedulov] Can you give some suggestion? Solution: Disable `_FLUSH_AFTER_WRITE_VALUE_` to avoid flush per record added. > Disable FLUSH_AFTER_WRITE_VALUE to avoid flush per record > - > > Key: FLINK-35240 > URL: https://issues.apache.org/jira/browse/FLINK-35240 > Project: Flink > Issue Type: Improvement > Components: Connectors / FileSystem >Reporter: Zhongqiang Gong >Priority: Minor > Attachments: image-2024-04-26-00-23-29-975.png > > > According to user email: > https://lists.apache.org/thread/9j5z8hv4vjkd54dkzqy1ryyvm0l5rxhc > !image-2024-04-26-00-23-29-975.png! > I found `org.apache.flink.formats.csv.CsvBulkWriter#addElement` will flush > per record. > I think maybe we can disable `FLUSH_AFTER_WRITE_VALUE` to avoid flush when a > record added. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FLINK-35240) Disable FLUSH_AFTER_WRITE_VALUE to avoid flush per record
Zhongqiang Gong created FLINK-35240: --- Summary: Disable FLUSH_AFTER_WRITE_VALUE to avoid flush per record Key: FLINK-35240 URL: https://issues.apache.org/jira/browse/FLINK-35240 Project: Flink Issue Type: Improvement Components: Connectors / FileSystem Reporter: Zhongqiang Gong Attachments: image-2024-04-26-00-23-29-975.png According to user email: https://lists.apache.org/thread/9j5z8hv4vjkd54dkzqy1ryyvm0l5rxhc !image-2024-04-26-00-23-29-975.png! I found `org.apache.flink.formats.csv.CsvBulkWriter#addElement` will flush per record. I think maybe we can disable `FLUSH_AFTER_WRITE_VALUE` to avoid flush when a record added. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FLINK-35182) Bump org.apache.commons:commons-compress from 1.24.0 to 1.26.1 for Flink Pulsar connector
Zhongqiang Gong created FLINK-35182: --- Summary: Bump org.apache.commons:commons-compress from 1.24.0 to 1.26.1 for Flink Pulsar connector Key: FLINK-35182 URL: https://issues.apache.org/jira/browse/FLINK-35182 Project: Flink Issue Type: Technical Debt Components: Connectors / Pulsar Reporter: Zhongqiang Gong -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (FLINK-35181) Bump org.apache.commons:commons-compress from 1.24.0 to 1.26.1 for Flink Elasticsearch connector
[ https://issues.apache.org/jira/browse/FLINK-35181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhongqiang Gong closed FLINK-35181. --- Resolution: Fixed > Bump org.apache.commons:commons-compress from 1.24.0 to 1.26.1 for Flink > Elasticsearch connector > > > Key: FLINK-35181 > URL: https://issues.apache.org/jira/browse/FLINK-35181 > Project: Flink > Issue Type: Technical Debt > Components: Connectors / ElasticSearch >Reporter: Zhongqiang Gong >Assignee: Danny Cranmer >Priority: Major > > Bump org.apache.commons:commons-compress from 1.24.0 to 1.26.1 for Flink > Elasticsearch connector > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-35181) Bump org.apache.commons:commons-compress from 1.24.0 to 1.26.1 for Flink Elasticsearch connector
[ https://issues.apache.org/jira/browse/FLINK-35181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhongqiang Gong updated FLINK-35181: Summary: Bump org.apache.commons:commons-compress from 1.24.0 to 1.26.1 for Flink Elasticsearch connector (was: CLONE - Bump org.apache.commons:commons-compress from 1.24.0 to 1.26.1 for Flink Elasticsearch connector) > Bump org.apache.commons:commons-compress from 1.24.0 to 1.26.1 for Flink > Elasticsearch connector > > > Key: FLINK-35181 > URL: https://issues.apache.org/jira/browse/FLINK-35181 > Project: Flink > Issue Type: Technical Debt > Components: Connectors / ElasticSearch >Reporter: Zhongqiang Gong >Assignee: Danny Cranmer >Priority: Major > > Bump org.apache.commons:commons-compress from 1.24.0 to 1.26.1 for Flink > Elasticsearch connector > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-35181) CLONE - Bump org.apache.commons:commons-compress from 1.24.0 to 1.26.1 for Flink Elasticsearch connector
[ https://issues.apache.org/jira/browse/FLINK-35181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhongqiang Gong updated FLINK-35181: Fix Version/s: (was: rabbitmq-3.1.0) > CLONE - Bump org.apache.commons:commons-compress from 1.24.0 to 1.26.1 for > Flink Elasticsearch connector > > > Key: FLINK-35181 > URL: https://issues.apache.org/jira/browse/FLINK-35181 > Project: Flink > Issue Type: Technical Debt > Components: Connectors/ RabbitMQ >Reporter: Zhongqiang Gong >Assignee: Danny Cranmer >Priority: Major > Labels: pull-request-available > > Bump org.apache.commons:commons-compress from 1.24.0 to 1.26.1 for Flink > RabbitMQ connector > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-35181) CLONE - Bump org.apache.commons:commons-compress from 1.24.0 to 1.26.1 for Flink Elasticsearch connector
[ https://issues.apache.org/jira/browse/FLINK-35181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhongqiang Gong updated FLINK-35181: Labels: (was: pull-request-available) > CLONE - Bump org.apache.commons:commons-compress from 1.24.0 to 1.26.1 for > Flink Elasticsearch connector > > > Key: FLINK-35181 > URL: https://issues.apache.org/jira/browse/FLINK-35181 > Project: Flink > Issue Type: Technical Debt > Components: Connectors / ElasticSearch >Reporter: Zhongqiang Gong >Assignee: Danny Cranmer >Priority: Major > > Bump org.apache.commons:commons-compress from 1.24.0 to 1.26.1 for Flink > RabbitMQ connector > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-35181) CLONE - Bump org.apache.commons:commons-compress from 1.24.0 to 1.26.1 for Flink Elasticsearch connector
[ https://issues.apache.org/jira/browse/FLINK-35181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhongqiang Gong updated FLINK-35181: Description: Bump org.apache.commons:commons-compress from 1.24.0 to 1.26.1 for Flink Elasticsearch connector was: Bump org.apache.commons:commons-compress from 1.24.0 to 1.26.1 for Flink RabbitMQ connector > CLONE - Bump org.apache.commons:commons-compress from 1.24.0 to 1.26.1 for > Flink Elasticsearch connector > > > Key: FLINK-35181 > URL: https://issues.apache.org/jira/browse/FLINK-35181 > Project: Flink > Issue Type: Technical Debt > Components: Connectors / ElasticSearch >Reporter: Zhongqiang Gong >Assignee: Danny Cranmer >Priority: Major > > Bump org.apache.commons:commons-compress from 1.24.0 to 1.26.1 for Flink > Elasticsearch connector > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-35181) CLONE - Bump org.apache.commons:commons-compress from 1.24.0 to 1.26.1 for Flink Elasticsearch connector
[ https://issues.apache.org/jira/browse/FLINK-35181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhongqiang Gong updated FLINK-35181: Component/s: Connectors / ElasticSearch (was: Connectors/ RabbitMQ) > CLONE - Bump org.apache.commons:commons-compress from 1.24.0 to 1.26.1 for > Flink Elasticsearch connector > > > Key: FLINK-35181 > URL: https://issues.apache.org/jira/browse/FLINK-35181 > Project: Flink > Issue Type: Technical Debt > Components: Connectors / ElasticSearch >Reporter: Zhongqiang Gong >Assignee: Danny Cranmer >Priority: Major > Labels: pull-request-available > > Bump org.apache.commons:commons-compress from 1.24.0 to 1.26.1 for Flink > RabbitMQ connector > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FLINK-35181) CLONE - Bump org.apache.commons:commons-compress from 1.24.0 to 1.26.1 for Flink Elasticsearch connector
Zhongqiang Gong created FLINK-35181: --- Summary: CLONE - Bump org.apache.commons:commons-compress from 1.24.0 to 1.26.1 for Flink Elasticsearch connector Key: FLINK-35181 URL: https://issues.apache.org/jira/browse/FLINK-35181 Project: Flink Issue Type: Technical Debt Components: Connectors/ RabbitMQ Reporter: Zhongqiang Gong Assignee: Danny Cranmer Fix For: rabbitmq-3.1.0 Bump org.apache.commons:commons-compress from 1.24.0 to 1.26.1 for Flink RabbitMQ connector -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (FLINK-34953) Add github ci for flink-web to auto commit build files
[ https://issues.apache.org/jira/browse/FLINK-34953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836459#comment-17836459 ] Zhongqiang Gong edited comment on FLINK-34953 at 4/12/24 8:10 AM: -- Hi [~mapohl][~martijnvisser] , PR is ready, But the flink-web repo's ci is not enabled. Myabe open a ticket to *Infra* team? was (Author: JIRAUSER301076): Hi [~mapohl][~martijnvisser] , PR is ready, But flink-web'ci is not enabled. Myabe open a ticket to *Infra* team? > Add github ci for flink-web to auto commit build files > -- > > Key: FLINK-34953 > URL: https://issues.apache.org/jira/browse/FLINK-34953 > Project: Flink > Issue Type: Improvement > Components: Project Website >Reporter: Zhongqiang Gong >Priority: Minor > Labels: pull-request-available, website > > Currently, https://github.com/apache/flink-web commit build files by local > build. So I want use github ci to build docs and commit. > > Changes: > * Add website build check for pr > * Auto build and commit build files after pr was merged to `asf-site` > * Optinal: this ci can triggered by manual -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-34953) Add github ci for flink-web to auto commit build files
[ https://issues.apache.org/jira/browse/FLINK-34953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836459#comment-17836459 ] Zhongqiang Gong commented on FLINK-34953: - Hi [~mapohl][~martijnvisser] , PR is ready, But flink-web'ci is not enabled. Myabe open a ticket to *Infra* team? > Add github ci for flink-web to auto commit build files > -- > > Key: FLINK-34953 > URL: https://issues.apache.org/jira/browse/FLINK-34953 > Project: Flink > Issue Type: Improvement > Components: Project Website >Reporter: Zhongqiang Gong >Priority: Minor > Labels: pull-request-available, website > > Currently, https://github.com/apache/flink-web commit build files by local > build. So I want use github ci to build docs and commit. > > Changes: > * Add website build check for pr > * Auto build and commit build files after pr was merged to `asf-site` > * Optinal: this ci can triggered by manual -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-34955) Upgrade commons-compress to 1.26.0
[
https://issues.apache.org/jira/browse/FLINK-34955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17834750#comment-17834750
]
Zhongqiang Gong commented on FLINK-34955:
-
Hi [~slfan1989] ,I apologize for the ambiguity. `{color:#c1c7d0}remove
commons-codec dependence{color}` means `{color:#c1c7d0}we don't have to
manually add a dependency to commons-codec.{color}` .
> Upgrade commons-compress to 1.26.0
> --
>
> Key: FLINK-34955
> URL: https://issues.apache.org/jira/browse/FLINK-34955
> Project: Flink
> Issue Type: Improvement
>Reporter: Shilun Fan
>Assignee: Shilun Fan
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.18.2, 1.20.0, 1.19.1
>
>
> commons-compress 1.24.0 has CVE issues, try to upgrade to 1.26.0, we can
> refer to the maven link
> https://mvnrepository.com/artifact/org.apache.commons/commons-compress
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (FLINK-34955) Upgrade commons-compress to 1.26.0
[ https://issues.apache.org/jira/browse/FLINK-34955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17834678#comment-17834678 ] Zhongqiang Gong commented on FLINK-34955: - [~slfan1989] [~mbalassi] According to https://issues.apache.org/jira/browse/COMPRESS-659 , [~jiabaosun] and I think it's better bump version to 1.26.1 and remove `commons-codec` dependence. > Upgrade commons-compress to 1.26.0 > -- > > Key: FLINK-34955 > URL: https://issues.apache.org/jira/browse/FLINK-34955 > Project: Flink > Issue Type: Improvement >Reporter: Shilun Fan >Assignee: Shilun Fan >Priority: Major > Labels: pull-request-available > Fix For: 1.18.2, 1.20.0, 1.19.1 > > > commons-compress 1.24.0 has CVE issues, try to upgrade to 1.26.0, we can > refer to the maven link > https://mvnrepository.com/artifact/org.apache.commons/commons-compress -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-35010) Bump org.apache.commons:commons-compress from 1.24.0 to 1.26.0 for Flink Mongodb connector
[ https://issues.apache.org/jira/browse/FLINK-35010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17834610#comment-17834610 ] Zhongqiang Gong commented on FLINK-35010: - +1 , It's better to bump commons-compress version to 1.26.1. > Bump org.apache.commons:commons-compress from 1.24.0 to 1.26.0 for Flink > Mongodb connector > -- > > Key: FLINK-35010 > URL: https://issues.apache.org/jira/browse/FLINK-35010 > Project: Flink > Issue Type: Technical Debt > Components: Connectors / MongoDB >Reporter: Zhongqiang Gong >Assignee: Zhongqiang Gong >Priority: Minor > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-35010) Bump org.apache.commons:commons-compress from 1.24.0 to 1.26.0 for Flink Mongodb connector
[ https://issues.apache.org/jira/browse/FLINK-35010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhongqiang Gong updated FLINK-35010: Summary: Bump org.apache.commons:commons-compress from 1.24.0 to 1.26.0 for Flink Mongodb connector (was: Bump org.apache.commons:commons-compress from 1.25.0 to 1.26.0 for Flink Mongodb connector) > Bump org.apache.commons:commons-compress from 1.24.0 to 1.26.0 for Flink > Mongodb connector > -- > > Key: FLINK-35010 > URL: https://issues.apache.org/jira/browse/FLINK-35010 > Project: Flink > Issue Type: Technical Debt > Components: Connectors / MongoDB >Reporter: Zhongqiang Gong >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-35010) Bump org.apache.commons:commons-compress from 1.25.0 to 1.26.0 for Flink Mongodb connector
[ https://issues.apache.org/jira/browse/FLINK-35010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17833935#comment-17833935 ] Zhongqiang Gong commented on FLINK-35010: - [~Leonard] I'm willing to take this issue. > Bump org.apache.commons:commons-compress from 1.25.0 to 1.26.0 for Flink > Mongodb connector > -- > > Key: FLINK-35010 > URL: https://issues.apache.org/jira/browse/FLINK-35010 > Project: Flink > Issue Type: Technical Debt > Components: Connectors / MongoDB >Reporter: Zhongqiang Gong >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FLINK-35010) Bump org.apache.commons:commons-compress from 1.25.0 to 1.26.0 for Flink Mongodb connector
Zhongqiang Gong created FLINK-35010: --- Summary: Bump org.apache.commons:commons-compress from 1.25.0 to 1.26.0 for Flink Mongodb connector Key: FLINK-35010 URL: https://issues.apache.org/jira/browse/FLINK-35010 Project: Flink Issue Type: Technical Debt Components: Connectors / MongoDB Reporter: Zhongqiang Gong -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-34953) Add github ci for flink-web to auto commit build files
[ https://issues.apache.org/jira/browse/FLINK-34953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832019#comment-17832019 ] Zhongqiang Gong commented on FLINK-34953: - [~mapohl] [~martijnvisser] Could we reach a consensus on this matter? Or let's start a discussion in community. > Add github ci for flink-web to auto commit build files > -- > > Key: FLINK-34953 > URL: https://issues.apache.org/jira/browse/FLINK-34953 > Project: Flink > Issue Type: Improvement > Components: Project Website >Reporter: Zhongqiang Gong >Priority: Minor > Labels: website > > Currently, https://github.com/apache/flink-web commit build files by local > build. So I want use github ci to build docs and commit. > > Changes: > * Add website build check for pr > * Auto build and commit build files after pr was merged to `asf-site` > * Optinal: this ci can triggered by manual -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (FLINK-34953) Add github ci for flink-web to auto commit build files
[ https://issues.apache.org/jira/browse/FLINK-34953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17831682#comment-17831682 ] Zhongqiang Gong edited comment on FLINK-34953 at 3/28/24 9:30 AM: -- I have a stupid question：Can we build website by ci and use Rsync Deployments Action to sync website content instead of maintain in repo, just like flink document website? was (Author: JIRAUSER301076): I have a stupid question：Can we use Rsync Deployments Action to sync website content instead of maintain in repo, just like flink document website? > Add github ci for flink-web to auto commit build files > -- > > Key: FLINK-34953 > URL: https://issues.apache.org/jira/browse/FLINK-34953 > Project: Flink > Issue Type: Improvement > Components: Project Website >Reporter: Zhongqiang Gong >Priority: Minor > Labels: website > > Currently, https://github.com/apache/flink-web commit build files by local > build. So I want use github ci to build docs and commit. > > Changes: > * Add website build check for pr > * Auto build and commit build files after pr was merged to `asf-site` > * Optinal: this ci can triggered by manual -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-34953) Add github ci for flink-web to auto commit build files
[ https://issues.apache.org/jira/browse/FLINK-34953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17831682#comment-17831682 ] Zhongqiang Gong commented on FLINK-34953: - I have a stupid question：Can we use Rsync Deployments Action to sync website content instead of maintain in repo, just like flink document website? > Add github ci for flink-web to auto commit build files > -- > > Key: FLINK-34953 > URL: https://issues.apache.org/jira/browse/FLINK-34953 > Project: Flink > Issue Type: Improvement > Components: Project Website >Reporter: Zhongqiang Gong >Priority: Minor > Labels: website > > Currently, https://github.com/apache/flink-web commit build files by local > build. So I want use github ci to build docs and commit. > > Changes: > * Add website build check for pr > * Auto build and commit build files after pr was merged to `asf-site` > * Optinal: this ci can triggered by manual -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-34958) Add support Flink 1.20-SNAPSHOT and bump flink-connector-parent to 1.1.0 for mongodb connector
[ https://issues.apache.org/jira/browse/FLINK-34958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17831632#comment-17831632 ] Zhongqiang Gong commented on FLINK-34958: - [~Leonard] I'm willing to take this. > Add support Flink 1.20-SNAPSHOT and bump flink-connector-parent to 1.1.0 for > mongodb connector > -- > > Key: FLINK-34958 > URL: https://issues.apache.org/jira/browse/FLINK-34958 > Project: Flink > Issue Type: Improvement > Components: Connectors / MongoDB >Reporter: Zhongqiang Gong >Priority: Minor > > Changes: > * Add support Flink 1.20-SNAPSHOT > * Bump flink-connector-parent to 1.1.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FLINK-34958) Add support Flink 1.20-SNAPSHOT and bump flink-connector-parent to 1.1.0 for mongodb connector
Zhongqiang Gong created FLINK-34958: --- Summary: Add support Flink 1.20-SNAPSHOT and bump flink-connector-parent to 1.1.0 for mongodb connector Key: FLINK-34958 URL: https://issues.apache.org/jira/browse/FLINK-34958 Project: Flink Issue Type: Improvement Components: Connectors / MongoDB Reporter: Zhongqiang Gong Changes: * Add support Flink 1.20-SNAPSHOT * Bump flink-connector-parent to 1.1.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (FLINK-34943) Support Flink 1.19, 1.20-SNAPSHOT for JDBC connector
[ https://issues.apache.org/jira/browse/FLINK-34943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhongqiang Gong closed FLINK-34943. --- Resolution: Fixed Fixed by https://github.com/apache/flink-connector-jdbc/pull/107 > Support Flink 1.19, 1.20-SNAPSHOT for JDBC connector > > > Key: FLINK-34943 > URL: https://issues.apache.org/jira/browse/FLINK-34943 > Project: Flink > Issue Type: Improvement > Components: Connectors / JDBC >Reporter: Zhongqiang Gong >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-34953) Add github ci for flink-web to auto commit build files
[ https://issues.apache.org/jira/browse/FLINK-34953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17831367#comment-17831367 ] Zhongqiang Gong commented on FLINK-34953: - [~martijnvisser] Thanks for your patience in explaining. > Add github ci for flink-web to auto commit build files > -- > > Key: FLINK-34953 > URL: https://issues.apache.org/jira/browse/FLINK-34953 > Project: Flink > Issue Type: Improvement > Components: Project Website >Reporter: Zhongqiang Gong >Priority: Minor > Labels: website > > Currently, https://github.com/apache/flink-web commit build files by local > build. So I want use github ci to build docs and commit. > > Changes: > * Add website build check for pr > * Auto build and commit build files after pr was merged to `asf-site` > * Optinal: this ci can triggered by manual -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-34953) Add github ci for flink-web to auto commit build files
[ https://issues.apache.org/jira/browse/FLINK-34953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhongqiang Gong updated FLINK-34953: Labels: website (was: ) > Add github ci for flink-web to auto commit build files > -- > > Key: FLINK-34953 > URL: https://issues.apache.org/jira/browse/FLINK-34953 > Project: Flink > Issue Type: Improvement > Components: Project Website >Reporter: Zhongqiang Gong >Priority: Minor > Labels: website > > Currently, https://github.com/apache/flink-web commit build files by local > build. So I want use github ci to build docs and commit. > > Changes: > * Add website build check for pr > * Auto build and commit build files after pr was merged to `asf-site` > * Optinal: this ci can triggered by manual -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-34953) Add github ci for flink-web to auto commit build files
[ https://issues.apache.org/jira/browse/FLINK-34953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17831328#comment-17831328 ] Zhongqiang Gong commented on FLINK-34953: - [~martijnvisser] Can you give me some suggestion? I'm looking forward to hear from you. Thank you! > Add github ci for flink-web to auto commit build files > -- > > Key: FLINK-34953 > URL: https://issues.apache.org/jira/browse/FLINK-34953 > Project: Flink > Issue Type: Improvement > Components: Project Website >Reporter: Zhongqiang Gong >Priority: Minor > > Currently, https://github.com/apache/flink-web commit build files by local > build. So I want use github ci to build docs and commit. > > Changes: > * Add website build check for pr > * Auto build and commit build files after pr was merged to `asf-site` > * Optinal: this ci can triggered by manual -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FLINK-34953) Add github ci for flink-web to auto commit build files
Zhongqiang Gong created FLINK-34953: --- Summary: Add github ci for flink-web to auto commit build files Key: FLINK-34953 URL: https://issues.apache.org/jira/browse/FLINK-34953 Project: Flink Issue Type: Improvement Components: Project Website Reporter: Zhongqiang Gong Currently, https://github.com/apache/flink-web commit build files by local build. So I want use github ci to build docs and commit. Changes: * Add website build check for pr * Auto build and commit build files after pr was merged to `asf-site` * Optinal: this ci can triggered by manual -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-34946) Flink Website Menu Adjustment
[
https://issues.apache.org/jira/browse/FLINK-34946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhongqiang Gong updated FLINK-34946:
Description:
{color:#00}Discuss
Thread：[https://lists.apache.org/thread/fvxrhc9nxzkjkt9t4ctmmopy9wlbp7wp]{color}
Expected Outcome :
- Menu "Getting Started"
Before:
* With Flink
* With Flink Stateful Functions
* With Flink ML
* With Flink Kubernetes Operator
* With Paimon(incubating) (formerly Flink Table Store)
* With Flink CDC
* Training Course
After:
* With Flink
* With Flink Kubernetes Operator
* With Flink CDC
* With Flink ML
* With Flink Stateful Functions
* Training Course
- Menu "Documentation" will same with "Getting Started"
- Add cdc repo to {{community.md}} , update repo order same with Menu "Getting
Started"
was:
{color:#00}Discuss
Thread：[https://lists.apache.org/thread/fvxrhc9nxzkjkt9t4ctmmopy9wlbp7wp]{color}
Expected Outcome :
- Menu "Getting Started"
Before:
* With Flink
* With Flink Stateful Functions
* With Flink ML
* With Flink Kubernetes Operator
* With Paimon(incubating) (formerly Flink Table Store)
* With Flink CDC
* Training Course
After:
* With Flink
* With Flink Kubernetes Operator
* With Flink CDC
* With Flink ML
* With Flink Stateful Functions
* Training Course
- Menu "Documentation" will same with "Getting Started"
> Flink Website Menu Adjustment
> -
>
> Key: FLINK-34946
> URL: https://issues.apache.org/jira/browse/FLINK-34946
> Project: Flink
> Issue Type: Improvement
> Components: Project Website
>Reporter: Zhongqiang Gong
>Assignee: Zhongqiang Gong
>Priority: Minor
> Labels: pull-request-available
>
> {color:#00}Discuss
> Thread：[https://lists.apache.org/thread/fvxrhc9nxzkjkt9t4ctmmopy9wlbp7wp]{color}
> Expected Outcome :
>
> - Menu "Getting Started"
> Before:
> * With Flink
> * With Flink Stateful Functions
> * With Flink ML
> * With Flink Kubernetes Operator
> * With Paimon(incubating) (formerly Flink Table Store)
> * With Flink CDC
> * Training Course
>
> After:
> * With Flink
> * With Flink Kubernetes Operator
> * With Flink CDC
> * With Flink ML
> * With Flink Stateful Functions
> * Training Course
>
> - Menu "Documentation" will same with "Getting Started"
> - Add cdc repo to {{community.md}} , update repo order same with Menu
> "Getting Started"
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (FLINK-34946) Flink Website Menu Adjustment
[
https://issues.apache.org/jira/browse/FLINK-34946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17831242#comment-17831242
]
Zhongqiang Gong commented on FLINK-34946:
-
[~leonard] [~renqs] I'm willing to take this.
> Flink Website Menu Adjustment
> -
>
> Key: FLINK-34946
> URL: https://issues.apache.org/jira/browse/FLINK-34946
> Project: Flink
> Issue Type: Improvement
> Components: Project Website
>Reporter: Zhongqiang Gong
>Priority: Minor
> Labels: pull-request-available
>
> {color:#00}Discuss
> Thread：[https://lists.apache.org/thread/fvxrhc9nxzkjkt9t4ctmmopy9wlbp7wp]{color}
> Expected Outcome :
>
> - Menu "Getting Started"
> Before:
> * With Flink
> * With Flink Stateful Functions
> * With Flink ML
> * With Flink Kubernetes Operator
> * With Paimon(incubating) (formerly Flink Table Store)
> * With Flink CDC
> * Training Course
>
> After:
> * With Flink
> * With Flink Kubernetes Operator
> * With Flink CDC
> * With Flink ML
> * With Flink Stateful Functions
> * Training Course
>
> - Menu "Documentation" will same with "Getting Started"
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-34946) Flink Website Menu Adjustment
[
https://issues.apache.org/jira/browse/FLINK-34946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhongqiang Gong updated FLINK-34946:
Description:
{color:#00}Discuss
Thread：[https://lists.apache.org/thread/fvxrhc9nxzkjkt9t4ctmmopy9wlbp7wp]{color}
Expected Outcome :
- Menu "Getting Started"
Before:
- With Flink
* With Flink Stateful Functions
* With Flink ML
* With Flink Kubernetes Operator
* With Paimon(incubating) (formerly Flink Table Store)
* With Flink CDC
* Training Course
After:
* With Flink
* With Flink Kubernetes Operator
* With Flink CDC
* With Flink ML
* With Flink Stateful Functions
* Training Course
- Menu "Documentation" will same with "Getting Started"
was:
{color:#00}Discuss
Thread：https://lists.apache.org/thread/fvxrhc9nxzkjkt9t4ctmmopy9wlbp7wp{color}
Expected Outcome :
- Menu "Getting Started"
Before: * With Flink
* With Flink Stateful Functions
* With Flink ML
* With Flink Kubernetes Operator
* With Paimon(incubating) (formerly Flink Table Store)
* With Flink CDC
* Training Course
After: * With Flink
* With Flink Kubernetes Operator
* With Flink CDC
* With Flink ML
* With Flink Stateful Functions
* Training Course
- Menu "Documentation" will same with "Getting Started"
> Flink Website Menu Adjustment
> -
>
> Key: FLINK-34946
> URL: https://issues.apache.org/jira/browse/FLINK-34946
> Project: Flink
> Issue Type: Improvement
> Components: Project Website
>Reporter: Zhongqiang Gong
>Priority: Minor
>
> {color:#00}Discuss
> Thread：[https://lists.apache.org/thread/fvxrhc9nxzkjkt9t4ctmmopy9wlbp7wp]{color}
> Expected Outcome :
>
> - Menu "Getting Started"
> Before:
> - With Flink
> * With Flink Stateful Functions
> * With Flink ML
> * With Flink Kubernetes Operator
> * With Paimon(incubating) (formerly Flink Table Store)
> * With Flink CDC
> * Training Course
>
> After:
> * With Flink
> * With Flink Kubernetes Operator
> * With Flink CDC
> * With Flink ML
> * With Flink Stateful Functions
> * Training Course
>
> - Menu "Documentation" will same with "Getting Started"
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-34946) Flink Website Menu Adjustment
[
https://issues.apache.org/jira/browse/FLINK-34946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhongqiang Gong updated FLINK-34946:
Description:
{color:#00}Discuss
Thread：[https://lists.apache.org/thread/fvxrhc9nxzkjkt9t4ctmmopy9wlbp7wp]{color}
Expected Outcome :
- Menu "Getting Started"
Before:
* With Flink
* With Flink Stateful Functions
* With Flink ML
* With Flink Kubernetes Operator
* With Paimon(incubating) (formerly Flink Table Store)
* With Flink CDC
* Training Course
After:
* With Flink
* With Flink Kubernetes Operator
* With Flink CDC
* With Flink ML
* With Flink Stateful Functions
* Training Course
- Menu "Documentation" will same with "Getting Started"
was:
{color:#00}Discuss
Thread：[https://lists.apache.org/thread/fvxrhc9nxzkjkt9t4ctmmopy9wlbp7wp]{color}
Expected Outcome :
- Menu "Getting Started"
Before:
- With Flink
* With Flink Stateful Functions
* With Flink ML
* With Flink Kubernetes Operator
* With Paimon(incubating) (formerly Flink Table Store)
* With Flink CDC
* Training Course
After:
* With Flink
* With Flink Kubernetes Operator
* With Flink CDC
* With Flink ML
* With Flink Stateful Functions
* Training Course
- Menu "Documentation" will same with "Getting Started"
> Flink Website Menu Adjustment
> -
>
> Key: FLINK-34946
> URL: https://issues.apache.org/jira/browse/FLINK-34946
> Project: Flink
> Issue Type: Improvement
> Components: Project Website
>Reporter: Zhongqiang Gong
>Priority: Minor
>
> {color:#00}Discuss
> Thread：[https://lists.apache.org/thread/fvxrhc9nxzkjkt9t4ctmmopy9wlbp7wp]{color}
> Expected Outcome :
>
> - Menu "Getting Started"
> Before:
> * With Flink
> * With Flink Stateful Functions
> * With Flink ML
> * With Flink Kubernetes Operator
> * With Paimon(incubating) (formerly Flink Table Store)
> * With Flink CDC
> * Training Course
>
> After:
> * With Flink
> * With Flink Kubernetes Operator
> * With Flink CDC
> * With Flink ML
> * With Flink Stateful Functions
> * Training Course
>
> - Menu "Documentation" will same with "Getting Started"
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-34946) Flink Website Menu Adjustment
[
https://issues.apache.org/jira/browse/FLINK-34946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhongqiang Gong updated FLINK-34946:
Description:
{color:#00}Discuss
Thread：https://lists.apache.org/thread/fvxrhc9nxzkjkt9t4ctmmopy9wlbp7wp{color}
Expected Outcome :
- Menu "Getting Started"
Before: * With Flink
* With Flink Stateful Functions
* With Flink ML
* With Flink Kubernetes Operator
* With Paimon(incubating) (formerly Flink Table Store)
* With Flink CDC
* Training Course
After: * With Flink
* With Flink Kubernetes Operator
* With Flink CDC
* With Flink ML
* With Flink Stateful Functions
* Training Course
- Menu "Documentation" will same with "Getting Started"
was:
{color:#00}Discuss Thread：
https://lists.apache.org/thread/fvxrhc9nxzkjkt9t4ctmmopy9wlbp7wp[link
title|[DISCUSS] Flink Website Menu Adjustment]{color}
{color:#00}Expected Outcome :{color}
{color:#00}- Menu "Getting Started"
{color}
{quote}{color:#00}Before:{color}
{quote}{color:#00}With Flink{color}{quote}
{quote}{color:#00}With Flink Stateful Functions{color}{quote}
{quote}{color:#00}With Flink ML{color}{quote}
{quote}{color:#00}With Flink Kubernetes Operator{color}{quote}
{quote}{color:#00}With Paimon(incubating) (formerly Flink Table
Store){color}{quote}
{quote}{color:#00}With Flink CDC{color}{quote}
{quote}{color:#00}Training Course{color}{quote}
{color:#00} {color}{color:#00}After:{color}
{quote}{color:#00}With Flink{color}
{color:#00}With Flink Kubernetes Operator{color}{quote}
{quote}{color:#00}With Flink CDC{color}{quote}
{quote}{color:#00}With Flink ML
{color}{quote}
{quote}{color:#00}With Flink Stateful Functions{color}{quote}
{quote}{color:#00}Training Course{color}{quote}{quote}
{quote}{color:#00} {color}{quote}
{color:#00}- Menu "Documentation" will same with "Getting Started"{color}
> Flink Website Menu Adjustment
> -
>
> Key: FLINK-34946
> URL: https://issues.apache.org/jira/browse/FLINK-34946
> Project: Flink
> Issue Type: Improvement
> Components: Project Website
>Reporter: Zhongqiang Gong
>Priority: Minor
>
> {color:#00}Discuss
> Thread：https://lists.apache.org/thread/fvxrhc9nxzkjkt9t4ctmmopy9wlbp7wp{color}
> Expected Outcome :
>
> - Menu "Getting Started"
>
> Before: * With Flink
> * With Flink Stateful Functions
> * With Flink ML
> * With Flink Kubernetes Operator
> * With Paimon(incubating) (formerly Flink Table Store)
> * With Flink CDC
> * Training Course
>
> After: * With Flink
> * With Flink Kubernetes Operator
> * With Flink CDC
> * With Flink ML
> * With Flink Stateful Functions
> * Training Course
>
> - Menu "Documentation" will same with "Getting Started"
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (FLINK-34946) Flink Website Menu Adjustment
Zhongqiang Gong created FLINK-34946:
---
Summary: Flink Website Menu Adjustment
Key: FLINK-34946
URL: https://issues.apache.org/jira/browse/FLINK-34946
Project: Flink
Issue Type: Improvement
Components: Project Website
Reporter: Zhongqiang Gong
{color:#00}Discuss Thread：
https://lists.apache.org/thread/fvxrhc9nxzkjkt9t4ctmmopy9wlbp7wp[link
title|[DISCUSS] Flink Website Menu Adjustment]{color}
{color:#00}Expected Outcome :{color}
{color:#00}- Menu "Getting Started"
{color}
{quote}{color:#00}Before:{color}
{quote}{color:#00}With Flink{color}{quote}
{quote}{color:#00}With Flink Stateful Functions{color}{quote}
{quote}{color:#00}With Flink ML{color}{quote}
{quote}{color:#00}With Flink Kubernetes Operator{color}{quote}
{quote}{color:#00}With Paimon(incubating) (formerly Flink Table
Store){color}{quote}
{quote}{color:#00}With Flink CDC{color}{quote}
{quote}{color:#00}Training Course{color}{quote}
{color:#00} {color}{color:#00}After:{color}
{quote}{color:#00}With Flink{color}
{color:#00}With Flink Kubernetes Operator{color}{quote}
{quote}{color:#00}With Flink CDC{color}{quote}
{quote}{color:#00}With Flink ML
{color}{quote}
{quote}{color:#00}With Flink Stateful Functions{color}{quote}
{quote}{color:#00}Training Course{color}{quote}{quote}
{quote}{color:#00} {color}{quote}
{color:#00}- Menu "Documentation" will same with "Getting Started"{color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-34943) Support Flink 1.19, 1.20-SNAPSHOT for JDBC connector
[ https://issues.apache.org/jira/browse/FLINK-34943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhongqiang Gong updated FLINK-34943: Summary: Support Flink 1.19, 1.20-SNAPSHOT for JDBC connector (was: Support Flink 1.19, 1.20-SNAPSHOT for OpenSearch connector) > Support Flink 1.19, 1.20-SNAPSHOT for JDBC connector > > > Key: FLINK-34943 > URL: https://issues.apache.org/jira/browse/FLINK-34943 > Project: Flink > Issue Type: Improvement > Components: Connectors / JDBC >Reporter: Zhongqiang Gong >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FLINK-34943) Support Flink 1.19, 1.20-SNAPSHOT for OpenSearch connector
Zhongqiang Gong created FLINK-34943: --- Summary: Support Flink 1.19, 1.20-SNAPSHOT for OpenSearch connector Key: FLINK-34943 URL: https://issues.apache.org/jira/browse/FLINK-34943 Project: Flink Issue Type: Improvement Components: Connectors / JDBC Reporter: Zhongqiang Gong -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-34841) [3.1][pipeline-connectors] Add jdbc pipeline sink
[
https://issues.apache.org/jira/browse/FLINK-34841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17830203#comment-17830203
]
Zhongqiang Gong commented on FLINK-34841:
-
[~leonard] [~renqs] I'm willing to take this. This work will be started
after https://issues.apache.org/jira/browse/FLINK-25421 ({*}Port JDBC Sink to
new Unified Sink API (FLIP-143){*}) was merged and flink-jdbc-connector
released a new version.
> [3.1][pipeline-connectors] Add jdbc pipeline sink
> --
>
> Key: FLINK-34841
> URL: https://issues.apache.org/jira/browse/FLINK-34841
> Project: Flink
> Issue Type: Improvement
> Components: Flink CDC
>Reporter: Flink CDC Issue Import
>Priority: Major
> Labels: github-import
>
> ### Search before asking
> - [X] I searched in the
> [issues|https://github.com/ververica/flink-cdc-connectors/issues] and found
> nothing similar.
> ### Motivation
> From my side and I saw in dingding group, Some user want to sync data to
> relation database by flink cdc.
> ### Solution
> _No response_
> ### Alternatives
> _No response_
> ### Anything else?
> _No response_
> ### Are you willing to submit a PR?
> - [X] I'm willing to submit a PR!
> Imported from GitHub
> Url: https://github.com/apache/flink-cdc/issues/2866
> Created by: [GOODBOY008|https://github.com/GOODBOY008]
> Labels: enhancement,
> Created at: Wed Dec 13 15:34:21 CST 2023
> State: open
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (FLINK-34732) Add document dead link check for Flink CDC Documentation
[ https://issues.apache.org/jira/browse/FLINK-34732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17830202#comment-17830202 ] Zhongqiang Gong commented on FLINK-34732: - [~leonard] [~renqs] I'm willing to take this. And pr is ready, please take a look. > Add document dead link check for Flink CDC Documentation > > > Key: FLINK-34732 > URL: https://issues.apache.org/jira/browse/FLINK-34732 > Project: Flink > Issue Type: Sub-task > Components: Flink CDC >Reporter: Zhongqiang Gong >Priority: Minor > Labels: pull-request-available > > Add ci for check dead link in flink cdc document. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FLINK-34732) Add document dead link check for Flink CDC Documentation
Zhongqiang Gong created FLINK-34732: --- Summary: Add document dead link check for Flink CDC Documentation Key: FLINK-34732 URL: https://issues.apache.org/jira/browse/FLINK-34732 Project: Flink Issue Type: Sub-task Components: Flink CDC Reporter: Zhongqiang Gong Add ci for check dead link in flink cdc document. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-34677) Refactor the structure of documentation for Flink CDC
[ https://issues.apache.org/jira/browse/FLINK-34677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17828201#comment-17828201 ] Zhongqiang Gong commented on FLINK-34677: - [~renqs] [~leonard] About ci of document , I want to add dead-link check ci for pr ,and also will be added to doc build ci for pre-check. > Refactor the structure of documentation for Flink CDC > - > > Key: FLINK-34677 > URL: https://issues.apache.org/jira/browse/FLINK-34677 > Project: Flink > Issue Type: Improvement > Components: Documentation, Flink CDC >Affects Versions: cdc-3.1.0 >Reporter: Qingsheng Ren >Assignee: Qingsheng Ren >Priority: Major > Labels: pull-request-available > Fix For: cdc-3.1.0 > > > The documentation structure of Flink CDC is not quite in good shape > currently. We plan to refactor it as below (✅ for existed pages and ️ for > new pages to write): > * Get Started > ** ️ Introduction > ** ✅ Quickstart > * Core Concept > ** ️ (Pages for data pipeline / sources / sinks / table ID / transform / > route) > * Connectors > ** ️ Overview > ** ✅ (Pages for connectors) > ** ✅ Legacy Flink CDC Sources (For CDC sources before 3.0) > * Deployment > ** ️ Standalone > ** ️ Kubernetes > ** ️ YARN > * Developer Guide > ** ️ Understand Flink CDC API > ** ️ Contribute to Flink CDC > ** ️ Licenses > * FAQ > ** ✅ Frequently Asked Questions -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-34677) Refactor the structure of documentation for Flink CDC
[ https://issues.apache.org/jira/browse/FLINK-34677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17827336#comment-17827336 ] Zhongqiang Gong commented on FLINK-34677: - [~renqs] Should add sub task to change `With Flink CDC`'s link in `Get Started` on [https://flink.apache.org/] should be changed. > Refactor the structure of documentation for Flink CDC > - > > Key: FLINK-34677 > URL: https://issues.apache.org/jira/browse/FLINK-34677 > Project: Flink > Issue Type: Improvement > Components: Flink CDC >Affects Versions: cdc-3.1.0 >Reporter: Qingsheng Ren >Assignee: Qingsheng Ren >Priority: Major > Labels: pull-request-available > Fix For: cdc-3.1.0 > > > The documentation structure of Flink CDC is not quite in good shape > currently. We plan to refactor it as below (✅ for existed pages and ️ for > new pages to write): > * Get Started > ** ️ Introduction > ** ✅ Quickstart > * Core Concept > ** ️ (Pages for data pipeline / sources / sinks / table ID / transform / > route) > * Connectors > ** ️ Overview > ** ✅ (Pages for connectors) > ** ✅ Legacy Flink CDC Sources (For CDC sources before 3.0) > * Deployment > ** ️ Standalone > ** ️ Kubernetes > ** ️ YARN > * Developer Guide > ** ️ Understand Flink CDC API > ** ️ Contribute to Flink CDC > ** ️ Licenses > * FAQ > ** ✅ Frequently Asked Questions -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FLINK-34578) Remove issue template
Zhongqiang Gong created FLINK-34578: --- Summary: Remove issue template Key: FLINK-34578 URL: https://issues.apache.org/jira/browse/FLINK-34578 Project: Flink Issue Type: Sub-task Components: Flink CDC Reporter: Zhongqiang Gong Flink cdc had done repo migration. So we should remove issue template. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FLINK-34577) Add IssueNavigationLink for IDEA git log
Zhongqiang Gong created FLINK-34577: --- Summary: Add IssueNavigationLink for IDEA git log Key: FLINK-34577 URL: https://issues.apache.org/jira/browse/FLINK-34577 Project: Flink Issue Type: Sub-task Components: Flink CDC Reporter: Zhongqiang Gong Add IssueNavigationLink for IDEA git log -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-34241) Transfer external connectors's CI result to Flink Slack #builds channel
[ https://issues.apache.org/jira/browse/FLINK-34241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17811195#comment-17811195 ] Zhongqiang Gong commented on FLINK-34241: - Hi [~leonard] , This should add bot or use app in slack and maintain `SLACK_BOT_TOKEN` or `SLACK_WEBHOOK_URL` variable in every connector github repo. > Transfer external connectors's CI result to Flink Slack #builds channel > --- > > Key: FLINK-34241 > URL: https://issues.apache.org/jira/browse/FLINK-34241 > Project: Flink > Issue Type: Improvement > Components: Build System / CI >Affects Versions: 1.18.1 >Reporter: Leonard Xu >Priority: Major > Fix For: 1.19.0 > > > As we discussed in FLINK-34237, we could timely found some blocker issue by > monitoring > external connectors' daily CI, we can transfer the CI failure to Flink’s > slack channel #builds > which release managers will check these failures and create JIRA tickets > timely. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-34241) Transfer external connectors's CI result to Flink Slack #builds channel
[ https://issues.apache.org/jira/browse/FLINK-34241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17811184#comment-17811184 ] Zhongqiang Gong commented on FLINK-34241: - [~leonard] I'm willing to take this issue , Please assign to me. > Transfer external connectors's CI result to Flink Slack #builds channel > --- > > Key: FLINK-34241 > URL: https://issues.apache.org/jira/browse/FLINK-34241 > Project: Flink > Issue Type: Improvement > Components: Build System / CI >Affects Versions: 1.18.1 >Reporter: Leonard Xu >Priority: Major > Fix For: 1.19.0 > > > As we discussed in FLINK-34237, we could timely found some blocker issue by > monitoring > external connectors' daily CI, we can transfer the CI failure to Flink’s > slack channel #builds > which release managers will check these failures and create JIRA tickets > timely. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-34183) Add NOTICE files for Flink CDC project
[ https://issues.apache.org/jira/browse/FLINK-34183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17809727#comment-17809727 ] Zhongqiang Gong commented on FLINK-34183: - [~leonard] I'm willing to take this. > Add NOTICE files for Flink CDC project > -- > > Key: FLINK-34183 > URL: https://issues.apache.org/jira/browse/FLINK-34183 > Project: Flink > Issue Type: Sub-task > Components: Flink CDC >Reporter: Leonard Xu >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-34187) Setup CI for Flink CDC project
[ https://issues.apache.org/jira/browse/FLINK-34187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17809725#comment-17809725 ] Zhongqiang Gong commented on FLINK-34187: - [~leonard] Here is the pr https://github.com/ververica/flink-cdc-connectors/pull/3022 > Setup CI for Flink CDC project > -- > > Key: FLINK-34187 > URL: https://issues.apache.org/jira/browse/FLINK-34187 > Project: Flink > Issue Type: Sub-task >Reporter: Leonard Xu >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-34182) Migrate doc website from ververica to flink
[ https://issues.apache.org/jira/browse/FLINK-34182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17809724#comment-17809724 ] Zhongqiang Gong commented on FLINK-34182: - [~leonard] Here is the pr https://github.com/ververica/flink-cdc-connectors/pull/3028 > Migrate doc website from ververica to flink > > > Key: FLINK-34182 > URL: https://issues.apache.org/jira/browse/FLINK-34182 > Project: Flink > Issue Type: Sub-task > Components: Flink CDC >Reporter: Leonard Xu >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-34187) Setup CI for Flink CDC project
[ https://issues.apache.org/jira/browse/FLINK-34187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17809719#comment-17809719 ] Zhongqiang Gong commented on FLINK-34187: - [~leonard] I'm willing to take this, Please assign to me. Thank you~ > Setup CI for Flink CDC project > -- > > Key: FLINK-34187 > URL: https://issues.apache.org/jira/browse/FLINK-34187 > Project: Flink > Issue Type: Sub-task >Reporter: Leonard Xu >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-34182) Migrate doc website from ververica to flink
[ https://issues.apache.org/jira/browse/FLINK-34182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17809718#comment-17809718 ] Zhongqiang Gong commented on FLINK-34182: - [~leonard] I'm willing to take this, Please assign to me. Thank you~ > Migrate doc website from ververica to flink > > > Key: FLINK-34182 > URL: https://issues.apache.org/jira/browse/FLINK-34182 > Project: Flink > Issue Type: Sub-task > Components: Flink CDC >Reporter: Leonard Xu >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-34018) Add flink 1.19 verison in ci for flink-connector-aws
[ https://issues.apache.org/jira/browse/FLINK-34018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17804336#comment-17804336 ] Zhongqiang Gong commented on FLINK-34018: - [https://github.com/apache/flink-connector-aws/blob/main/.github/workflows/common.yml] can only test jdk version with *8, 11 .* Should add more jdk version check for ci. > Add flink 1.19 verison in ci for flink-connector-aws > > > Key: FLINK-34018 > URL: https://issues.apache.org/jira/browse/FLINK-34018 > Project: Flink > Issue Type: Improvement >Reporter: Zhongqiang Gong >Priority: Minor > > Add flink 1.19 verison in ci for flink-connector-aws -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (FLINK-34018) Add flink 1.19 verison in ci for flink-connector-aws
[ https://issues.apache.org/jira/browse/FLINK-34018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17804328#comment-17804328 ] Zhongqiang Gong edited comment on FLINK-34018 at 1/8/24 2:38 PM: - Hi [~dannycranmer] , Thanks for your kind explain. I think push PR should add *1.19-SNAPSHOT* and modify exist flink with specific version to *SNAPSHOT.* Because pr for uncoming version should be checked when pr was opened. Also we can add flink with specific version to nightly.yml to check full version of flink. was (Author: JIRAUSER301076): Hi [~dannycranmer] , Thanks for your kind explain. I think push PR should add *1.19-SNAPSHOT* and modify exist flink with specific version to *SNAPSHOT.* Because pr for uncoming version should be checked when pr was opened. Also we can add move flink with specific version to nightly.yml to check full version of flink. > Add flink 1.19 verison in ci for flink-connector-aws > > > Key: FLINK-34018 > URL: https://issues.apache.org/jira/browse/FLINK-34018 > Project: Flink > Issue Type: Improvement >Reporter: Zhongqiang Gong >Priority: Minor > > Add flink 1.19 verison in ci for flink-connector-aws -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (FLINK-34018) Add flink 1.19 verison in ci for flink-connector-aws
[ https://issues.apache.org/jira/browse/FLINK-34018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17804328#comment-17804328 ] Zhongqiang Gong edited comment on FLINK-34018 at 1/8/24 2:36 PM: - Hi [~dannycranmer] , Thanks for your kind explain. I think push PR should add *1.19-SNAPSHOT* and modify exist flink with specific version to *SNAPSHOT.* Because pr for uncoming version should be checked when pr was opened. Also we can add move flink with specific version to nightly.yml to check full version of flink. was (Author: JIRAUSER301076): [~dannycranmer] I think push PR should add *1.19-SNAPSHOT* and modify exist flink with specific version to *SNAPSHOT.* Because pr for uncoming version should be checked when pr was opened. Also we can add move flink with specific version to nightly.yml to check full version of flink. > Add flink 1.19 verison in ci for flink-connector-aws > > > Key: FLINK-34018 > URL: https://issues.apache.org/jira/browse/FLINK-34018 > Project: Flink > Issue Type: Improvement >Reporter: Zhongqiang Gong >Priority: Minor > > Add flink 1.19 verison in ci for flink-connector-aws -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-34018) Add flink 1.19 verison in ci for flink-connector-aws
[ https://issues.apache.org/jira/browse/FLINK-34018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17804328#comment-17804328 ] Zhongqiang Gong commented on FLINK-34018: - [~dannycranmer] I think push PR should add *1.19-SNAPSHOT* and modify exist flink with specific version to *SNAPSHOT.* Because pr for uncoming version should be checked when pr was opened. Also we can add move flink with specific version to nightly.yml to check full version of flink. > Add flink 1.19 verison in ci for flink-connector-aws > > > Key: FLINK-34018 > URL: https://issues.apache.org/jira/browse/FLINK-34018 > Project: Flink > Issue Type: Improvement >Reporter: Zhongqiang Gong >Priority: Minor > > Add flink 1.19 verison in ci for flink-connector-aws -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FLINK-34018) Add flink 1.19 verison in ci for flink-connector-aws
Zhongqiang Gong created FLINK-34018: --- Summary: Add flink 1.19 verison in ci for flink-connector-aws Key: FLINK-34018 URL: https://issues.apache.org/jira/browse/FLINK-34018 Project: Flink Issue Type: Improvement Reporter: Zhongqiang Gong Add flink 1.19 verison in ci for flink-connector-aws -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (FLINK-33970) Add necessary checks for connector document
[
https://issues.apache.org/jira/browse/FLINK-33970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17803909#comment-17803909
]
Zhongqiang Gong edited comment on FLINK-33970 at 1/8/24 9:38 AM:
-
Hi [~martijnvisser] [~leonard]
Here is the pr for complete the docs check for connectors. Here is the
[PR|https://github.com/apache/flink-connector-shared-utils/pull/33] in
*flink-connector-shared-utils.*
*Hugo build check:*
_Because connector docs depends on flink main docs and no dependencies between
connector docs , so we can just check flink main docs and single connector
docs. Finally,We use hugo build to check docs._
* -check out flink repo with only `docs` dir cloned ,use *sparse-checkout*-
* check out flink repo with only docs dir and check other connectors docs
exclude current connector docs
* move connector (which repo related) docs into flink `docs` dir
* execute hugo build command
*Dead links check:*
_Because of hugo build cannot check dead link. It's very useful to add dead
link check for this._
* use npm module *markdown-link-check* to check dead link
Currently，dead link check is used only to connector docs, So about enable dead
link check in flink main repo, I want to add this check to
{color:#FF}docs.yml{color:#172b4d} too.{color}{color}
was (Author: JIRAUSER301076):
Hi [~martijnvisser] [~leonard]
Here is the pr for complete the docs check for connectors. Here is the
[PR|https://github.com/apache/flink-connector-shared-utils/pull/33] in
*flink-connector-shared-utils.*
*Hugo build check:*
_Because connector docs depends on flink main docs and no dependencies between
connector docs , so we can just check flink main docs and single connector
docs. Finally,We use hugo build to check docs._
* -check out flink repo with only `docs` dir cloned ,use *sparse-checkout*-
* check out flink repo with only docs dir and check other connectors docs
exclude current connector docs
* move connector (which repo related) docs into flink `docs` dir
* execute hugo build command
*Dead links check:*
_Because of hugo build cannot check dead link. It's very useful to add dead
link check for this._
* use npm module *markdown-link-check* to check dead link
> Add necessary checks for connector document
> ---
>
> Key: FLINK-33970
> URL: https://issues.apache.org/jira/browse/FLINK-33970
> Project: Flink
> Issue Type: Improvement
> Components: Documentation
>Reporter: Leonard Xu
>Assignee: Zhongqiang Gong
>Priority: Major
> Labels: pull-request-available
> Fix For: pulsar-4.2.0, pulsar-4.1.1
>
>
> In FLINK-33964, we found the documentation files in independent connector
> repos lacks basic checks like broken url, this ticket aims to add necessary
> checks and avoid similar issue.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (FLINK-34017) Connectors docs with 404 link in dynamodb.md
[ https://issues.apache.org/jira/browse/FLINK-34017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17804200#comment-17804200 ] Zhongqiang Gong edited comment on FLINK-34017 at 1/8/24 9:29 AM: - Hi [~martijnvisser] [~leonard] , Please assign to me, I am willing to fix this. And I think add dead link check is very useful to us. was (Author: JIRAUSER301076): [~leonard] Please assign to me > Connectors docs with 404 link in dynamodb.md > > > Key: FLINK-34017 > URL: https://issues.apache.org/jira/browse/FLINK-34017 > Project: Flink > Issue Type: Improvement > Components: Documentation >Reporter: Zhongqiang Gong >Priority: Minor > Labels: pull-request-available > Attachments: image-2024-01-08-17-21-16-434.png > > > docs Link: > [https://nightlies.apache.org/flink/flink-docs-release-1.18/docs/connectors/datastream/dynamodb/|http://example.com/] > screenshort: > !image-2024-01-08-17-21-16-434.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-34017) Connectors docs with 404 link in dynamodb.md
[ https://issues.apache.org/jira/browse/FLINK-34017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17804200#comment-17804200 ] Zhongqiang Gong commented on FLINK-34017: - [~leonard] Please assign to me > Connectors docs with 404 link in dynamodb.md > > > Key: FLINK-34017 > URL: https://issues.apache.org/jira/browse/FLINK-34017 > Project: Flink > Issue Type: Improvement > Components: Documentation >Reporter: Zhongqiang Gong >Priority: Minor > Attachments: image-2024-01-08-17-21-16-434.png > > > docs Link: > [https://nightlies.apache.org/flink/flink-docs-release-1.18/docs/connectors/datastream/dynamodb/|http://example.com/] > screenshort: > !image-2024-01-08-17-21-16-434.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FLINK-34017) Connectors docs with 404 link in dynamodb.md
Zhongqiang Gong created FLINK-34017: --- Summary: Connectors docs with 404 link in dynamodb.md Key: FLINK-34017 URL: https://issues.apache.org/jira/browse/FLINK-34017 Project: Flink Issue Type: Improvement Components: Documentation Reporter: Zhongqiang Gong Attachments: image-2024-01-08-17-21-16-434.png docs Link: [https://nightlies.apache.org/flink/flink-docs-release-1.18/docs/connectors/datastream/dynamodb/|http://example.com/] screenshort: !image-2024-01-08-17-21-16-434.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-33970) Add necessary checks for connector document
[ https://issues.apache.org/jira/browse/FLINK-33970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17803909#comment-17803909 ] Zhongqiang Gong commented on FLINK-33970: - Hi [~martijnvisser] [~leonard] Here is the pr for complete the docs check for connectors. Here is the [PR|https://github.com/apache/flink-connector-shared-utils/pull/33] in *flink-connector-shared-utils.* *Hugo build check:* _Because connector docs depends on flink main docs and no dependencies between connector docs , so we can just check flink main docs and single connector docs. Finally,We use hugo build to check docs._ * -check out flink repo with only `docs` dir cloned ,use *sparse-checkout*- * check out flink repo with only docs dir and check other connectors docs exclude current connector docs * move connector (which repo related) docs into flink `docs` dir * execute hugo build command *Dead links check:* _Because of hugo build cannot check dead link. It's very useful to add dead link check for this._ * use npm module *markdown-link-check* to check dead link > Add necessary checks for connector document > --- > > Key: FLINK-33970 > URL: https://issues.apache.org/jira/browse/FLINK-33970 > Project: Flink > Issue Type: Improvement > Components: Documentation >Reporter: Leonard Xu >Assignee: Zhongqiang Gong >Priority: Major > Labels: pull-request-available > Fix For: pulsar-4.2.0, pulsar-4.1.1 > > > In FLINK-33964, we found the documentation files in independent connector > repos lacks basic checks like broken url, this ticket aims to add necessary > checks and avoid similar issue. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (FLINK-33970) Add necessary checks for connector document
[ https://issues.apache.org/jira/browse/FLINK-33970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17803382#comment-17803382 ] Zhongqiang Gong edited comment on FLINK-33970 at 1/7/24 1:16 AM: - [~martijnvisser] [~leonard] Can you give me some advices for this issue? I have a idea for this issue: *Hugo build check:* _Because connector docs depends on flink main docs and no dependencies between connector docs , so we can just check flink main docs and single connector docs. Finally,We use hugo build to check docs._ * -check out flink repo with only `docs` dir cloned ,use *sparse-checkout*- * check out flink repo with only docs dir and check other connectors docs exclude current connector docs * move connector (which repo related) docs into flink `docs` dir * execute hugo build command *Dead links check:* _Because of hugo build cannot check dead link. It's very useful to add dead link check for this._ * use npm module *markdown-link-check* to check dead link was (Author: JIRAUSER301076): [~martijnvisser] [~leonard] Can you give me some advices for this issue? I have a idea for this issue: *Hugo build check:* _Because connector docs depends on flink main docs and no dependencies between connector docs , so we can just check flink main docs and single connector docs. Finally,We use hugo build to check docs._ * check out flink repo with only `docs` dir cloned ,use *sparse-checkout* * move connector (which repo related) docs into flink `docs` dir * execute hugo build command *Dead links check:* _Because of hugo build cannot check dead link. It's very useful to add dead link check for this._ * use npm module *markdown-link-check* to check dead link > Add necessary checks for connector document > --- > > Key: FLINK-33970 > URL: https://issues.apache.org/jira/browse/FLINK-33970 > Project: Flink > Issue Type: Improvement > Components: Documentation >Reporter: Leonard Xu >Assignee: Zhongqiang Gong >Priority: Major > Labels: pull-request-available > Fix For: pulsar-4.2.0, pulsar-4.1.1 > > > In FLINK-33964, we found the documentation files in independent connector > repos lacks basic checks like broken url, this ticket aims to add necessary > checks and avoid similar issue. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (FLINK-33970) Add necessary checks for connector document
[ https://issues.apache.org/jira/browse/FLINK-33970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17803450#comment-17803450 ] Zhongqiang Gong edited comment on FLINK-33970 at 1/5/24 8:10 AM: - I had complete dead link check at [https://github.com/GOODBOY008/flink-connector-shared-utils/tree/ci_utils] jdbc connector action for test ci : [https://github.com/GOODBOY008/flink-connector-jdbc/actions/runs/7419405021/job/2012787] was (Author: JIRAUSER301076): I had complete dead link check at [https://github.com/|https://github.com/apache/flink-connector-shared-utils/tree/ci_utils] [GOODBOY008|https://github.com/GOODBOY008/flink-connector-jdbc/actions/runs/7419405021/job/2012787] [/flink-connector-shared-utils/tree/ci_utils|https://github.com/apache/flink-connector-shared-utils/tree/ci_utils] jdbc connector action for test ci : [https://github.com/GOODBOY008/flink-connector-jdbc/actions/runs/7419405021/job/2012787] > Add necessary checks for connector document > --- > > Key: FLINK-33970 > URL: https://issues.apache.org/jira/browse/FLINK-33970 > Project: Flink > Issue Type: Improvement > Components: Documentation >Reporter: Leonard Xu >Assignee: Zhongqiang Gong >Priority: Major > Labels: pull-request-available > Fix For: pulsar-4.2.0, pulsar-4.1.1 > > > In FLINK-33964, we found the documentation files in independent connector > repos lacks basic checks like broken url, this ticket aims to add necessary > checks and avoid similar issue. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (FLINK-33970) Add necessary checks for connector document
[ https://issues.apache.org/jira/browse/FLINK-33970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17803450#comment-17803450 ] Zhongqiang Gong edited comment on FLINK-33970 at 1/5/24 8:07 AM: - I had complete dead link check at [https://github.com/|https://github.com/apache/flink-connector-shared-utils/tree/ci_utils] [GOODBOY008|https://github.com/GOODBOY008/flink-connector-jdbc/actions/runs/7419405021/job/2012787] [/flink-connector-shared-utils/tree/ci_utils|https://github.com/apache/flink-connector-shared-utils/tree/ci_utils] jdbc connector action for test ci : [https://github.com/GOODBOY008/flink-connector-jdbc/actions/runs/7419405021/job/2012787] was (Author: JIRAUSER301076): jdbc action for test : https://github.com/GOODBOY008/flink-connector-jdbc/actions/runs/7419405021/job/2012787 > Add necessary checks for connector document > --- > > Key: FLINK-33970 > URL: https://issues.apache.org/jira/browse/FLINK-33970 > Project: Flink > Issue Type: Improvement > Components: Documentation >Reporter: Leonard Xu >Assignee: Zhongqiang Gong >Priority: Major > Labels: pull-request-available > Fix For: pulsar-4.2.0, pulsar-4.1.1 > > > In FLINK-33964, we found the documentation files in independent connector > repos lacks basic checks like broken url, this ticket aims to add necessary > checks and avoid similar issue. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-33970) Add necessary checks for connector document
[ https://issues.apache.org/jira/browse/FLINK-33970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17803450#comment-17803450 ] Zhongqiang Gong commented on FLINK-33970: - jdbc action for test : https://github.com/GOODBOY008/flink-connector-jdbc/actions/runs/7419405021/job/2012787 > Add necessary checks for connector document > --- > > Key: FLINK-33970 > URL: https://issues.apache.org/jira/browse/FLINK-33970 > Project: Flink > Issue Type: Improvement > Components: Documentation >Reporter: Leonard Xu >Assignee: Zhongqiang Gong >Priority: Major > Labels: pull-request-available > Fix For: pulsar-4.2.0, pulsar-4.1.1 > > > In FLINK-33964, we found the documentation files in independent connector > repos lacks basic checks like broken url, this ticket aims to add necessary > checks and avoid similar issue. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (FLINK-33970) Add necessary checks for connector document
[ https://issues.apache.org/jira/browse/FLINK-33970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17803382#comment-17803382 ] Zhongqiang Gong edited comment on FLINK-33970 at 1/5/24 2:48 AM: - [~martijnvisser] [~leonard] Can you give me some advices for this issue? I have a idea for this issue: *Hugo build check:* _Because connector docs depends on flink main docs and no dependencies between connector docs , so we can just check flink main docs and single connector docs. Finally,We use hugo build to check docs._ * check out flink repo with only `docs` dir cloned ,use *sparse-checkout* * move connector (which repo related) docs into flink `docs` dir * execute hugo build command _Because of hugo build cannot check dead link. It's very useful to add dead link check for this._ *Dead links check:* * use npm module *markdown-link-check* to check dead link was (Author: JIRAUSER301076): [~martijnvisser] [~leonard] Can you give me some advices for this issue? I have a idea for this issue: *Hugo build check:* _Because connector docs depends on flink main docs and no dependencies between connector docs , so we can just check flink main docs and single connector docs. Finally,We use hugo build to check docs._ * check out flink repo with only `docs` dir cloned ,use *sparse-checkout* * move connector (which repo related) docs into flink `docs` dir * execute hugo build command Because of hugo build cannot check dead link. It's very useful to add dead link check for this. *Dead links check:* * use npm module *markdown-link-check* to check dead link > Add necessary checks for connector document > --- > > Key: FLINK-33970 > URL: https://issues.apache.org/jira/browse/FLINK-33970 > Project: Flink > Issue Type: Improvement > Components: Documentation >Reporter: Leonard Xu >Assignee: Zhongqiang Gong >Priority: Major > Labels: pull-request-available > Fix For: pulsar-4.2.0, pulsar-4.1.1 > > > In FLINK-33964, we found the documentation files in independent connector > repos lacks basic checks like broken url, this ticket aims to add necessary > checks and avoid similar issue. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (FLINK-33970) Add necessary checks for connector document
[ https://issues.apache.org/jira/browse/FLINK-33970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17803382#comment-17803382 ] Zhongqiang Gong edited comment on FLINK-33970 at 1/5/24 2:48 AM: - [~martijnvisser] [~leonard] Can you give me some advices for this issue? I have a idea for this issue: *Hugo build check:* _Because connector docs depends on flink main docs and no dependencies between connector docs , so we can just check flink main docs and single connector docs. Finally,We use hugo build to check docs._ * check out flink repo with only `docs` dir cloned ,use *sparse-checkout* * move connector (which repo related) docs into flink `docs` dir * execute hugo build command *Dead links check:* _Because of hugo build cannot check dead link. It's very useful to add dead link check for this._ * use npm module *markdown-link-check* to check dead link was (Author: JIRAUSER301076): [~martijnvisser] [~leonard] Can you give me some advices for this issue? I have a idea for this issue: *Hugo build check:* _Because connector docs depends on flink main docs and no dependencies between connector docs , so we can just check flink main docs and single connector docs. Finally,We use hugo build to check docs._ * check out flink repo with only `docs` dir cloned ,use *sparse-checkout* * move connector (which repo related) docs into flink `docs` dir * execute hugo build command _Because of hugo build cannot check dead link. It's very useful to add dead link check for this._ *Dead links check:* * use npm module *markdown-link-check* to check dead link > Add necessary checks for connector document > --- > > Key: FLINK-33970 > URL: https://issues.apache.org/jira/browse/FLINK-33970 > Project: Flink > Issue Type: Improvement > Components: Documentation >Reporter: Leonard Xu >Assignee: Zhongqiang Gong >Priority: Major > Labels: pull-request-available > Fix For: pulsar-4.2.0, pulsar-4.1.1 > > > In FLINK-33964, we found the documentation files in independent connector > repos lacks basic checks like broken url, this ticket aims to add necessary > checks and avoid similar issue. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (FLINK-33970) Add necessary checks for connector document
[
https://issues.apache.org/jira/browse/FLINK-33970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17803382#comment-17803382
]
Zhongqiang Gong edited comment on FLINK-33970 at 1/5/24 2:48 AM:
-
[~martijnvisser] [~leonard] Can you give me some advices for this issue?
I have a idea for this issue:
*Hugo build check:*
_Because connector docs depends on flink main docs and no dependencies between
connector docs , so we can just check flink main docs and single connector
docs. Finally,We use hugo build to check docs._
* check out flink repo with only `docs` dir cloned ,use *sparse-checkout*
* move connector (which repo related) docs into flink `docs` dir
* execute hugo build command
Because of hugo build cannot check dead link. It's very useful to add dead link
check for this.
*Dead links check:*
* use npm module *markdown-link-check* to check dead link
was (Author: JIRAUSER301076):
[~martijnvisser] [~leonard] Can you give me some advices for this issue?
I have a idea for this issue:
*Hugo build check:*
{_}Because connector docs depends on flink main docs and no dependencies
between connector docs , so we can just check flink main docs and single
connector docs. Finally,We use hugo build to check docs.{_}{*}{*}
* check out flink repo with only `docs` dir cloned ,use *sparse-checkout*
* move connector (which repo related) docs into flink `docs` dir
* execute hugo build command
Because of hugo build cannot check dead link. It's very useful to add dead link
check for this.
*Dead links check:*
* use npm module *markdown-link-check* to check dead link
> Add necessary checks for connector document
> ---
>
> Key: FLINK-33970
> URL: https://issues.apache.org/jira/browse/FLINK-33970
> Project: Flink
> Issue Type: Improvement
> Components: Documentation
>Reporter: Leonard Xu
>Assignee: Zhongqiang Gong
>Priority: Major
> Labels: pull-request-available
> Fix For: pulsar-4.2.0, pulsar-4.1.1
>
>
> In FLINK-33964, we found the documentation files in independent connector
> repos lacks basic checks like broken url, this ticket aims to add necessary
> checks and avoid similar issue.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (FLINK-33970) Add necessary checks for connector document
[
https://issues.apache.org/jira/browse/FLINK-33970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17803382#comment-17803382
]
Zhongqiang Gong edited comment on FLINK-33970 at 1/5/24 2:47 AM:
-
[~martijnvisser] [~leonard] Can you give me some advices for this issue?
I have a idea for this issue:
*Hugo build check:*
{_}Because connector docs depends on flink main docs and no dependencies
between connector docs , so we can just check flink main docs and single
connector docs. Finally,We use hugo build to check docs.{_}{*}{*}
* check out flink repo with only `docs` dir cloned ,use *sparse-checkout*
* move connector (which repo related) docs into flink `docs` dir
* execute hugo build command
Because of hugo build cannot check dead link. It's very useful to add dead link
check for this.
*Dead links check:*
* use npm module *markdown-link-check* to check dead link
was (Author: JIRAUSER301076):
[~martijnvisser] [~leonard] Can you give me some advices for this issue?
I have a idea for this issue:
*Hugo build check:*
* check out flink repo with only `docs` dir cloned ,use *sparse-checkout*
* move connector (which repo related) docs into flink `docs` dir
* execute hugo build command
Because of hugo build cannot check dead link. It's very useful to add dead link
check for this.
*Dead links check:*
* use npm module *markdown-link-check* to check dead link
> Add necessary checks for connector document
> ---
>
> Key: FLINK-33970
> URL: https://issues.apache.org/jira/browse/FLINK-33970
> Project: Flink
> Issue Type: Improvement
> Components: Documentation
>Reporter: Leonard Xu
>Assignee: Zhongqiang Gong
>Priority: Major
> Labels: pull-request-available
> Fix For: pulsar-4.2.0, pulsar-4.1.1
>
>
> In FLINK-33964, we found the documentation files in independent connector
> repos lacks basic checks like broken url, this ticket aims to add necessary
> checks and avoid similar issue.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (FLINK-33970) Add necessary checks for connector document
[ https://issues.apache.org/jira/browse/FLINK-33970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17803382#comment-17803382 ] Zhongqiang Gong commented on FLINK-33970: - [~martijnvisser] [~leonard] Can you give me some advices for this issue? I have a idea for this issue: *Hugo build check:* * check out flink repo with only `docs` dir cloned ,use *sparse-checkout* * move connector (which repo related) docs into flink `docs` dir * execute hugo build command Because of hugo build cannot check dead link. It's very useful to add dead link check for this. *Dead links check:* * use npm module *markdown-link-check* to check dead link > Add necessary checks for connector document > --- > > Key: FLINK-33970 > URL: https://issues.apache.org/jira/browse/FLINK-33970 > Project: Flink > Issue Type: Improvement > Components: Documentation >Reporter: Leonard Xu >Assignee: Zhongqiang Gong >Priority: Major > Labels: pull-request-available > Fix For: pulsar-4.2.0, pulsar-4.1.1 > > > In FLINK-33964, we found the documentation files in independent connector > repos lacks basic checks like broken url, this ticket aims to add necessary > checks and avoid similar issue. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-33970) Add necessary checks for connector document
[ https://issues.apache.org/jira/browse/FLINK-33970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17803203#comment-17803203 ] Zhongqiang Gong commented on FLINK-33970: - [~martijnvisser] And I checked my pr cannot solve the original problem , I will try to find the way to both check hugo build and dead link check. Thanks for your kind remind. > Add necessary checks for connector document > --- > > Key: FLINK-33970 > URL: https://issues.apache.org/jira/browse/FLINK-33970 > Project: Flink > Issue Type: Improvement > Components: Documentation >Reporter: Leonard Xu >Assignee: Zhongqiang Gong >Priority: Major > Labels: pull-request-available > Fix For: pulsar-4.2.0, pulsar-4.1.1 > > > In FLINK-33964, we found the documentation files in independent connector > repos lacks basic checks like broken url, this ticket aims to add necessary > checks and avoid similar issue. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-33970) Add necessary checks for connector document
[ https://issues.apache.org/jira/browse/FLINK-33970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17803196#comment-17803196 ] Zhongqiang Gong commented on FLINK-33970: - [~martijnvisser] I had tried to use hugo to check document build , but `config.toml` is neccessary for hugo. So I use simple scrips to check dead link. > Add necessary checks for connector document > --- > > Key: FLINK-33970 > URL: https://issues.apache.org/jira/browse/FLINK-33970 > Project: Flink > Issue Type: Improvement > Components: Documentation >Reporter: Leonard Xu >Assignee: Zhongqiang Gong >Priority: Major > Labels: pull-request-available > Fix For: pulsar-4.2.0, pulsar-4.1.1 > > > In FLINK-33964, we found the documentation files in independent connector > repos lacks basic checks like broken url, this ticket aims to add necessary > checks and avoid similar issue. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (FLINK-33970) Add necessary checks for connector document
[ https://issues.apache.org/jira/browse/FLINK-33970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17803150#comment-17803150 ] Zhongqiang Gong edited comment on FLINK-33970 at 1/4/24 1:13 PM: - [~tison] I also want to add this check to other connector repo to avoid to build flink doc failed , what do you think about this ? was (Author: JIRAUSER301076): [~tison] I also want to add this check to other connector repo to avoid to build flink doc failed , want do you think about this ? > Add necessary checks for connector document > --- > > Key: FLINK-33970 > URL: https://issues.apache.org/jira/browse/FLINK-33970 > Project: Flink > Issue Type: Improvement > Components: Documentation >Reporter: Leonard Xu >Assignee: Zhongqiang Gong >Priority: Major > Labels: pull-request-available > Fix For: pulsar-4.2.0, pulsar-4.1.1 > > > In FLINK-33964, we found the documentation files in independent connector > repos lacks basic checks like broken url, this ticket aims to add necessary > checks and avoid similar issue. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-33970) Add necessary checks for connector document
[ https://issues.apache.org/jira/browse/FLINK-33970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17803150#comment-17803150 ] Zhongqiang Gong commented on FLINK-33970: - [~tison] I also want to add this check to other connector repo to avoid to build flink doc failed , want do you think about this ? > Add necessary checks for connector document > --- > > Key: FLINK-33970 > URL: https://issues.apache.org/jira/browse/FLINK-33970 > Project: Flink > Issue Type: Improvement > Components: Documentation >Reporter: Leonard Xu >Assignee: Zhongqiang Gong >Priority: Major > Labels: pull-request-available > Fix For: pulsar-4.2.0, pulsar-4.1.1 > > > In FLINK-33964, we found the documentation files in independent connector > repos lacks basic checks like broken url, this ticket aims to add necessary > checks and avoid similar issue. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-33970) Add necessary checks for connector document
[ https://issues.apache.org/jira/browse/FLINK-33970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17802025#comment-17802025 ] Zhongqiang Gong commented on FLINK-33970: - [~leonard] I am willing to take this issue, Please assign to me. Thank you~ > Add necessary checks for connector document > --- > > Key: FLINK-33970 > URL: https://issues.apache.org/jira/browse/FLINK-33970 > Project: Flink > Issue Type: Improvement > Components: Documentation >Reporter: Leonard Xu >Priority: Major > > In FLINK-33964, we found the documentation files in independent connector > repos lacks basic checks like broken url, this ticket aims to add necessary > checks and avoid similar issue. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FLINK-32767) Fix en-doc SHOW CREATE TABLE usage
Zhongqiang Gong created FLINK-32767: --- Summary: Fix en-doc SHOW CREATE TABLE usage Key: FLINK-32767 URL: https://issues.apache.org/jira/browse/FLINK-32767 Project: Flink Issue Type: Bug Reporter: Zhongqiang Gong -- This message was sent by Atlassian Jira (v8.20.10#820010)
