[
https://issues.apache.org/jira/browse/TIKA-4799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Allison updated TIKA-4799:
------------------------------
Description:
Opt-in MetadataFilter that rewrites 4.x metadata keys to their 3.x spellings
(and the inverse for ingest) so 3.x consumers survive the 4.0 rename break.
Data-driven from the
3.x↔4.x field-table join (TIKA-4797): flat renames + drops + prefix rules
(tk:digest:, tk:exception:/warn: ). Skeleton done (mechanism + trusted
reserved-key write validated);
table-gen + prefix rules + bundling depend on TIKA-4794 renames landing
was:
Opt-in MetadataFilter that rewrites 4.x metadata keys to their 3.x spellings
(and the inverse for ingest) so 3.x consumers survive the 4.0 rename break.
Data-driven from the
3.x↔4.x field-table join (TIKA-4797): flat renames + drops + prefix rules
(tk:digest:, tk:exception:/warn:). Skeleton done (mechanism + trusted
reserved-key write validated);
table-gen + prefix rules + bundling depend on TIKA-4794 renames landing
> LegacyKeyMigrationFilter for 3.x metadata key back-compat
> ---------------------------------------------------------
>
> Key: TIKA-4799
> URL: https://issues.apache.org/jira/browse/TIKA-4799
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Priority: Major
>
> Opt-in MetadataFilter that rewrites 4.x metadata keys to their 3.x spellings
> (and the inverse for ingest) so 3.x consumers survive the 4.0 rename break.
> Data-driven from the
> 3.x↔4.x field-table join (TIKA-4797): flat renames + drops + prefix rules
> (tk:digest:, tk:exception:/warn: ). Skeleton done (mechanism + trusted
> reserved-key write validated);
> table-gen + prefix rules + bundling depend on TIKA-4794 renames landing
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
