Hive
  1. Hive
  2. HIVE-621

Inconsistent reporting of "null" and delimiter across access types

    Details

    • Type: Wish Wish
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Invalid
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      If you INSERT OVERWRITE LOCAL DIRECTORY, you get a bunch of \N fields in your output...If you hive -e "SELECT ..." you get a bunch of "null" fields in your output. I also recall having seen NULL (in caps) before somewhere, too, but maybe I'm dreaming that.

      In any case, it would be nice if this were consistent! Preference: \N everywhere.

      Ditto, when you I O L D, your fields are ^A-delimited, but when you SELECT, they're ^V (tab)-delimited. It would be nice if this, too, were consistent. Preference: tabs everywhere.

        Activity

        Carl Steinbach made changes -
        Status Reopened [ 4 ] Resolved [ 5 ]
        Resolution Invalid [ 6 ]
        Carl Steinbach made changes -
        Resolution Fixed [ 1 ]
        Status Resolved [ 5 ] Reopened [ 4 ]
        Adam Kramer made changes -
        Field Original Value New Value
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Hide
        Adam Kramer added a comment -

        This is the way things work now. Unsure who fixed it. Note, however, that \N and null and NULL are still not consistent; see https://issues.apache.org/jira/browse/HIVE-1466

        Show
        Adam Kramer added a comment - This is the way things work now. Unsure who fixed it. Note, however, that \N and null and NULL are still not consistent; see https://issues.apache.org/jira/browse/HIVE-1466
        Hide
        Adam Kramer added a comment -

        Actually, this behavior appears to have just changed also--I did an INSERT OVERWRITE LOCAL DIRECTORY, and the result was delimited by ^A and \t characters (like, a key/value pairing...first column, ^A, other columns).

        Inserting into a local directory should DEFINITELY use the same delimiter to separate all columns. Failure to do this is likely a bug. The "wish" is that it also be consistent with SELECT output.

        Show
        Adam Kramer added a comment - Actually, this behavior appears to have just changed also--I did an INSERT OVERWRITE LOCAL DIRECTORY, and the result was delimited by ^A and \t characters (like, a key/value pairing...first column, ^A, other columns). Inserting into a local directory should DEFINITELY use the same delimiter to separate all columns. Failure to do this is likely a bug. The "wish" is that it also be consistent with SELECT output.
        Adam Kramer created issue -

          People

          • Assignee:
            Unassigned
            Reporter:
            Adam Kramer
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development