Skip to content

Conversation

@beryllw
Copy link
Contributor

@beryllw beryllw commented Dec 12, 2025

Purpose

Linked issue: close #2111

Brief change log

Tests

API and Format

Documentation

@beryllw beryllw marked this pull request as draft December 12, 2025 08:14
@beryllw beryllw force-pushed the auto-inc-impl branch 2 times, most recently from 45dc38a to 4d674d7 Compare December 12, 2025 15:04
@vamossagar12
Copy link
Contributor

hi, I had created this Pr: #2119 for this issue. Do we want to prefer this one over that?

@xx789633
Copy link
Contributor

Hi @vamossagar12 , we prefer this one to work on since it is more comprehensive.

@beryllw beryllw marked this pull request as ready for review December 24, 2025 06:03
@beryllw beryllw requested a review from xx789633 December 24, 2025 06:10
new Column(
column.getName(),
column.getDataType().copy(false),
column.getDataType().copy(true),
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Partial update is required, so the data type here needs to be temporarily set to nullable.

@beryllw beryllw changed the title [kv]: Add an implementation of AutoIncIDBuffer [kv] Add an implementation of AutoIncIDBuffer Dec 25, 2025
@beryllw beryllw requested a review from xx789633 December 25, 2025 03:16
@beryllw beryllw requested a review from xx789633 December 26, 2025 01:13
Copy link
Contributor

@platinumhamburg platinumhamburg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@beryllw Thanks for contribution, I left some comments.

*
* <p>/metadata/databases/[databaseName]/tables/[tableName]/auto_inc/col_[columnIdx]
*/
public static final class AutoIncrementColumnZNode {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Schema evolution (adding a column) is already supported; It would be better to use column IDs instead of column indices here.

if (incrementValue.succeeded()) {
return incrementValue.preValue();
} else {
throw new Exception("Failed to add sequence id counter.");
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps we could make the exception information clearer—for example, by including the sequenceIDPath.

int schemaId,
Configuration properties,
TableConfig tableConf,
Schema schema,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Use SchemaGetter instead of Schema.

TableConfig tableConf,
Schema schema,
ZooKeeperClient zkClient) {
int[] autoIncColumnIndexes = schema.getAutoIncColumnIndexes();
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Use column IDs instead of column indices.


/**
* Return row value.
* Returns the next auto increment column ID.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Consider renaming this method, as "column ID" is misleading and conflicts with the actual ID of a Column object, which can cause confusion. Moreover, while UID is one use case for auto-increment columns, it does not encompass all possible scenarios, so naming it with "ID" is not advisable.

this.current = start;
}

public long remaining() {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This part is a bit confusing to me—the outer check already handles negative values, so the Math.max here seems like an unnecessary overhead.

}

@Test
void testPutAutoIncColumnAndLookup() throws Exception {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To achieve more precise test assertions, I recommend explicitly creating a single-bucket table, writing multiple batches of data—some with duplicate primary keys and others with distinct primary keys—and then verifying that the auto-increment column behaves correctly.

.longType()
.defaultValue(100000L)
.withDescription(
"The batch size of auto-increment IDs fetched from the distributed counter each time. This value determines the length of the ID segment cached locally. Default: 100000.");
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

New configuration options should be documented, including recommended values and a description of the behavioral impact associated with different settings.

throws Exception {
walBuilder.append(ChangeType.INSERT, latestSchemaRow.replaceRow(currentValue.row));
kvPreWriteBuffer.put(key, currentValue.encodeValue(), logOffset);
BinaryValue newValue = autoIncProcessor.processAutoInc(currentValue);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've been wondering about the relationship between auto-increment column handling and the Merge Engine. I think they should probably be integrated in the design to avoid redundant encoding of row data, which would otherwise lead to significant performance overhead.

@platinumhamburg
Copy link
Contributor

In addition to integration tests, I think we should also add several unit tests in KvTabletTest to cover behavior assertions after a TabletServer restart and after a single segment overflows.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[kv/auto increment column] Implement AutoIncIDBuffer on tablet server

4 participants