[FLINK-38661][docs] Add 2.2.0 release note #27235
Conversation
| (e.g., Retrieval-Augmented Generation, RAG) directly within Flink. | ||
|
|
||
| See more details about the capabilities and usages of | ||
| Flink's [Vector Search](https://nightlies.apache.org/flink/flink-docs-release-2.2/docs/dev/table/sql/queries/vector-search/). |
There was a problem hiding this comment.
this link is a technical reference to the API and is not guide to use it in in RAG etc .
There was a problem hiding this comment.
I think we're missing some quick starts for RAG now. Seems we can only link to the vector search doc here...
|
|
||
| ##### [FLINK-38104](https://issues.apache.org/jira/browse/FLINK-38104) | ||
|
|
||
| Flink already expanded the `ML_PREDICT` table-valued function (TVF) to perform |
There was a problem hiding this comment.
Was the "already expanded " in 2.1? This implies there was a datastream version of ML_PREDICT at 2.0 that was enhanced at 2.1.
Maybe we should include SQL as well as the table api
There was a problem hiding this comment.
@davidradl I rewrite this part. Please take a look.
github-actions
bot
added
the
community-reviewed
| that changed between Flink 2.1 and Flink 2.2. Please read these notes carefully if you are | ||
| planning to upgrade your Flink version to 2.2. | ||
|
|
||
| ### Table SQL / API |
There was a problem hiding this comment.
There is a breaking change for Flink SQL after fixing FLINK-20539
Can we also have it mentioned in release notes?
In jira's for FLINK-20539 there is a filled release notes field.
May be we should also check in case there are some more jira issues targeted to 2.2.0 with not empty release notes field
There was a problem hiding this comment.
@snuyanzin Thanks. Could you help to provide the document about this part?
There was a problem hiding this comment.
what document are you talking about?
There was a problem hiding this comment.
If you open https://issues.apache.org/jira/browse/FLINK-20539
there is a field Release Note: like for every other jira
if this field is not empty then it should be reflected in release notes
5 participants
What is the purpose of the change
This pull request adds 2.2.0 release note.
Brief change log
This pull request adds 2.2.0 release note.
Verifying this change
This change is a docs work without any test coverage.
Does this pull request potentially affect one of the following parts:
@Public(Evolving): (no)Documentation