1.3.0-rc.61

Metacat 1.3.0 Release Candidate 61

1.3.0-rc.60

Metacat 1.3.0 Release Candidate 60.

1.3.0-rc.59

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.

1.3.0-rc.58

Metacat 1.3.0 Release Candidate 58.

1.3.0-rc.57

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

1.3.0-rc.56

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":
[]
},

1.3.0-rc.55

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.

1.3.0-rc.54

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

1.3.0-rc.53

RequestWrapper invokes rate limiter check within try-catch block.

1.3.0-rc.52

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