You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/04/19 13:21:00 UTC

[jira] [Work logged] (HIVE-26151) Support range-based time travel queries for Iceberg

     [ https://issues.apache.org/jira/browse/HIVE-26151?focusedWorklogId=758461&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-758461 ]

ASF GitHub Bot logged work on HIVE-26151:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 19/Apr/22 13:20
            Start Date: 19/Apr/22 13:20
    Worklog Time Spent: 10m 
      Work Description: marton-bod opened a new pull request, #3222:
URL: https://github.com/apache/hive/pull/3222

   ### What changes were proposed in this pull request?
   Add support for range-based time travel queries
   
   ### Why are the changes needed?
   Users can validate/audit changes between two points in time
   
   ### Does this PR introduce _any_ user-facing change?
   Query language support with new syntax
   
   ### How was this patch tested?
   Manual testing, unit tests
   




Issue Time Tracking
-------------------

            Worklog Id:     (was: 758461)
    Remaining Estimate: 0h
            Time Spent: 10m

> Support range-based time travel queries for Iceberg
> ---------------------------------------------------
>
>                 Key: HIVE-26151
>                 URL: https://issues.apache.org/jira/browse/HIVE-26151
>             Project: Hive
>          Issue Type: New Feature
>            Reporter: Marton Bod
>            Assignee: Marton Bod
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Allow querying which records have been inserted during a certain time window for Iceberg tables. The Iceberg TableScan API provides an implementation for that, so most of the work would go into adding syntax support and transporting the startTime and endTime parameters to the Iceberg input format.
> Proposed new syntax: 
> SELECT * FROM table FOR SYSTEM_TIME FROM '<startTime>' TO '<endTime>'
> SELECT * FROM table FOR SYSTEM_VERSION FROM <startVersion> TO <endVersion>
> (the TO clause is optional in both cases)



--
This message was sent by Atlassian Jira
(v8.20.7#820007)