[
https://issues.apache.org/jira/browse/ASTERIXDB-3255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17765822#comment-17765822
]
ASF subversion and git services commented on ASTERIXDB-3255:
------------------------------------------------------------
Commit e45416d27de9f89870b3d353fbfe7ae0d78de874 in asterixdb's branch
refs/heads/master from Wail Alkowaileet
[ https://gitbox.apache.org/repos/asf?p=asterixdb.git;h=e45416d27d ]
[ASTERIXDB-3255][RT] Embed filter values in CSV/TSV
- user model changes: no
- storage format changes: no
- interface changes: no
Details:
Add the support to embed filter values when
parsing CSV files..
Change-Id: I611e2117cc68d7f1f2c5c5bcf1c97947f20043cb
Reviewed-on: https://asterix-gerrit.ics.uci.edu/c/asterixdb/+/17779
Integration-Tests: Jenkins <[email protected]>
Tested-by: Jenkins <[email protected]>
Reviewed-by: Wail Alkowaileet <[email protected]>
> Embed computed fields' values to resulting records
> --------------------------------------------------
>
> Key: ASTERIXDB-3255
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-3255
> Project: Apache AsterixDB
> Issue Type: Improvement
> Components: EXT - External data
> Affects Versions: 0.9.9
> Reporter: Wail Y. Alkowaileet
> Assignee: Wail Y. Alkowaileet
> Priority: Major
> Labels: triaged
> Fix For: 0.9.9
>
>
> The current implementation of dynamic prefixes requires that declared
> computed fields should also appear in the external datasets' records. In
> certain use cases, computed fields may not have the same values or they may
> have a different JSON path or type. Those cases should be handled by
> embedding the values of computed fields.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)