Skip to content

Bump the dependencies group with 2 updates #335

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
jnmt merged 2 commits into from
Dec 3, 2025
Merged

Bump the dependencies group with 2 updates #335

jnmt merged 2 commits into from
Dec 3, 2025
+2 −2

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Dec 1, 2025

Bumps the dependencies group with 2 updates: com.scalar-labs:scalardb and com.scalar-labs:scalardb-schema-loader.

Updates com.scalar-labs:scalardb from 3.16.1 to 3.17.0

Release notes

Sourced from com.scalar-labs:scalardb's releases.

v3.17.0

Summary

This release includes many enhancements, improvements, security issue fixes, and bug fixes.

Community edition

Enhancements

  • Added support for ifNotExists option in add column operation. (#2960)
  • Added support for dropping columns in ScalarDB. (#2983)
  • Added support for renaming columns in ScalarDB. (#2990)
  • Added support for renaming tables in ScalarDB. (#3021)
  • Added support for altering column types in ScalarDB. (#3028)
  • AlloyDB versions 15 and 16 are now supported as underlying storage by using the PostgreSQL JDBC driver. (#3029)
  • TiDB versions 6.5, 7.5, and 8.5 are now supported as underlying storage by using MySQL Connector/J JDBC driver. (#3001)
  • Added support for batch operations that perform multiple operations in the Transaction API. (#3082)
  • Added support for administrative operations over Azure Blob Storage. (#3104)
  • Added support for data manipulation operations over Azure Blob Storage. (#3124)
  • Added Amazon S3 adapter. (#3141)
  • Add integration tests for Cassandra 4 and 5. (#3143)
  • Added Google Cloud Storage adapter. (#3179)
  • Introduced virtual tables in the Storage abstraction layer. Virtual tables allow exposing a logical join of two source tables on their primary key, enabling related data stored in separate tables to be accessed as a single logical entity. (#3180)
  • Added isConsistentVirtualTableReadGuaranteed() method to the StorageInfo interface to indicate whether a storage guarantees consistent reads for virtual tables. (#3204)
  • Added transaction metadata decoupling support in Consensus Commit. This feature enables users to perform Consensus Commit ScalarDB transactions on pre-existing data without schema modifications or data migration. (#3207)

Improvements

  • When using Db2, the default data type used for ScalarDB BLOB column from Db2 is changed from VARBINARY(32672) to BLOB(2G) to allow storing data up to 2GB. This brings new limitations that a BLOB column can no longer be used as partition key, clustering key, secondary index or as an ordering column in a cross-partitions scan, .i.e. ScanAll, operation. (#3000)
  • When using Oracle, the default data type used for ScalarDB BLOB column from Oracle is changed from RAW(2000) to BLOB to allow storing data up to 2GB. This introduces new limitations: a BLOB column can no longer be used as a partition key, clustering key, secondary index, or a condition in a Get or Scan operation. (#3070)
  • When using the JDBC transaction manager, do not set the JDBC transaction isolation level to SERIALIZABLE when the configuration scalar.db.jdbc.isolation_level is not set. The default is now the default value set by the storage. (#3076)
  • Added Maven publishing support for the ScalarDB Data Loader CLI, enabling distribution as a Maven artifact. (#3120)

Bug fixes

  • Fixed a bug where a CommitException was thrown when committing a transaction, even though the transaction was actually committed. (#2826)
  • Fixed error handling for mutations in Cassandra. (#2827)
  • Fixed a bug where group commit did not work correctly with one-phase commit. (#2832)
  • Fixed --no-header option being ignored in data loader CSV exports (#2924)
  • Fixed an inconsistency where Get and Scan operations were prepared differently for transaction reads and Serializable validation, which could result in inconsistent ordering and cause Serializable validation failures. (#3113)
  • Exclude slf4j-api from alloydb dependency to correct logging behaviour (#3119)
  • Deprecated --log-success argument and introduced a new replacement option --enable-log-success (#3117)
  • Fixed incorrect validation causing maxThreads to be treated as required (#3128)
  • Prohibited Get and Scan operations using secondary indexes when the isolation level is SERIALIZABLE in the Consensus Commit transaction manager, as these operations are now defined as eventually consistent and cannot guarantee the strict consistency required by SERIALIZABLE isolation. (#3133)
  • Updated the import command help text to include default values for four CLI arguments. (#3059)
  • Fixed data-loader to properly handle unexpected exceptions during transaction processing for importing, ensuring transactions are aborted and errors are logged with proper context. (#3183)
  • Fixed failure log writing issue in storage mode for Data Loader imports (#3189)
  • Fixed handling of "null" values for non-TEXT columns in CSV imports (#3160)

Enterprise edition

Enhancements

ScalarDB Cluster

  • Added support for ifNotExists option in add column operation for ScalarDB Cluster.
  • Added support for dropping columns in ScalarDB Cluster.
  • Added support for renaming columns in ScalarDB Cluster.
  • Added support for renaming tables in ScalarDB Cluster.

... (truncated)

Commits
  • 861c596 Upgrade the version to 3.17.0
  • 64d9e0b Backport to branch(3) : Support transaction metadata decoupling in Consensus ...
  • e74a993 Backport to branch(3) : Bump software.amazon.awssdk:bom from 2.38.2 to 2.39.2...
  • 41cbc9f Bump actions/checkout from 5 to 6 in the actions-on-branch-3 group (#3215)
  • 900b873 Backport to branch(3) : Revisit handling IS_NULL conditions on right source t...
  • eb425fe Backport to branch(3) : Enable negative cache in VirtualTableInfoManager to i...
  • e15da2e Backport to branch(3) : Add isConsistentVirtualTableReadGuaranteed() to Stora...
  • f49ac40 Backport to branch(3) : Add Explicit \N NULL Marker for CSV Export/Import of ...
  • fabbd68 Backport to branch(3) : Replace ScalarDbMode with core TransactionMode for cl...
  • 6523424 Backport to branch(3) : Fix failure log writing issue in storage mode for Dat...
  • Additional commits viewable in compare view

Updates com.scalar-labs:scalardb-schema-loader from 3.16.1 to 3.17.0

Release notes

Sourced from com.scalar-labs:scalardb-schema-loader's releases.

v3.17.0

Summary

This release includes many enhancements, improvements, security issue fixes, and bug fixes.

Community edition

Enhancements

  • Added support for ifNotExists option in add column operation. (#2960)
  • Added support for dropping columns in ScalarDB. (#2983)
  • Added support for renaming columns in ScalarDB. (#2990)
  • Added support for renaming tables in ScalarDB. (#3021)
  • Added support for altering column types in ScalarDB. (#3028)
  • AlloyDB versions 15 and 16 are now supported as underlying storage by using the PostgreSQL JDBC driver. (#3029)
  • TiDB versions 6.5, 7.5, and 8.5 are now supported as underlying storage by using MySQL Connector/J JDBC driver. (#3001)
  • Added support for batch operations that perform multiple operations in the Transaction API. (#3082)
  • Added support for administrative operations over Azure Blob Storage. (#3104)
  • Added support for data manipulation operations over Azure Blob Storage. (#3124)
  • Added Amazon S3 adapter. (#3141)
  • Add integration tests for Cassandra 4 and 5. (#3143)
  • Added Google Cloud Storage adapter. (#3179)
  • Introduced virtual tables in the Storage abstraction layer. Virtual tables allow exposing a logical join of two source tables on their primary key, enabling related data stored in separate tables to be accessed as a single logical entity. (#3180)
  • Added isConsistentVirtualTableReadGuaranteed() method to the StorageInfo interface to indicate whether a storage guarantees consistent reads for virtual tables. (#3204)
  • Added transaction metadata decoupling support in Consensus Commit. This feature enables users to perform Consensus Commit ScalarDB transactions on pre-existing data without schema modifications or data migration. (#3207)

Improvements

  • When using Db2, the default data type used for ScalarDB BLOB column from Db2 is changed from VARBINARY(32672) to BLOB(2G) to allow storing data up to 2GB. This brings new limitations that a BLOB column can no longer be used as partition key, clustering key, secondary index or as an ordering column in a cross-partitions scan, .i.e. ScanAll, operation. (#3000)
  • When using Oracle, the default data type used for ScalarDB BLOB column from Oracle is changed from RAW(2000) to BLOB to allow storing data up to 2GB. This introduces new limitations: a BLOB column can no longer be used as a partition key, clustering key, secondary index, or a condition in a Get or Scan operation. (#3070)
  • When using the JDBC transaction manager, do not set the JDBC transaction isolation level to SERIALIZABLE when the configuration scalar.db.jdbc.isolation_level is not set. The default is now the default value set by the storage. (#3076)
  • Added Maven publishing support for the ScalarDB Data Loader CLI, enabling distribution as a Maven artifact. (#3120)

Bug fixes

  • Fixed a bug where a CommitException was thrown when committing a transaction, even though the transaction was actually committed. (#2826)
  • Fixed error handling for mutations in Cassandra. (#2827)
  • Fixed a bug where group commit did not work correctly with one-phase commit. (#2832)
  • Fixed --no-header option being ignored in data loader CSV exports (#2924)
  • Fixed an inconsistency where Get and Scan operations were prepared differently for transaction reads and Serializable validation, which could result in inconsistent ordering and cause Serializable validation failures. (#3113)
  • Exclude slf4j-api from alloydb dependency to correct logging behaviour (#3119)
  • Deprecated --log-success argument and introduced a new replacement option --enable-log-success (#3117)
  • Fixed incorrect validation causing maxThreads to be treated as required (#3128)
  • Prohibited Get and Scan operations using secondary indexes when the isolation level is SERIALIZABLE in the Consensus Commit transaction manager, as these operations are now defined as eventually consistent and cannot guarantee the strict consistency required by SERIALIZABLE isolation. (#3133)
  • Updated the import command help text to include default values for four CLI arguments. (#3059)
  • Fixed data-loader to properly handle unexpected exceptions during transaction processing for importing, ensuring transactions are aborted and errors are logged with proper context. (#3183)
  • Fixed failure log writing issue in storage mode for Data Loader imports (#3189)
  • Fixed handling of "null" values for non-TEXT columns in CSV imports (#3160)

Enterprise edition

Enhancements

ScalarDB Cluster

  • Added support for ifNotExists option in add column operation for ScalarDB Cluster.
  • Added support for dropping columns in ScalarDB Cluster.
  • Added support for renaming columns in ScalarDB Cluster.
  • Added support for renaming tables in ScalarDB Cluster.

... (truncated)

Commits
  • 861c596 Upgrade the version to 3.17.0
  • 64d9e0b Backport to branch(3) : Support transaction metadata decoupling in Consensus ...
  • e74a993 Backport to branch(3) : Bump software.amazon.awssdk:bom from 2.38.2 to 2.39.2...
  • 41cbc9f Bump actions/checkout from 5 to 6 in the actions-on-branch-3 group (#3215)
  • 900b873 Backport to branch(3) : Revisit handling IS_NULL conditions on right source t...
  • eb425fe Backport to branch(3) : Enable negative cache in VirtualTableInfoManager to i...
  • e15da2e Backport to branch(3) : Add isConsistentVirtualTableReadGuaranteed() to Stora...
  • f49ac40 Backport to branch(3) : Add Explicit \N NULL Marker for CSV Export/Import of ...
  • fabbd68 Backport to branch(3) : Replace ScalarDbMode with core TransactionMode for cl...
  • 6523424 Backport to branch(3) : Fix failure log writing issue in storage mode for Dat...
  • Additional commits viewable in compare view

Updates com.scalar-labs:scalardb-schema-loader from 3.16.1 to 3.17.0

Release notes

Sourced from com.scalar-labs:scalardb-schema-loader's releases.

v3.17.0

Summary

This release includes many enhancements, improvements, security issue fixes, and bug fixes.

Community edition

Enhancements

  • Added support for ifNotExists option in add column operation. (#2960)
  • Added support for dropping columns in ScalarDB. (#2983)
  • Added support for renaming columns in ScalarDB. (#2990)
  • Added support for renaming tables in ScalarDB. (#3021)
  • Added support for altering column types in ScalarDB. (#3028)
  • AlloyDB versions 15 and 16 are now supported as underlying storage by using the PostgreSQL JDBC driver. (#3029)
  • TiDB versions 6.5, 7.5, and 8.5 are now supported as underlying storage by using MySQL Connector/J JDBC driver. (#3001)
  • Added support for batch operations that perform multiple operations in the Transaction API. (#3082)
  • Added support for administrative operations over Azure Blob Storage. (#3104)
  • Added support for data manipulation operations over Azure Blob Storage. (#3124)
  • Added Amazon S3 adapter. (#3141)
  • Add integration tests for Cassandra 4 and 5. (#3143)
  • Added Google Cloud Storage adapter. (#3179)
  • Introduced virtual tables in the Storage abstraction layer. Virtual tables allow exposing a logical join of two source tables on their primary key, enabling related data stored in separate tables to be accessed as a single logical entity. (#3180)
  • Added isConsistentVirtualTableReadGuaranteed() method to the StorageInfo interface to indicate whether a storage guarantees consistent reads for virtual tables. (#3204)
  • Added transaction metadata decoupling support in Consensus Commit. This feature enables users to perform Consensus Commit ScalarDB transactions on pre-existing data without schema modifications or data migration. (#3207)

Improvements

  • When using Db2, the default data type used for ScalarDB BLOB column from Db2 is changed from VARBINARY(32672) to BLOB(2G) to allow storing data up to 2GB. This brings new limitations that a BLOB column can no longer be used as partition key, clustering key, secondary index or as an ordering column in a cross-partitions scan, .i.e. ScanAll, operation. (#3000)
  • When using Oracle, the default data type used for ScalarDB BLOB column from Oracle is changed from RAW(2000) to BLOB to allow storing data up to 2GB. This introduces new limitations: a BLOB column can no longer be used as a partition key, clustering key, secondary index, or a condition in a Get or Scan operation. (#3070)
  • When using the JDBC transaction manager, do not set the JDBC transaction isolation level to SERIALIZABLE when the configuration scalar.db.jdbc.isolation_level is not set. The default is now the default value set by the storage. (#3076)
  • Added Maven publishing support for the ScalarDB Data Loader CLI, enabling distribution as a Maven artifact. (#3120)

Bug fixes

  • Fixed a bug where a CommitException was thrown when committing a transaction, even though the transaction was actually committed. (#2826)
  • Fixed error handling for mutations in Cassandra. (#2827)
  • Fixed a bug where group commit did not work correctly with one-phase commit. (#2832)
  • Fixed --no-header option being ignored in data loader CSV exports (#2924)
  • Fixed an inconsistency where Get and Scan operations were prepared differently for transaction reads and Serializable validation, which could result in inconsistent ordering and cause Serializable validation failures. (#3113)
  • Exclude slf4j-api from alloydb dependency to correct logging behaviour (#3119)
  • Deprecated --log-success argument and introduced a new replacement option --enable-log-success (#3117)
  • Fixed incorrect validation causing maxThreads to be treated as required (#3128)
  • Prohibited Get and Scan operations using secondary indexes when the isolation level is SERIALIZABLE in the Consensus Commit transaction manager, as these operations are now defined as eventually consistent and cannot guarantee the strict consistency required by SERIALIZABLE isolation. (#3133)
  • Updated the import command help text to include default values for four CLI arguments. (#3059)
  • Fixed data-loader to properly handle unexpected exceptions during transaction processing for importing, ensuring transactions are aborted and errors are logged with proper context. (#3183)
  • Fixed failure log writing issue in storage mode for Data Loader imports (#3189)
  • Fixed handling of "null" values for non-TEXT columns in CSV imports (#3160)

Enterprise edition

Enhancements

ScalarDB Cluster

  • Added support for ifNotExists option in add column operation for ScalarDB Cluster.
  • Added support for dropping columns in ScalarDB Cluster.
  • Added support for renaming columns in ScalarDB Cluster.
  • Added support for renaming tables in ScalarDB Cluster.

... (truncated)

Commits
  • 861c596 Upgrade the version to 3.17.0
  • 64d9e0b Backport to branch(3) : Support transaction metadata decoupling in Consensus ...
  • e74a993 Backport to branch(3) : Bump software.amazon.awssdk:bom from 2.38.2 to 2.39.2...
  • 41cbc9f Bump actions/checkout from 5 to 6 in the actions-on-branch-3 group (#3215)
  • 900b873 Backport to branch(3) : Revisit handling IS_NULL conditions on right source t...
  • eb425fe Backport to branch(3) : Enable negative cache in VirtualTableInfoManager to i...
  • e15da2e Backport to branch(3) : Add isConsistentVirtualTableReadGuaranteed() to Stora...
  • f49ac40 Backport to branch(3) : Add Explicit \N NULL Marker for CSV Export/Import of ...
  • fabbd68 Backport to branch(3) : Replace ScalarDbMode with core TransactionMode for cl...
  • 6523424 Backport to branch(3) : Fix failure log writing issue in storage mode for Dat...
  • Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

@dependabot
Bump the dependencies group with 2 updates
d24485b 
Bumps the dependencies group with 2 updates: [com.scalar-labs:scalardb](https://github.com/scalar-labs/scalardb) and [com.scalar-labs:scalardb-schema-loader](https://github.com/scalar-labs/scalardb).


Updates `com.scalar-labs:scalardb` from 3.16.1 to 3.17.0
- [Release notes](https://github.com/scalar-labs/scalardb/releases)
- [Commits](scalar-labs/scalardb@v3.16.1...v3.17.0)

Updates `com.scalar-labs:scalardb-schema-loader` from 3.16.1 to 3.17.0
- [Release notes](https://github.com/scalar-labs/scalardb/releases)
- [Commits](scalar-labs/scalardb@v3.16.1...v3.17.0)

Updates `com.scalar-labs:scalardb-schema-loader` from 3.16.1 to 3.17.0
- [Release notes](https://github.com/scalar-labs/scalardb/releases)
- [Commits](scalar-labs/scalardb@v3.16.1...v3.17.0)

---
updated-dependencies:
- dependency-name: com.scalar-labs:scalardb
  dependency-version: 3.17.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: dependencies
- dependency-name: com.scalar-labs:scalardb-schema-loader
  dependency-version: 3.17.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: dependencies
- dependency-name: com.scalar-labs:scalardb-schema-loader
  dependency-version: 3.17.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: dependencies
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies java Pull requests that update Java code labels Dec 1, 2025
@feeblefakie feeblefakie requested review from a team, choplin, feeblefakie and jnmt and removed request for a team December 1, 2025 04:41
choplin
choplin approved these changes Dec 2, 2025
View reviewed changes
Copy link

@choplin choplin left a comment

Choose a reason for hiding this comment

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

The same here https://github.com/scalar-labs/scalardl-enterprise/pull/1527#pullrequestreview-3528006508

@jnmt jnmt added improvement and removed java Pull requests that update Java code labels Dec 3, 2025
@jnmt
Copy link
Collaborator

jnmt commented Dec 3, 2025

Note: I slightly changed the test code to follow the message format change in the new ScalarDB version.

@jnmt jnmt merged commit 7989f4a into master Dec 3, 2025
10 checks passed
@dependabot dependabot bot deleted the dependabot/gradle/dependencies-c6009526f8 branch December 3, 2025 02:40
feeblefakie pushed a commit that referenced this pull request Dec 3, 2025
@dependabot @jnmt
Bump the dependencies group with 2 updates (#335)
984ef42 
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Jun Nemoto <jun.nemoto@gmail.com>
@feeblefakie feeblefakie mentioned this pull request Dec 3, 2025
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@choplin choplin choplin approved these changes

@jnmt jnmt jnmt approved these changes

@feeblefakie feeblefakie Awaiting requested review from feeblefakie feeblefakie was automatically assigned from scalar-labs/scalardl

Assignees

No one assigned

Labels

dependencies improvement

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@jnmt @choplin