[
https://issues.apache.org/jira/browse/SPARK-32760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17188612#comment-17188612
]
Ruslan Dautkhanov edited comment on SPARK-32760 at 9/1/20, 4:29 PM:
--------------------------------------------------------------------
[~smilegator] understood. Would be great to consider separating logical and
physical datatypes like it is done in Parquet for example. It might be easier
to add higher-level / logical data types then? IPv4 address for example fits
nicely into parquet's _INT64_ physical data type. Feel free to close if it's
not feasible near-term. Thanks.
was (Author: tagar):
[~smilegator] understood. Would be great to consider separating logical and
physical datatypes like it is done in Parquet for example. It might be easier
to add higher-level data types then? IPv4 address for example fits nicely into
parquet's _INT64_ data type. Feel free to close if it's not feasible near-term.
Thanks.
> Support for INET data type
> --------------------------
>
> Key: SPARK-32760
> URL: https://issues.apache.org/jira/browse/SPARK-32760
> Project: Spark
> Issue Type: Sub-task
> Components: Spark Core
> Affects Versions: 2.4.0, 3.0.0, 3.1.0
> Reporter: Ruslan Dautkhanov
> Priority: Major
>
> PostgreSQL has support for `INET` data type
> [https://www.postgresql.org/docs/9.1/datatype-net-types.html]
> We have a few customers that are interested in similar, native support for IP
> addresses, just like in PostgreSQL.
> The issue with storing IP addresses as strings, is that most of the matches
> (like if an IP address belong to a subnet) in most cases can't take leverage
> of parquet bloom filters.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
