You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Flink Jira Bot (Jira)" <ji...@apache.org> on 2021/11/13 22:39:00 UTC

[jira] [Updated] (FLINK-13858) Add flink-connector-elasticsearch6 Specify the field as the primary key id

     [ https://issues.apache.org/jira/browse/FLINK-13858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Flink Jira Bot updated FLINK-13858:
-----------------------------------
    Labels: auto-deprioritized-major stale-minor  (was: auto-deprioritized-major)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see this issues has been marked as Minor but is unassigned and neither itself nor its Sub-Tasks have been updated for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is still Minor, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized.


> Add flink-connector-elasticsearch6 Specify the field as the primary key id
> --------------------------------------------------------------------------
>
>                 Key: FLINK-13858
>                 URL: https://issues.apache.org/jira/browse/FLINK-13858
>             Project: Flink
>          Issue Type: Improvement
>          Components: Connectors / ElasticSearch
>    Affects Versions: 1.6.3, 1.6.4, 1.7.2, 1.8.0, 1.8.1, 1.9.0
>            Reporter: hubin
>            Priority: Minor
>              Labels: auto-deprioritized-major, stale-minor
>
> For example, syncing an order table sink to es6, order_id is primary key 
>  `insert into es6_table select order_id, order_name from source_table`
> However, the primary key in es6 is randomly generated, and the order_id cannot be used to find the record.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)