SK-3061: revert fields→tokens rename, restore data field on bulkInsert response

[Devesh-Skyflow]

Summary

Fixes the deviations from the FlowVault API contract flagged in this Slack thread, plus a documentation/samples cleanup pass that grew out of it.

⚠️ Breaking change (item 6), already regenerated: InsertResponseRecord/BulkInsertResponseRecord's deprecated constructors and getFields() had their tokens generics change. The japicmp baseline (flowvault/api-report/skyflow-flowvault-java.baseline.jar) has been regenerated via scripts/contract-snapshot-update.sh flowvault and is included in this PR — mvn -pl common,flowvault -am verify passes clean against it (confirmed locally once a JDK/Maven became available partway through review; see item 6 and the Testing section for the full picture, including which parts of this turned out to be avoidable and were declined on purpose).

1. Response contract fix

1. fields → tokens: the SDK had renamed the API's tokens response key to fields, so callers needed getFields() instead of the API-matching getTokens(). Reverted the rename; getFields() stays as a @Deprecated alias that logs a warning and delegates to getTokens() — existing callers keep working unchanged, detokenize/deleteTokens untouched throughout.
2. data field restored: the API's data field was silently dropped from the bulk insert response. It's wired back through from V1RecordResponseObject.getData(), which already carried it — nothing in Utils.formatBulkInsertResponse was reading it.

Compatibility note: flowvault/pom.xml runs a japicmp binary/source-compatibility check against flowvault/api-report/*.baseline.jar for com.skyflow.vault.data. Rather than changing the existing InsertResponseRecord/BulkInsertResponseRecord constructor signatures (a breaking change under that gate), the old (data-less) constructor overloads are kept as @Deprecated pass-throughs, and data is added via new overloads. No baseline regeneration should be required.

2. flowvault/README.md accuracy pass

Went through the README against the actual source rather than just fixing the two items above:

• Version snippets said 1.0.0; pom.xml is 1.0.1.
• CustomHeaderKey sample used names (SkyflowAccountId, etc.) that don't exist — the real enum is SKYFLOW_ACCOUNT_ID/SKYFLOW_ACCOUNT_NAME/REQUEST_ID_HEADER. The README's own code block didn't compile.
• "vault() takes no arguments, use one client per vault" was false — vault(String vaultId) exists and is tested for multi-vault use on one client. Documented it.
• "updateType accepts UPDATE (the default)" overstated the SDK's behavior — it omits the field when unset rather than sending "UPDATE" itself; reworded.
• getHttpStatus() example used "BAD_REQUEST"; the actual hardcoded validation-error string is "Bad Request".
• Bulk Insert tokens JSON example showed a flat string per column; the real shape is always a list of {token, tokenGroupName} entries per column (one per token group), per a dedicated regression test (testBulkInsert_successWithListOfMapsTokenShape). Fixed the example and added a snippet showing how to read it (there's no typed accessor yet — same gap raised in the Slack thread).
• Added a "Schema vs. schemaless vaults" table (bulkInsert = structured, bulkTokenize/bulkDeleteTokens = schemaless, bulkDetokenize = both) — flagged in the thread as a known doc gap, confirmed against git history (SK-2646, which shipped tokenize/delete-tokens specifically as "Schemaless vault apis") since there's no code-level enforcement of it. Repeated as a one-line note on each of the four operation sections so it's visible without reading top-to-bottom.
• Bulk Detokenize metadata JSON example initially backed out a claim about its typical content (only skyflowId was grounded in code; tableName was just a Javadoc description with nothing behind it), then re-grounded it against flowdb_dp_apis.proto's own literal example value for the field, {"table": "table1", "skyflowID": "4524524534623"} — stronger evidence than the description text, which is itself misleading (it says "tableName", the actual wire key is table; Utils.java only renames skyflowID→skyflowId, table passes through unrenamed). Updated the JSON example to match.

3. Samples cleanup (flowvault/samples/)

• Deleted BearerTokenExpiryExample.java — despite its name, it never touches BearerToken/Token.isExpired(); it's a generic "retry once on 401" wrapper, redundant with BearerTokenGenerationExample's real expiry pattern and the README's own retry guidance.
• Rewrote samples/README.md — it referenced DetokenizeExample.java, InsertExample.java, GetByIdExample.java, etc., none of which exist in this module (stale boilerplate from a different layout). Replaced with an accurate index of the real samples and correct Maven run instructions.
• Added response iteration (summary + per-record/per-token walk + retry) to BulkInsertSync/Async, BulkMultiTableInsertSync/Async, BulkDetokenizeSync/Async, and CustomHeaderExample — these previously only did System.out.println(response). BulkTokenizeSync/Async and BulkDeleteTokensSync/Async already had this pattern.

4. Testing

• Updated ResponseComponentTests, BulkResponseTests, UtilsTests, VaultControllerTests for the rename/restore, including a dedicated test for the deprecated constructor + getFields() alias.
• Codecov flagged 2 uncovered lines in InsertResponseRecord.java (its own deprecated constructor — never exercised directly, since BulkInsertResponseRecord's deprecated constructor bypasses it). Added a direct test for it.
• Actually verified, not just written: a JDK/Maven became available partway through this PR's review (none were available in the sandbox this branch was authored in until then). mvn -pl common,flowvault -am test → 692 tests, 0 failures. mvn -pl common,flowvault -am verify (full reactor, japicmp included) → BUILD SUCCESS against the regenerated baseline from item 6.
  • One unrelated pre-existing failure surfaced along the way and had to be excluded to get a clean run: common's TokenTests.testExpiredTokenForIsExpiredToken reads a TEST_EXPIRED_TOKEN value from a .env file that isn't committed to the repo (a CI-only secret) — nothing to do with this PR, com.skyflow.serviceaccount.util.Token is a pre-existing, unrelated class (JWT expiry check) that this PR never touches.

5. Bug fix: Skyflow.getVaultConfig() crashed on an empty vault list

Found while double-checking the vault()/vault(String) claim above — a different, unrelated method with a real bug:

public VaultConfig getVaultConfig() {
    Object[] array = this.builder.vaultConfigMap.values().toArray();
    return (VaultConfig) array[0];   // unguarded — throws ArrayIndexOutOfBoundsException if empty
}

build() never validates that at least one vault was registered, so a client built with zero addVaultConfig(...) calls is a valid, reachable state — and calling getVaultConfig() on one crashed with an unchecked ArrayIndexOutOfBoundsException rather than failing predictably. Traced every call site in the codebase first: all of them are on VaultController (a different, already-safe method with the same name — it just returns its own single stored config, no lookup involved), never on Skyflow directly. So this had zero usages and zero test coverage anywhere in the suite.

Fixed by mirroring the sibling method's already-correct convention — BaseSkyflow.getVaultConfig(String) is a plain map.get(vaultId) that returns null when absent, no exception, no signature change:

public VaultConfig getVaultConfig() {
    return this.builder.vaultConfigMap.values().stream().findFirst().orElse(null);
}

Deliberately did not make it throw SkyflowException like vault()/vault(String) do — that would diverge from its own sibling method's contract and require adding a checked exception to the signature, a source-incompatible change under this module's japicmp gate, for no real benefit. This fix is implementation-only (same signature), so no baseline update needed. Added 7 tests in SkyflowTests covering the regression case plus the existing untested gaps on the by-id overload.

6. InsertResponseRecord.getTokens() is now typed (Map<String, List<Token>>)

The generic tokens: Map<String, Object> (item 2 above) still required casting/iterating by hand to reach token/tokenGroupName — the exact usability complaint in the Slack thread. First pass at fixing this added a separate typed accessor (getTokenDetails()) alongside the untouched generic getTokens(), keeping both per the thread's "generic for flexibility, typed for UX" clarification. Per explicit direction, went further: getTokens() itself is now the typed one — Map<String, List<Token>> — matching the shape this field had before insert was reworked (flowvault's own pre-rework "v3" Success.tokens was Map<String, List<Token>>; getTokenDetails() no longer exists).

This is the one genuinely breaking change in this PR — confirmed against the actual japicmp diff once a JDK/Maven became available (not just reasoned about in the abstract):

• getTokens() itself was never breaking. It's reported as a brand-new method against the committed baseline — the pre-SK-3061 codebase only ever had getFields(), so any shape getTokens() returns is additive. My initial writeup here overstated this, assuming a same-arity generic-erasure conflict that doesn't actually apply to a method with zero parameters (erasure conflicts are a parameter-list problem, not a return-type one — a method can't be overloaded by return type at all, regardless of arity, so this was never really in question).
• What is flagged, all under com.skyflow.vault.data: InsertResponseRecord's deprecated 6-arg constructor and BulkInsertResponseRecord's deprecated 8-arg constructor (both had their tokens parameter generics change), and getFields() (return type generics changed, since it just delegates to getTokens()).
• These three were avoidable with modest extra code — the deprecated constructors are a different arity than the primary ones, so nothing forces their parameter type to change; getFields() could reverse-map back to the original shape instead of delegating directly. Flagged this and asked; declined in favor of just regenerating the baseline (see the warning banner above and the regenerated flowvault/api-report/skyflow-flowvault-java.baseline.jar in this PR).
• This also reverses the "keep contract exactly like API" decision made earlier in this same thread — the API's own wire contract types a column's tokens as generic Object. Accepted as the tradeoff for matching the requested typed shape.

Token (getToken()/getTokenGroupName()) isn't a new invention — it's a straight reintroduction of a class flowvault itself had before insert was reworked (deleted in 685a82ff), with final fields and a toString() added to match TokenizeResponseToken's established convention in this package.

The actual parsing (a column's raw wire value can be a list of {token, tokenGroupName} entries, a single such entry, or a bare value) now lives in a new static utility, Token.parseTokens(Map<String, Object>), called once by Utils.formatBulkInsertResponse when constructing each record — not recomputed on every getTokens() call like the first pass's getTokenDetails() was.

Found and fixed a real landmine while adding the Token class: ResponseComponentTests.java had a dangling {@link Token} Javadoc reference left over from the class's original removal, which would have silently started resolving to this new class (while the surrounding comment still said Token "was removed") had I not updated it.

Updated every test that constructed a record with a raw Map<String,Object> tokens value or asserted on the old generic return type, BulkInsertSync/Async, BulkMultiTableInsertSync/Async, and CustomHeaderExample to use getTokens() directly (matching BulkTokenizeSync.java's existing typed per-token loop), and closed every branch in the new parsing logic with tests (a per-column null value, a null element inside a token-group list, a Map entry missing one of its two expected keys). VaultControllerTests.testBulkInsert_successWithListOfMapsTokenShape simplified nicely as a result — no more manual casting needed to assert on it.

Also updated outside this repo

The FlowVault 1.0.0 migration Confluence doc (linked from the Slack thread) has been corrected to match the response-contract change and flags the Object-typing gap (now closed by item 6, but the doc itself is unchanged since this PR).

Not in this PR (flagged as follow-ups)

• A CI safeguard test to catch future wire-type fields silently going unread (the same failure mode data had here).

🤖 Generated with Claude Code

[codecov]

Codecov Report

❌ Patch coverage is 96.66667% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 91.36%. Comparing base (1145b80) to head (f326ec2).

Files with missing lines	Patch %	Lines
...lt/src/main/java/com/skyflow/vault/data/Token.java	94.87%	0 Missing and 2 partials ⚠️

Additional details and impacted files

@@                       Coverage Diff                       @@
##             flowvault-release/26.8.13     #408      +/-   ##
===============================================================
+ Coverage                        91.30%   91.36%   +0.06%     
- Complexity                           0      475     +475     
===============================================================
  Files                              157      158       +1     
  Lines                             6392     6440      +48     
  Branches                           850      859       +9     
===============================================================
+ Hits                              5836     5884      +48     
+ Misses                             364      362       -2     
- Partials                           192      194       +2     

Flag	Coverage Δ
common	88.39% <100.00%> (+<0.01%)	⬆️
flowvault	88.88% <96.55%> (+0.23%)	⬆️
skyvault	94.72% <ø> (ø)
unittests-flowvault	89.85% <96.22%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
Module: common	88.39% <100.00%> (+<0.01%)	⬆️
Module: skyvault	94.72% <ø> (ø)
Module: flowvault	88.88% <96.55%> (+0.23%)	⬆️
Service Account	86.69% <ø> (ø)
Vault Data	91.66% <96.07%> (+0.23%)	⬆️
Vault Tokens	99.03% <ø> (ø)
Vault Connection	100.00% <ø> (ø)
Vault Controller	85.31% <ø> (ø)
Detect	100.00% <ø> (ø)
Audit	100.00% <ø> (ø)
BIN Lookup	100.00% <ø> (ø)
Config	96.26% <ø> (ø)
Utils	89.22% <100.00%> (+<0.01%)	⬆️
Errors	100.00% <ø> (ø)
Enums	100.00% <ø> (ø)
Logs	95.34% <100.00%> (+0.01%)	⬆️

Files with missing lines	Coverage Δ
...ommon/src/main/java/com/skyflow/logs/InfoLogs.java	100.00% <100.00%> (ø)
flowvault/src/main/java/com/skyflow/Skyflow.java	93.68% <100.00%> (+2.01%)	⬆️
...owvault/src/main/java/com/skyflow/utils/Utils.java	87.58% <100.00%> (+0.02%)	⬆️
...m/skyflow/vault/data/BulkInsertResponseRecord.java	100.00% <100.00%> (ø)
...a/com/skyflow/vault/data/InsertResponseRecord.java	100.00% <100.00%> (ø)
...lt/src/main/java/com/skyflow/vault/data/Token.java	94.87% <94.87%> (ø)

---

Continue to review full report in Codecov by Harness.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1145b80...f326ec2. Read the comment docs.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[github-actions]

Contract baseline change detected (flowvault)

This PR updates flowvault/api-report/skyflow-flowvault-java.baseline.jar (the approved public API contract). Here is exactly what it changes, comparing the baseline on flowvault-release/26.8.13 against the baseline committed in this PR:

Compatibility Report

Summary

Warning

Compatible changes found while checking backward compatibility of version skyflow-flowvault-java.baseline with the previous version old-baseline.

Expand to see options used.

• Report only summary: No
• Report only changes: Yes
• Report only binary-incompatible changes: No
• Access modifier filter: PROTECTED
• Old archives:
  • 
• New archives:
  • 
• Evaluate annotations: Yes
• Include synthetic classes and class members: No
• Include specific elements: Yes
  • com.skyflow.Skyflow
  • com.skyflow.config
  • com.skyflow.enums
  • com.skyflow.errors
  • com.skyflow.serviceaccount.util
  • com.skyflow.vault.audit
  • com.skyflow.vault.bin
  • com.skyflow.vault.connection
  • com.skyflow.vault.controller
  • com.skyflow.vault.data
  • com.skyflow.vault.detect
  • com.skyflow.vault.tokens
• Exclude specific elements: No
• Ignore all missing classes: Yes
• Ignore specific missing classes: No
• Treat changes as errors:
  • Any changes: No
  • Binary incompatible changes: No
  • Source incompatible changes: No
  • Incompatible changes caused by excluded classes: Yes
  • Semantically incompatible changes: No
  • Semantically incompatible changes, including development versions: No
• Classpath mode: TWO_SEPARATE_CLASSPATHS
• Old classpath:

/home/runner/.m2/repository/com/skyflow/common/1.0.0/common-1.0.0.jar:/home/runner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.17.2/jackson-databind-2.17.2.jar:/home/runner/.m2/repository/com/fasterxml/jackson/core/jackson-annotations/2.17.2/jackson-annotations-2.17.2.jar:/home/runner/.m2/repository/com/fasterxml/jackson/core/jackson-core/2.17.2/jackson-core-2.17.2.jar:/home/runner/.m2/repository/com/fasterxml/jackson/datatype/jackson-datatype-jdk8/2.18.6/jackson-datatype-jdk8-2.18.6.jar:/home/runner/.m2/repository/com/fasterxml/jackson/datatype/jackson-datatype-jsr310/2.18.6/jackson-datatype-jsr310-2.18.6.jar:/home/runner/.m2/repository/io/github/cdimascio/dotenv-java/2.2.0/dotenv-java-2.2.0.jar:/home/runner/.m2/repository/com/google/code/gson/gson/2.10.1/gson-2.10.1.jar:/home/runner/.m2/repository/com/squareup/okhttp3/okhttp/4.12.0/okhttp-4.12.0.jar:/home/runner/.m2/repository/com/squareup/okio/okio/3.6.0/okio-3.6.0.jar:/home/runner/.m2/repository/com/squareup/okio/okio-jvm/3.6.0/okio-jvm-3.6.0.jar:/home/runner/.m2/repository/org/jetbrains/kotlin/kotlin-stdlib-common/1.9.10/kotlin-stdlib-common-1.9.10.jar:/home/runner/.m2/repository/org/jetbrains/kotlin/kotlin-stdlib-jdk8/1.8.21/kotlin-stdlib-jdk8-1.8.21.jar:/home/runner/.m2/repository/org/jetbrains/kotlin/kotlin-stdlib/1.8.21/kotlin-stdlib-1.8.21.jar:/home/runner/.m2/repository/org/jetbrains/annotations/13.0/annotations-13.0.jar:/home/runner/.m2/repository/org/jetbrains/kotlin/kotlin-stdlib-jdk7/1.8.21/kotlin-stdlib-jdk7-1.8.21.jar:/home/runner/.m2/repository/io/jsonwebtoken/jjwt/0.12.6/jjwt-0.12.6.jar:/home/runner/.m2/repository/io/jsonwebtoken/jjwt-api/0.12.6/jjwt-api-0.12.6.jar:/home/runner/.m2/repository/io/jsonwebtoken/jjwt-impl/0.12.6/jjwt-impl-0.12.6.jar:/home/runner/.m2/repository/io/jsonwebtoken/jjwt-jackson/0.12.6/jjwt-jackson-0.12.6.jar:/home/runner/.m2/repository/junit/junit/4.13.2/junit-4.13.2.jar:/home/runner/.m2/repository/org/hamcrest/hamcrest-core/1.3/hamcrest-core-1.3.jar:/home/runner/.m2/repository/org/powermock/powermock-module-junit4/2.0.9/powermock-module-junit4-2.0.9.jar:/home/runner/.m2/repository/org/powermock/powermock-module-junit4-common/2.0.9/powermock-module-junit4-common-2.0.9.jar:/home/runner/.m2/repository/org/powermock/powermock-reflect/2.0.9/powermock-reflect-2.0.9.jar:/home/runner/.m2/repository/net/bytebuddy/byte-buddy/1.10.14/byte-buddy-1.10.14.jar:/home/runner/.m2/repository/net/bytebuddy/byte-buddy-agent/1.10.14/byte-buddy-agent-1.10.14.jar:/home/runner/.m2/repository/org/powermock/powermock-core/2.0.9/powermock-core-2.0.9.jar:/home/runner/.m2/repository/org/javassist/javassist/3.27.0-GA/javassist-3.27.0-GA.jar:/home/runner/.m2/repository/org/powermock/powermock-api-mockito2/2.0.9/powermock-api-mockito2-2.0.9.jar:/home/runner/.m2/repository/org/powermock/powermock-api-support/2.0.9/powermock-api-support-2.0.9.jar:/home/runner/.m2/repository/org/mockito/mockito-core/3.3.3/mockito-core-3.3.3.jar:/home/runner/.m2/repository/org/objenesis/objenesis/2.6/objenesis-2.6.jar

• New classpath:

/home/runner/.m2/repository/com/skyflow/common/1.0.0/common-1.0.0.jar:/home/runner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.17.2/jackson-databind-2.17.2.jar:/home/runner/.m2/repository/com/fasterxml/jackson/core/jackson-annotations/2.17.2/jackson-annotations-2.17.2.jar:/home/runner/.m2/repository/com/fasterxml/jackson/core/jackson-core/2.17.2/jackson-core-2.17.2.jar:/home/runner/.m2/repository/com/fasterxml/jackson/datatype/jackson-datatype-jdk8/2.18.6/jackson-datatype-jdk8-2.18.6.jar:/home/runner/.m2/repository/com/fasterxml/jackson/datatype/jackson-datatype-jsr310/2.18.6/jackson-datatype-jsr310-2.18.6.jar:/home/runner/.m2/repository/io/github/cdimascio/dotenv-java/2.2.0/dotenv-java-2.2.0.jar:/home/runner/.m2/repository/com/google/code/gson/gson/2.10.1/gson-2.10.1.jar:/home/runner/.m2/repository/com/squareup/okhttp3/okhttp/4.12.0/okhttp-4.12.0.jar:/home/runner/.m2/repository/com/squareup/okio/okio/3.6.0/okio-3.6.0.jar:/home/runner/.m2/repository/com/squareup/okio/okio-jvm/3.6.0/okio-jvm-3.6.0.jar:/home/runner/.m2/repository/org/jetbrains/kotlin/kotlin-stdlib-common/1.9.10/kotlin-stdlib-common-1.9.10.jar:/home/runner/.m2/repository/org/jetbrains/kotlin/kotlin-stdlib-jdk8/1.8.21/kotlin-stdlib-jdk8-1.8.21.jar:/home/runner/.m2/repository/org/jetbrains/kotlin/kotlin-stdlib/1.8.21/kotlin-stdlib-1.8.21.jar:/home/runner/.m2/repository/org/jetbrains/annotations/13.0/annotations-13.0.jar:/home/runner/.m2/repository/org/jetbrains/kotlin/kotlin-stdlib-jdk7/1.8.21/kotlin-stdlib-jdk7-1.8.21.jar:/home/runner/.m2/repository/io/jsonwebtoken/jjwt/0.12.6/jjwt-0.12.6.jar:/home/runner/.m2/repository/io/jsonwebtoken/jjwt-api/0.12.6/jjwt-api-0.12.6.jar:/home/runner/.m2/repository/io/jsonwebtoken/jjwt-impl/0.12.6/jjwt-impl-0.12.6.jar:/home/runner/.m2/repository/io/jsonwebtoken/jjwt-jackson/0.12.6/jjwt-jackson-0.12.6.jar:/home/runner/.m2/repository/junit/junit/4.13.2/junit-4.13.2.jar:/home/runner/.m2/repository/org/hamcrest/hamcrest-core/1.3/hamcrest-core-1.3.jar:/home/runner/.m2/repository/org/powermock/powermock-module-junit4/2.0.9/powermock-module-junit4-2.0.9.jar:/home/runner/.m2/repository/org/powermock/powermock-module-junit4-common/2.0.9/powermock-module-junit4-common-2.0.9.jar:/home/runner/.m2/repository/org/powermock/powermock-reflect/2.0.9/powermock-reflect-2.0.9.jar:/home/runner/.m2/repository/net/bytebuddy/byte-buddy/1.10.14/byte-buddy-1.10.14.jar:/home/runner/.m2/repository/net/bytebuddy/byte-buddy-agent/1.10.14/byte-buddy-agent-1.10.14.jar:/home/runner/.m2/repository/org/powermock/powermock-core/2.0.9/powermock-core-2.0.9.jar:/home/runner/.m2/repository/org/javassist/javassist/3.27.0-GA/javassist-3.27.0-GA.jar:/home/runner/.m2/repository/org/powermock/powermock-api-mockito2/2.0.9/powermock-api-mockito2-2.0.9.jar:/home/runner/.m2/repository/org/powermock/powermock-api-support/2.0.9/powermock-api-support-2.0.9.jar:/home/runner/.m2/repository/org/mockito/mockito-core/3.3.3/mockito-core-3.3.3.jar:/home/runner/.m2/repository/org/objenesis/objenesis/2.6/objenesis-2.6.jar

Results

Status	Type	Serialization	Compatibility Changes
Modified	com.skyflow.vault.data.BulkInsertResponseRecord
Modified	com.skyflow.vault.data.InsertResponseRecord
Added	com.skyflow.vault.data.Token

Expand for details.

---

com.skyflow.vault.data.BulkInsertResponseRecord

• Binary-compatible
• Source-compatible
• Serialization-compatible

Status	Modifiers	Type	Name	Extends	JDK	Serialization	Compatibility Changes
Modified	public	Class	BulkInsertResponseRecord	InsertResponseRecord	JDK 8

Constructors

Status	Modifiers	Generics	Constructor	Annotations	Throws	Compatibility Changes
Source-incompatible	public		BulkInsertResponseRecord(int, String, String, Map<String, Object> → Map<String, List<Token>>, Map<String, Object>, int, String, String)	Deprecated: forRemoval=true, since="1.0.2"
Added	public		BulkInsertResponseRecord(int, String, String, Map<String, List<Token>>, Map<String, Object>, Map<String, Object>, int, String, String)

---

com.skyflow.vault.data.InsertResponseRecord

• Binary-compatible
• Source-compatible
• Serialization-compatible

Status	Modifiers	Type	Name	Extends	JDK	Serialization	Compatibility Changes
Modified	public	Class	InsertResponseRecord	Object	JDK 8

Constructors

Status	Modifiers	Generics	Constructor	Annotations	Throws	Compatibility Changes
Source-incompatible	public		InsertResponseRecord(String, String, Map<String, Object> → Map<String, List<Token>>, Map<String, Object>, int, String)	Deprecated: forRemoval=true, since="1.0.2"
Added	public		InsertResponseRecord(String, String, Map<String, List<Token>>, Map<String, Object>, Map<String, Object>, int, String)

Methods

Status	Modifiers	Generics	Type	Method	Annotations	Throws	Compatibility Changes
Added	public		Map<String, Object>	getData()
Source-incompatible	public		Map<String, Object> → Map<String, List<Token>>	getFields()	Deprecated: forRemoval=true, since="1.0.2"
Added	public		Map<String, List<Token>>	getTokens()

---

com.skyflow.vault.data.Token

• Binary-compatible
• Source-compatible
• Serialization-compatible

Status	Modifiers	Type	Name	Extends	JDK	Serialization	Compatibility Changes
Added	public	Class	Token	Object	JDK 8

Constructors

Status	Modifiers	Generics	Constructor	Annotations	Throws	Compatibility Changes
Added	public		Token(String, String)

Methods

Status	Modifiers	Generics	Type	Method	Annotations	Throws	Compatibility Changes
Added	public		String	getToken()
Added	public		String	getTokenGroupName()
Added	static public		Map<String, List<Token>>	parseTokens(Map<String, Object>)
Added	public		String	toString()

Warning

All missing classes, i.e. superclasses and interfaces that could not be found on the classpath were ignored.

Hence changes caused by these superclasses and interfaces are not reflected in the output.

---

Generated on: 2026-08-13 15:21:49.670+0000.