You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@tajo.apache.org by "Hyunsik Choi (JIRA)" <ji...@apache.org> on 2016/04/22 05:57:13 UTC

[jira] [Comment Edited] (TAJO-2130) Remove inet4 data type

    [ https://issues.apache.org/jira/browse/TAJO-2130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15253294#comment-15253294 ] 

Hyunsik Choi edited comment on TAJO-2130 at 4/22/16 3:57 AM:
-------------------------------------------------------------

It's because of too minor feature. IMO, INET4 is just 4 bytes data. Currently, most of operations works with some UDFs instead of basic operation system. So, it would be better to improve binary, varbinary, blob and UDFs on them. If so, Tajo can do more than now with less maintenance cost.


was (Author: hyunsik):
The main reason is too minor feature. IMO, INET4 is just 4 bytes data. Currently, most of operations works with some UDFs instead of basic operation system. So, it would be better to improve binary, varbinary, blob and UDFs on them. If so, Tajo can do more than now with less maintenance cost.

> Remove inet4 data type
> ----------------------
>
>                 Key: TAJO-2130
>                 URL: https://issues.apache.org/jira/browse/TAJO-2130
>             Project: Tajo
>          Issue Type: Task
>            Reporter: Hyunsik Choi
>            Priority: Minor
>
> Inet4 data type is not necessary and is not used. It can be easily replaced by INT4 data type with some UDFs. Also, inet4 is overlapped with binary data types. Instead of keeping inet4, it would be better to improve binary data types.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)