feat: add backfill columns and refresh materialized view operations (#335)

## Summary

- Update `add_columns` and `alter_columns` schemas: remove `identity`,
`context`, `id` from requests, remove `transaction_id` from responses,
rename `NewColumnTransform` to `AddColumnsEntry`, adopt OpenAPI 3.1
nullable style
- Add `POST /v1/table/{id}/backfill_column`
(`AlterTableBackfillColumns`) — trigger async backfill job for a
computed column, returns 202 with job_id
- Add `POST /v1/table/{id}/refresh` (`RefreshMaterializedView`) —
trigger async materialized view refresh, returns 202 with job_id
- Add new operations to `LanceNamespace` interfaces (Python, Java sync,
Java async)
- Regenerate all clients (Rust, Python, Java)
- Update operation docs and REST impl spec

## Test plan

- [x] YAML validates successfully
- [x] All `$ref` targets resolve
- [x] Rust client compiles
- [x] Java builds with mvnw
- [x] Python imports verified

---------

Co-authored-by: Claude <noreply@anthropic.com>

Author: jackye1995

docs/src/client/operations/index.md

@@ -76,7 +76,9 @@ See [REST Routes](../../rest/catalog-spec.md#rest-routes) for more details.
 | AnalyzeTableQueryPlan     | 1               |           | ✓     |       |          | ✓    |             |
 | AlterTableAddColumns      | 1               |           | ✓     |       |          | ✓    |             |
 | AlterTableAlterColumns    | 1               |           | ✓     |       | ✓        |      |             |
+| AlterTableBackfillColumns | 1               |           | ✓     |       |          | ✓    |             |
 | AlterTableDropColumns     | 1               |           | ✓     |       | ✓        |      |             |
+| RefreshMaterializedView   | 1               |           | ✓     |       |          | ✓    |             |
 | UpdateTableSchemaMetadata | 1               |           | ✓     |       | ✓        |      |             |
 | GetTableStats             | 1               |           | ✓     |       | ✓        |      |             |
 | ListTableTags             | 1               |           | ✓     |       | ✓        |      |             |

docs/src/client/operations/models/AddColumnsEntry.md

@@ -0,0 +1,15 @@
+
+
+# AddColumnsEntry
+
+
+## Properties
+
+| Name | Type | Description | Notes |
+|------------ | ------------- | ------------- | -------------|
+|**name** | **String** | Name of the new column |  |
+|**expression** | **String** | SQL expression for the column (optional if virtual_column is specified) |  [optional] |
+|**virtualColumn** | [**AddVirtualColumnEntry**](AddVirtualColumnEntry.md) |  |  [optional] |
+
+
+

docs/src/client/operations/models/AlterColumnsEntry.md

@@ -11,7 +11,7 @@
 |**dataType** | **Object** | New data type for the column using JSON representation (optional) |  |
 |**rename** | **String** | New name for the column (optional) |  [optional] |
 |**nullable** | **Boolean** | Whether the column should be nullable (optional) |  [optional] |
-|**virtualColumn** | [**AlterVirtualColumnEntry**](AlterVirtualColumnEntry.md) | Virtual column alterations (optional) |  [optional] |
+|**virtualColumn** | [**AlterVirtualColumnEntry**](AlterVirtualColumnEntry.md) |  |  [optional] |
 
 
 

docs/src/client/operations/models/AlterTableAddColumnsRequest.md

@@ -7,10 +7,7 @@
 
 | Name | Type | Description | Notes |
 |------------ | ------------- | ------------- | -------------|
-|**identity** | [**Identity**](Identity.md) |  |  [optional] |
-|**context** | **Map<String, String>** | Arbitrary context for a request as key-value pairs. How to use the context is custom to the specific implementation.  REST NAMESPACE ONLY Context entries are passed via HTTP headers using the naming convention `x-lance-ctx-<key>: <value>`. For example, a context entry `{\"trace_id\": \"abc123\"}` would be sent as the header `x-lance-ctx-trace_id: abc123`.  |  [optional] |
-|**id** | **List<String>** |  |  [optional] |
-|**newColumns** | [**List<NewColumnTransform>**](NewColumnTransform.md) | List of new columns to add |  |
+|**newColumns** | [**List<AddColumnsEntry>**](AddColumnsEntry.md) | List of new columns to add to the table |  |
 
 
 

docs/src/client/operations/models/AlterTableAddColumnsResponse.md

@@ -7,8 +7,7 @@
 
 | Name | Type | Description | Notes |
 |------------ | ------------- | ------------- | -------------|
-|**transactionId** | **String** | Optional transaction identifier |  [optional] |
-|**version** | **Long** | Version of the table after adding columns |  |
+|**version** | **Long** | The commit version associated with the operation |  |
 
 
 

docs/src/client/operations/models/AlterTableAlterColumnsRequest.md

@@ -7,10 +7,7 @@
 
 | Name | Type | Description | Notes |
 |------------ | ------------- | ------------- | -------------|
-|**identity** | [**Identity**](Identity.md) |  |  [optional] |
-|**context** | **Map<String, String>** | Arbitrary context for a request as key-value pairs. How to use the context is custom to the specific implementation.  REST NAMESPACE ONLY Context entries are passed via HTTP headers using the naming convention `x-lance-ctx-<key>: <value>`. For example, a context entry `{\"trace_id\": \"abc123\"}` would be sent as the header `x-lance-ctx-trace_id: abc123`.  |  [optional] |
-|**id** | **List<String>** |  |  [optional] |
-|**alterations** | [**List<AlterColumnsEntry>**](AlterColumnsEntry.md) | List of column alterations to perform |  |
+|**alterations** | [**List<AlterColumnsEntry>**](AlterColumnsEntry.md) | List of column alterations to apply to the table |  |
 
 
 

docs/src/client/operations/models/AlterTableAlterColumnsResponse.md

@@ -7,8 +7,7 @@
 
 | Name | Type | Description | Notes |
 |------------ | ------------- | ------------- | -------------|
-|**transactionId** | **String** | Optional transaction identifier |  [optional] |
-|**version** | **Long** | Version of the table after altering columns |  |
+|**version** | **Long** | The commit version associated with the operation |  |
 
 
 

docs/src/client/operations/models/AlterTableBackfillColumnsRequest.md

@@ -0,0 +1,26 @@
+
+
+# AlterTableBackfillColumnsRequest
+
+
+## Properties
+
+| Name | Type | Description | Notes |
+|------------ | ------------- | ------------- | -------------|
+|**column** | **String** | Column name to backfill |  |
+|**where** | **String** | Optional WHERE clause filter |  [optional] |
+|**concurrency** | **Integer** | Optional concurrency override |  [optional] |
+|**intraApplierConcurrency** | **Integer** | Optional intra-applier concurrency override |  [optional] |
+|**minCheckpointSize** | **Integer** | Optional minimum checkpoint size |  [optional] |
+|**maxCheckpointSize** | **Integer** | Optional maximum checkpoint size |  [optional] |
+|**batchCheckpointFlushIntervalSeconds** | **BigDecimal** | Optional batch checkpoint flush interval in seconds |  [optional] |
+|**readVersion** | **Integer** | Optional table version to read from |  [optional] |
+|**taskSize** | **Integer** | Optional task size |  [optional] |
+|**numFrags** | **Integer** | Optional number of fragments |  [optional] |
+|**checkpointSize** | **Integer** | Optional checkpoint size |  [optional] |
+|**commitGranularity** | **Integer** | Optional commit granularity |  [optional] |
+|**cluster** | **String** | Optional cluster name |  [optional] |
+|**manifest** | **String** | Optional manifest name |  [optional] |
+
+
+

docs/src/client/operations/models/AlterTableBackfillColumnsResponse.md

@@ -0,0 +1,13 @@
+
+
+# AlterTableBackfillColumnsResponse
+
+
+## Properties
+
+| Name | Type | Description | Notes |
+|------------ | ------------- | ------------- | -------------|
+|**jobId** | **String** | The job ID for tracking the backfill job |  |
+
+
+