Hi Rex, Currently, the unique key is inferred by the optimizer. However, the inference is not perfect. There are known issues that the unique key is not derived correctly, e.g. FLINK-20036 (is this opened by you?). If you think you have the same case, please open an issue.
Query hint is a nice way for this, but it is not supported yet. We have an issue to track supporting query hint, see FLINK-17173. Beest, Jark On Tue, 17 Nov 2020 at 15:23, Rex Fenley <r...@remind101.com> wrote: > Hello, > > I have quite a few joins in my plan that have > > leftInputSpec=[NoUniqueKey] > > in Flink UI. I know this can't truly be the case that there is no unique > key, at least for some of these joins that I've evaluated. > > Is there a way to hint to the join what the unique key is for a table? > > Thanks! > > -- > > Rex Fenley | Software Engineer - Mobile and Backend > > > Remind.com <https://www.remind.com/> | BLOG <http://blog.remind.com/> | > FOLLOW US <https://twitter.com/remindhq> | LIKE US > <https://www.facebook.com/remindhq> >
