bkietz opened a new pull request, #37792:
URL: https://github.com/apache/arrow/pull/37792

   <!--
   Thanks for opening a pull request!
   If this is your first pull request you can find detailed information on how 
   to contribute here:
     * [New Contributor's 
Guide](https://arrow.apache.org/docs/dev/developers/guide/step_by_step/pr_lifecycle.html#reviews-and-merge-of-the-pull-request)
     * [Contributing 
Overview](https://arrow.apache.org/docs/dev/developers/overview.html)
   
   
   If this is not a [minor 
PR](https://github.com/apache/arrow/blob/main/CONTRIBUTING.md#Minor-Fixes). 
Could you open an issue for this pull request on GitHub? 
https://github.com/apache/arrow/issues/new/choose
   
   Opening GitHub issues ahead of time contributes to the 
[Openness](http://theapacheway.com/open/#:~:text=Openness%20allows%20new%20users%20the,must%20happen%20in%20the%20open.)
 of the Apache Arrow project.
   
   Then could you also rename the pull request title in the following format?
   
       GH-${GITHUB_ISSUE_ID}: [${COMPONENT}] ${SUMMARY}
   
   or
   
       MINOR: [${COMPONENT}] ${SUMMARY}
   
   In the case of PARQUET issues on JIRA the title also supports:
   
       PARQUET-${JIRA_ISSUE_ID}: [${COMPONENT}] ${SUMMARY}
   
   -->
   
   ### Rationale for this change
   
   After the PR changing the spec and schema ( 
https://github.com/apache/arrow/pull/37526 ) is accepted, this PR will be 
undrafted. It adds the minimal addition of a C++ implementation and was 
extracted from the original C++ Utf8View pr ( 
https://github.com/apache/arrow/pull/35628 ) for ease of review.
   
   <!--
    Why are you proposing this change? If this is already explained clearly in 
the issue then this section is not needed.
    Explaining clearly why changes are proposed helps reviewers understand your 
changes and offer better suggestions for fixes.  
   -->
   
   ### What changes are included in this PR?
   
   - The new types are available with new subclasses of DataType, Array, 
ArrayBuilder, ...
   - The values of string view arrays can be visited as `std::string_view` as 
with StringArray
   - String view arrays can be round tripped through IPC, parquet, and 
integration JSON
   - A variant of the string view type `utf8_view(/*has_raw_pointers=*/true)` 
is supported
     which uses raw pointer views. This enables zero copy interop with code 
which uses
     raw pointer views.
   - Conversions are provided between index/offset view arrays, raw pointer 
view arrays, and 
     regular string arrays.
   
   <!--
   There is no need to duplicate the description in the issue here but it is 
sometimes worth providing a summary of the individual changes in this PR.
   -->
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to