metacat

Metacat 1.3.0 Release Candidate 62

Metacat 1.3.0 Release Candidate 61

Metacat 1.3.0 Release Candidate 60.

adding back keysets:
For sources using JDBC connector (s3, snowflake, mysql) append partition keys to response.
new table GET response includes set of partition/primary/sort/index keys.

Metacat 1.3.0 Release Candidate 58.

Fixes a bug where Iceberg commits can get lost when schema updates race with data updates, and add logging for Iceberg commits

For sources using JDBC connector (s3, snowflake, mysql) append partition keys to response.
new table GET response includes set of partition/primary/sort/index keys.
existing clients expecting partition_keys array should not break as it is backwards compatible.

"keys":
{
"partition":
[],
"primary":
[
{
"name": "PRIMARY",
"fields":
[
"id"
]
}
],
"sort":
[],
"index":
[]
},

Publish the list of partition ids on TABLE_PARTITION_UPDATE event (PR #449)

• Adds and deletes are both published.
• The list of partitions ids does not classify if the updated partition(s) were added or deleted, but either all partitions in the list are added or all are deleted. We can infer whether it was added or deleted using the numCreatedPartitions and numDeletedPartitions values. Only of the values will be non-zero.

Avoid wrapping MetacatException (and subclasses) in a new MetacatException.

RequestWrapper invokes rate limiter check within try-catch block.

• Added a table type metric dimension to requests.
• Added ability to refresh jdbc connection pools.

Metacat 1.3.0 Release Candidate 51.

Metacat 1.3.0 Release Candidate 50.

Metacat 1.3.0 Release Candidate 49.

Metacat 1.3.0 Release Candidate 48.

Metacat 1.3.0 Release Candidate 47.

Metacat 1.3.0 Release Candidate 46.

Metacat 1.3.0 Release Candidate 45.

Metacat 1.3.0 Release Candidate 44.

• Fixes a couple of SQL vulnerabilities in the List Metadata API and the Tag API.

Metacat 1.3.0 Release Candidate 43.

Milestone