Bump fdb-record-layer-core-pb3 from 3.1.256.0 to 3.3.302.0

[dependabot[bot]]

Bumps fdb-record-layer-core-pb3 from 3.1.256.0 to 3.3.302.0.

Changelog

Sourced from fdb-record-layer-core-pb3's changelog.

3.3.302.0

• Bug fix ensure that partial records are created as proper protobuf messages [(Issue #1893)](FoundationDB/fdb-record-layer#1893)

3.3.301.0

• Bug fix Account for FDBStoreTimer.Counts.BYTES_READ in remote fetch [(Issue #1889)](FoundationDB/fdb-record-layer#1889)
• Bug fix The RecordQueryPlanner now chooses more efficient indexes for and-queries with one-of-them predicates on repeated nested fields [(Issue #1876)](FoundationDB/fdb-record-layer#1876)
• Performance Single record deletes can now be configured to be executed as multiple single-key clears instead of one range clear, which should be an improvement for LSM-based FDB storage engines [(Issue #1493)](FoundationDB/fdb-record-layer#1493)

3.3.300.0

3.3.298.0

• Feature Add a method to construct a single record from a raw indexed record [(Issue #1865)](FoundationDB/fdb-record-layer#1865)
• Feature Joined record types now allow some kinds of function key expressions in their join conditions [(Issue #1872)](FoundationDB/fdb-record-layer#1872)
• Feature Allow users to name enum types in TypeRepository [(Issue #1847)](FoundationDB/fdb-record-layer#1847)
• Feature Support planning of (covering) index scans, fetches over synthetic record types [(Issue #1886)](FoundationDB/fdb-record-layer#1886)

3.3.297.0

• Bug fix TimeWindowLeaderboardWindowUpdate rebuild = NEVER is not honored for new directory [(Issue #1878)](FoundationDB/fdb-record-layer#1878)

3.3.296.0

• Performance Looking up logical values from DirectoryLayerDirectorys no longer needs to create new transactions [(Issue #1857)](FoundationDB/fdb-record-layer#1857)

3.3.295.0

• Breaking change Enable incremental builds. Upgrade guava dependency to 31.1-jre. [(Issue #1868)](FoundationDB/fdb-record-layer#1868)

3.2

Features

This version of the Record Layer allows the FDB API version to be configured through the FDBDatabaseFactory. This means that while this version allows the client to be configured to use 7.1 features, it also supports connecting to 6.3 FDB clusters if the API version is set appropriately. Note that setting the API version does restrict the set of potential FDB server versions that can be connected to, so this configuration change should only be made if the FDB server has already been updated.

New index state "READABLE_UNIQUE_PENDING" - the proper way to roll this feature out is:

1. The adopter should upgrade to the new Record Layer version and deploy the version everywhere.
2. The format version should be set READABLE_UNIQUE_PENDING_FORMAT_VERSION.
3. Only after all the possible clients are upgraded to support the new state, the adopter may set the allowPendingState on the indexing policy of new index builds. An index may be in this new state if it is fully built, the unique flag is set, and duplications were found during online indexing. From the code point of view, it is defined as scannable but not readable.

Breaking Changes

The FoundationDB Java binding dependency has been updated to 7.1 with this release. This means that clients also need to update their main FDB C client to a 7.1 version. Adopters that still wish to connect to an FDB cluster running a 6.3 or 7.0 server version can do so by packaging additional FDB C clients at the appropriate version(s) using the FDB multi-version client feature.

This release also updates downstream dependency versions. Most notably, the proto3 artifacts now require Protobuf version 3.20.1.

... (truncated)

Commits

• 148fc53 Release notes updated for version 3.3.302.0
• 1feebf1 Merge pull request #1892 from normen662/main
• bfae15d add copiers for required fields for covering index scans
• 184aa81 Release notes updated for version 3.3.301.0
• 5b9c96c Resolves #1493: Consider replacing single record range deletes with multiple ...
• 0bc29ce Merge pull request #1877 from alecgrieser/01876-andwiththen-with-oneofthemwit...
• b6a6e03 Merge pull request #1890 from ohadzeliger/count-bytes-read
• b9115a1 fix up test with merge skew from fa5bc182fb
• 776afaa Fixes #1876: AndWithThenPlanner does not handle OneOfThemWithComponent expres...
• f2ab83e Style
• 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 ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)