[jira] [Commented] (ARROW-999) [Java] Minor types don't account for nullable FieldType flag
[
https://issues.apache.org/jira/browse/ARROW-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16005908#comment-16005908
]
Jacques Nadeau commented on ARROW-999:
--
I've previously found that it adds excessive complexity (earlier versions of
Arrow maintained them more as alternatives to the nullable versions). We've
generally found that once you do vectorized operations, word-wise or wider
bitmap evals are rarely the performance bottleneck.
> [Java] Minor types don't account for nullable FieldType flag
>
>
> Key: ARROW-999
> URL: https://issues.apache.org/jira/browse/ARROW-999
> Project: Apache Arrow
> Issue Type: Improvement
>Affects Versions: 0.3.0
>Reporter: Emilio Lahr-Vivaz
>Priority: Minor
>
> Calling e.g. `FLOAT4.getNewVector("foo", new FieldType(false, ...), ...)"
> returns a NullableFloat4Vector instead of a Float4Vector.
> edit: Float4Vector doesn't implement FieldVector, so can't currently be a
> top-level vector. I'm confused as to what the nullable flag is supposed to
> represent then.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (ARROW-1005) [JAVA] NullableDecimalVector.setSafe(int, byte[]...) throws UnsupportedOperationException
[ https://issues.apache.org/jira/browse/ARROW-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Nadeau updated ARROW-1005: -- Summary: [JAVA] NullableDecimalVector.setSafe(int, byte[]...) throws UnsupportedOperationException (was: [JAVA] NullableDecimalVector.set(int, byte[]...) throws UnsupportedOperationException) > [JAVA] NullableDecimalVector.setSafe(int, byte[]...) throws > UnsupportedOperationException > - > > Key: ARROW-1005 > URL: https://issues.apache.org/jira/browse/ARROW-1005 > Project: Apache Arrow > Issue Type: Bug >Reporter: Jacques Nadeau > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ARROW-1005) [JAVA] NullableDecimalVector.setSafe(int, byte[]...) throws UnsupportedOperationException
[ https://issues.apache.org/jira/browse/ARROW-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16005686#comment-16005686 ] Jacques Nadeau commented on ARROW-1005: --- Think it is this: https://github.com/apache/arrow/blob/master/java/vector/src/main/codegen/templates/NullableValueVectors.java#L549 Full signature: void setSafe(int index, byte[] value, int start, int length) > [JAVA] NullableDecimalVector.setSafe(int, byte[]...) throws > UnsupportedOperationException > - > > Key: ARROW-1005 > URL: https://issues.apache.org/jira/browse/ARROW-1005 > Project: Apache Arrow > Issue Type: Bug >Reporter: Jacques Nadeau > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ARROW-1005) [JAVA] NullableDecimalVector.set(int, byte[]...) throws UnsupportedOperationException
[ https://issues.apache.org/jira/browse/ARROW-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16005668#comment-16005668 ] Julien Le Dem commented on ARROW-1005: -- [~jnadeau] Could you add the stacktrace? There isn't such a method. Maybe setSafe? > [JAVA] NullableDecimalVector.set(int, byte[]...) throws > UnsupportedOperationException > - > > Key: ARROW-1005 > URL: https://issues.apache.org/jira/browse/ARROW-1005 > Project: Apache Arrow > Issue Type: Bug >Reporter: Jacques Nadeau > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ARROW-1005) NullableDecimalVector.set(int, byte[]...) throws UnsupportedOperationException
Jacques Nadeau created ARROW-1005: - Summary: NullableDecimalVector.set(int, byte[]...) throws UnsupportedOperationException Key: ARROW-1005 URL: https://issues.apache.org/jira/browse/ARROW-1005 Project: Apache Arrow Issue Type: Bug Reporter: Jacques Nadeau -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ARROW-1005) [JAVA] NullableDecimalVector.set(int, byte[]...) throws UnsupportedOperationException
[ https://issues.apache.org/jira/browse/ARROW-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Nadeau updated ARROW-1005: -- Summary: [JAVA] NullableDecimalVector.set(int, byte[]...) throws UnsupportedOperationException (was: NullableDecimalVector.set(int, byte[]...) throws UnsupportedOperationException) > [JAVA] NullableDecimalVector.set(int, byte[]...) throws > UnsupportedOperationException > - > > Key: ARROW-1005 > URL: https://issues.apache.org/jira/browse/ARROW-1005 > Project: Apache Arrow > Issue Type: Bug >Reporter: Jacques Nadeau > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ARROW-1004) ArrowInvalid: Invalid: Python object of type float is not None and is not a string, bool, or date object
William Cox created ARROW-1004:
--
Summary: ArrowInvalid: Invalid: Python object of type float is not
None and is not a string, bool, or date object
Key: ARROW-1004
URL: https://issues.apache.org/jira/browse/ARROW-1004
Project: Apache Arrow
Issue Type: Bug
Reporter: William Cox
in python 3.6, arrow 0.3.0 and pandas 0.20.1 running the following:
{code}
import pyarrow as pa
import pandas as pd
rec2_df = pd.DataFrame({'0.7': {49283: 0.0}, '@proxy_inject': {49283: '@jst'}},
dtype=object)
bad_table = pa.Table.from_pandas(rec2_df)
{code}
yields this error:
{code}
---
ArrowInvalid Traceback (most recent call last)
in ()
3
4 rec2_df = pd.DataFrame({'0.7': {49283: 0.0}, '@proxy_inject': {49283:
'@jst'}}, dtype=object)
> 5 bad_table = pa.Table.from_pandas(rec2_df)
/Users/william/anaconda/envs/parquet-python/lib/python3.6/site-packages/pyarrow/_table.pyx
in pyarrow._table.Table.from_pandas
(/Users/travis/miniconda3/conda-bld/pyarrow_1494071287970/work/arrow-d8db8f8a11a6c45645b2d7370610311731bd/python/build/temp.macosx-10.9-x86_64-3.6/_table.cxx:9250)()
/Users/william/anaconda/envs/parquet-python/lib/python3.6/site-packages/pyarrow/_table.pyx
in pyarrow._table._dataframe_to_arrays
(/Users/travis/miniconda3/conda-bld/pyarrow_1494071287970/work/arrow-d8db8f8a11a6c45645b2d7370610311731bd/python/build/temp.macosx-10.9-x86_64-3.6/_table.cxx:5997)()
/Users/william/anaconda/envs/parquet-python/lib/python3.6/site-packages/pyarrow/_array.pyx
in pyarrow._array.Array.from_pandas
(/Users/travis/miniconda3/conda-bld/pyarrow_1494071287970/work/arrow-d8db8f8a11a6c45645b2d7370610311731bd/python/build/temp.macosx-10.9-x86_64-3.6/_array.cxx:16456)()
/Users/william/anaconda/envs/parquet-python/lib/python3.6/site-packages/pyarrow/_error.pyx
in pyarrow._error.check_status
(/Users/travis/miniconda3/conda-bld/pyarrow_1494071287970/work/arrow-d8db8f8a11a6c45645b2d7370610311731bd/python/build/temp.macosx-10.9-x86_64-3.6/_error.cxx:1249)()
ArrowInvalid: Invalid: Python object of type float is not None and is not a
string, bool, or date object
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (ARROW-999) [Java] Minor types don't account for nullable FieldType flag
[
https://issues.apache.org/jira/browse/ARROW-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16005169#comment-16005169
]
Emilio Lahr-Vivaz commented on ARROW-999:
-
Thanks, maybe I should update this issue to be 'implement non-nullable
FieldVectors'? Is that something that would be desirable to implement, or would
it introduce too much complexity? It seems like it would provide a performance
improvement in the non-nullable case.
> [Java] Minor types don't account for nullable FieldType flag
>
>
> Key: ARROW-999
> URL: https://issues.apache.org/jira/browse/ARROW-999
> Project: Apache Arrow
> Issue Type: Improvement
>Affects Versions: 0.3.0
>Reporter: Emilio Lahr-Vivaz
>Priority: Minor
>
> Calling e.g. `FLOAT4.getNewVector("foo", new FieldType(false, ...), ...)"
> returns a NullableFloat4Vector instead of a Float4Vector.
> edit: Float4Vector doesn't implement FieldVector, so can't currently be a
> top-level vector. I'm confused as to what the nullable flag is supposed to
> represent then.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (ARROW-999) [Java] Minor types don't account for nullable FieldType flag
[
https://issues.apache.org/jira/browse/ARROW-999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emilio Lahr-Vivaz updated ARROW-999:
Issue Type: Improvement (was: Bug)
> [Java] Minor types don't account for nullable FieldType flag
>
>
> Key: ARROW-999
> URL: https://issues.apache.org/jira/browse/ARROW-999
> Project: Apache Arrow
> Issue Type: Improvement
>Affects Versions: 0.3.0
>Reporter: Emilio Lahr-Vivaz
>
> Calling e.g. `FLOAT4.getNewVector("foo", new FieldType(false, ...), ...)"
> returns a NullableFloat4Vector instead of a Float4Vector.
> edit: Float4Vector doesn't implement FieldVector, so can't currently be a
> top-level vector. I'm confused as to what the nullable flag is supposed to
> represent then.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (ARROW-999) [Java] Minor types don't account for nullable FieldType flag
[
https://issues.apache.org/jira/browse/ARROW-999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emilio Lahr-Vivaz updated ARROW-999:
Priority: Minor (was: Major)
> [Java] Minor types don't account for nullable FieldType flag
>
>
> Key: ARROW-999
> URL: https://issues.apache.org/jira/browse/ARROW-999
> Project: Apache Arrow
> Issue Type: Improvement
>Affects Versions: 0.3.0
>Reporter: Emilio Lahr-Vivaz
>Priority: Minor
>
> Calling e.g. `FLOAT4.getNewVector("foo", new FieldType(false, ...), ...)"
> returns a NullableFloat4Vector instead of a Float4Vector.
> edit: Float4Vector doesn't implement FieldVector, so can't currently be a
> top-level vector. I'm confused as to what the nullable flag is supposed to
> represent then.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (ARROW-999) [Java] Minor types don't account for nullable FieldType flag
[
https://issues.apache.org/jira/browse/ARROW-999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emilio Lahr-Vivaz reassigned ARROW-999:
---
Assignee: (was: Emilio Lahr-Vivaz)
> [Java] Minor types don't account for nullable FieldType flag
>
>
> Key: ARROW-999
> URL: https://issues.apache.org/jira/browse/ARROW-999
> Project: Apache Arrow
> Issue Type: Bug
>Affects Versions: 0.3.0
>Reporter: Emilio Lahr-Vivaz
>
> Calling e.g. `FLOAT4.getNewVector("foo", new FieldType(false, ...), ...)"
> returns a NullableFloat4Vector instead of a Float4Vector.
> edit: Float4Vector doesn't implement FieldVector, so can't currently be a
> top-level vector. I'm confused as to what the nullable flag is supposed to
> represent then.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (ARROW-999) [Java] Minor types don't account for nullable FieldType flag
[
https://issues.apache.org/jira/browse/ARROW-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16005137#comment-16005137
]
Jacques Nadeau commented on ARROW-999:
--
You probably need to update the vectors so that they set all the bits to null
if they have "no-nulls". The goal was to only have nullable types in the java
implementation as we found maintaining two parallel sets of vectors an extra
level of complexity.
> [Java] Minor types don't account for nullable FieldType flag
>
>
> Key: ARROW-999
> URL: https://issues.apache.org/jira/browse/ARROW-999
> Project: Apache Arrow
> Issue Type: Bug
>Affects Versions: 0.3.0
>Reporter: Emilio Lahr-Vivaz
>Assignee: Emilio Lahr-Vivaz
>
> Calling e.g. `FLOAT4.getNewVector("foo", new FieldType(false, ...), ...)"
> returns a NullableFloat4Vector instead of a Float4Vector.
> edit: Float4Vector doesn't implement FieldVector, so can't currently be a
> top-level vector. I'm confused as to what the nullable flag is supposed to
> represent then.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (ARROW-12) Get Github activity mirrored to JIRA
[ https://issues.apache.org/jira/browse/ARROW-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16005059#comment-16005059 ] Uwe L. Korn commented on ARROW-12: -- [~wesmckinn] Drill has done this > Get Github activity mirrored to JIRA > > > Key: ARROW-12 > URL: https://issues.apache.org/jira/browse/ARROW-12 > Project: Apache Arrow > Issue Type: Bug >Reporter: Jacques Nadeau >Assignee: Wes McKinney > Fix For: 0.4.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ARROW-12) Get Github activity mirrored to JIRA
[ https://issues.apache.org/jira/browse/ARROW-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16005058#comment-16005058 ] Jacques Nadeau commented on ARROW-12: - I'm pretty sure that Drill has a system when a PR starts with a JIRA number, any comments to the PR are copied back. > Get Github activity mirrored to JIRA > > > Key: ARROW-12 > URL: https://issues.apache.org/jira/browse/ARROW-12 > Project: Apache Arrow > Issue Type: Bug >Reporter: Jacques Nadeau >Assignee: Wes McKinney > Fix For: 0.4.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ARROW-1003) Hdfs and java dlls fail to load when built for Windows with MSVC
Balázs Gosztonyi created ARROW-1003: --- Summary: Hdfs and java dlls fail to load when built for Windows with MSVC Key: ARROW-1003 URL: https://issues.apache.org/jira/browse/ARROW-1003 Project: Apache Arrow Issue Type: Bug Components: C++ Environment: Windows, MSVC Reporter: Balázs Gosztonyi If I build the cpp library with MSVC for windows and try to use the hdfs io interface, the dynamic library loads fail. The reason is that in file hdfs-internal.cc on two occasions the __WIN32 define is checked instead of _WIN32. The former is not set by MSVC. I checked that these are the only two locations in the arrow library where the flag __WIN32 is used, so all we need to do is replace these two references in hdfs-internal.cc. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ARROW-998) [Doc] File format documents incorrect schema location
[ https://issues.apache.org/jira/browse/ARROW-998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16004933#comment-16004933 ] Brian Hulette commented on ARROW-998: - IPC.md suggests it should be 8-byte aligned right now, so seems like 64-byte aligning was technically correct. > [Doc] File format documents incorrect schema location > - > > Key: ARROW-998 > URL: https://issues.apache.org/jira/browse/ARROW-998 > Project: Apache Arrow > Issue Type: Bug >Reporter: Brian Hulette > > The documentation for the file format makes it look like the schema is at the > beginning of the file, since it "contains" the streaming format > (https://github.com/apache/arrow/blob/master/format/IPC.md#file-format), but > in reality the schema is in the footer > (https://github.com/apache/arrow/blob/master/format/File.fbs#L29) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ARROW-1002) [C++] It is not necessary to add padding after the magic header in the FileWriter implementation
Wes McKinney created ARROW-1002: --- Summary: [C++] It is not necessary to add padding after the magic header in the FileWriter implementation Key: ARROW-1002 URL: https://issues.apache.org/jira/browse/ARROW-1002 Project: Apache Arrow Issue Type: Improvement Components: C++ Affects Versions: 0.3.0 Reporter: Wes McKinney Fix For: 0.4.0 See ARROW-998 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ARROW-998) [Doc] File format documents incorrect schema location
[ https://issues.apache.org/jira/browse/ARROW-998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16004923#comment-16004923 ] Wes McKinney commented on ARROW-998: ARROW-1002 > [Doc] File format documents incorrect schema location > - > > Key: ARROW-998 > URL: https://issues.apache.org/jira/browse/ARROW-998 > Project: Apache Arrow > Issue Type: Bug >Reporter: Brian Hulette > > The documentation for the file format makes it look like the schema is at the > beginning of the file, since it "contains" the streaming format > (https://github.com/apache/arrow/blob/master/format/IPC.md#file-format), but > in reality the schema is in the footer > (https://github.com/apache/arrow/blob/master/format/File.fbs#L29) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ARROW-998) [Doc] File format documents incorrect schema location
[ https://issues.apache.org/jira/browse/ARROW-998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16004922#comment-16004922 ] Wes McKinney commented on ARROW-998: Looking at the implementation https://github.com/apache/arrow/blob/master/cpp/src/arrow/ipc/writer.cc#L757 I don't think we need the magic to be 64-byte aligned. I'll open a JIRA > [Doc] File format documents incorrect schema location > - > > Key: ARROW-998 > URL: https://issues.apache.org/jira/browse/ARROW-998 > Project: Apache Arrow > Issue Type: Bug >Reporter: Brian Hulette > > The documentation for the file format makes it look like the schema is at the > beginning of the file, since it "contains" the streaming format > (https://github.com/apache/arrow/blob/master/format/IPC.md#file-format), but > in reality the schema is in the footer > (https://github.com/apache/arrow/blob/master/format/File.fbs#L29) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ARROW-12) Get Github activity mirrored to JIRA
[ https://issues.apache.org/jira/browse/ARROW-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16004870#comment-16004870 ] Wes McKinney commented on ARROW-12: --- Are there examples of connecting GitHub to JIRA? We can also stick with our current process of posting the PR link as a comment > Get Github activity mirrored to JIRA > > > Key: ARROW-12 > URL: https://issues.apache.org/jira/browse/ARROW-12 > Project: Apache Arrow > Issue Type: Bug >Reporter: Jacques Nadeau >Assignee: Wes McKinney > Fix For: 0.4.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ARROW-12) Get Github activity mirrored to JIRA
[ https://issues.apache.org/jira/browse/ARROW-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wes McKinney updated ARROW-12: -- Fix Version/s: 0.4.0 > Get Github activity mirrored to JIRA > > > Key: ARROW-12 > URL: https://issues.apache.org/jira/browse/ARROW-12 > Project: Apache Arrow > Issue Type: Bug >Reporter: Jacques Nadeau > Fix For: 0.4.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (ARROW-12) Get Github activity mirrored to JIRA
[ https://issues.apache.org/jira/browse/ARROW-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wes McKinney reassigned ARROW-12: - Assignee: Wes McKinney > Get Github activity mirrored to JIRA > > > Key: ARROW-12 > URL: https://issues.apache.org/jira/browse/ARROW-12 > Project: Apache Arrow > Issue Type: Bug >Reporter: Jacques Nadeau >Assignee: Wes McKinney > Fix For: 0.4.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ARROW-12) Get Github activity mirrored to JIRA
[ https://issues.apache.org/jira/browse/ARROW-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16004869#comment-16004869 ] Wes McKinney commented on ARROW-12: --- I created INFRA-14131 > Get Github activity mirrored to JIRA > > > Key: ARROW-12 > URL: https://issues.apache.org/jira/browse/ARROW-12 > Project: Apache Arrow > Issue Type: Bug >Reporter: Jacques Nadeau > Fix For: 0.4.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ARROW-1001) [GLib] Unify writer files
Kouhei Sutou created ARROW-1001: --- Summary: [GLib] Unify writer files Key: ARROW-1001 URL: https://issues.apache.org/jira/browse/ARROW-1001 Project: Apache Arrow Issue Type: Improvement Components: GLib Reporter: Kouhei Sutou -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ARROW-999) [Java] Minor types don't account for nullable FieldType flag
[
https://issues.apache.org/jira/browse/ARROW-999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emilio Lahr-Vivaz updated ARROW-999:
Description:
Calling e.g. `FLOAT4.getNewVector("foo", new FieldType(false, ...), ...)"
returns a NullableFloat4Vector instead of a Float4Vector.
edit: Float4Vector doesn't implement FieldVector, so can't currently be a
top-level vector. I'm confused as to what the nullable flag is supposed to
represent then.
was:Calling e.g. `FLOAT4.getNewVector("foo", new FieldType(false, ...), ...)"
returns a NullableFloat4Vector instead of a Float4Vector.
> [Java] Minor types don't account for nullable FieldType flag
>
>
> Key: ARROW-999
> URL: https://issues.apache.org/jira/browse/ARROW-999
> Project: Apache Arrow
> Issue Type: Bug
>Affects Versions: 0.3.0
>Reporter: Emilio Lahr-Vivaz
>Assignee: Emilio Lahr-Vivaz
>
> Calling e.g. `FLOAT4.getNewVector("foo", new FieldType(false, ...), ...)"
> returns a NullableFloat4Vector instead of a Float4Vector.
> edit: Float4Vector doesn't implement FieldVector, so can't currently be a
> top-level vector. I'm confused as to what the nullable flag is supposed to
> represent then.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (ARROW-999) [Java] Minor types don't account for nullable FieldType flag
[
https://issues.apache.org/jira/browse/ARROW-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16004773#comment-16004773
]
Emilio Lahr-Vivaz commented on ARROW-999:
-
So it seems from the layout
(https://github.com/apache/arrow/blob/master/format/Layout.md) that all vectors
have a null bitarray, however it doesn't have to be populated if there are no
null values. So is the intention that the Field nullable flag should just
control the creation of the null bitarray?
> [Java] Minor types don't account for nullable FieldType flag
>
>
> Key: ARROW-999
> URL: https://issues.apache.org/jira/browse/ARROW-999
> Project: Apache Arrow
> Issue Type: Bug
>Affects Versions: 0.3.0
>Reporter: Emilio Lahr-Vivaz
>Assignee: Emilio Lahr-Vivaz
>
> Calling e.g. `FLOAT4.getNewVector("foo", new FieldType(false, ...), ...)"
> returns a NullableFloat4Vector instead of a Float4Vector.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (ARROW-999) [Java] Minor types don't account for nullable FieldType flag
[
https://issues.apache.org/jira/browse/ARROW-999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emilio Lahr-Vivaz reassigned ARROW-999:
---
Assignee: Emilio Lahr-Vivaz
> [Java] Minor types don't account for nullable FieldType flag
>
>
> Key: ARROW-999
> URL: https://issues.apache.org/jira/browse/ARROW-999
> Project: Apache Arrow
> Issue Type: Bug
>Affects Versions: 0.3.0
>Reporter: Emilio Lahr-Vivaz
>Assignee: Emilio Lahr-Vivaz
>
> Calling e.g. `FLOAT4.getNewVector("foo", new FieldType(false, ...), ...)"
> returns a NullableFloat4Vector instead of a Float4Vector.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (ARROW-999) [Java] Minor types don't account for nullable FieldType flag
Emilio Lahr-Vivaz created ARROW-999: --- Summary: [Java] Minor types don't account for nullable FieldType flag Key: ARROW-999 URL: https://issues.apache.org/jira/browse/ARROW-999 Project: Apache Arrow Issue Type: Bug Affects Versions: 0.3.0 Reporter: Emilio Lahr-Vivaz -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (ARROW-994) Arrow is unable to reuse Memory chunk in the Pool.
[ https://issues.apache.org/jira/browse/ARROW-994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deng Changchun closed ARROW-994. Resolution: Invalid > Arrow is unable to reuse Memory chunk in the Pool. > -- > > Key: ARROW-994 > URL: https://issues.apache.org/jira/browse/ARROW-994 > Project: Apache Arrow > Issue Type: Bug > Components: Java - Memory, Java - Vectors >Affects Versions: 0.3.0 > Environment: Arrow 0.3.0 > java version "1.7.0_79" > Windows 7 64bits > IntelliJ IDEA 14.0 ( run the test) >Reporter: Deng Changchun >Priority: Critical > Labels: Leak, Memory > Attachments: MemoryLeakTest.java > > > See the Attachment ( MemoryLeakTest.java), it just want to test whether Arrow > can reuse memory chunk in the Pool or not. However, it didn't all the time. > So, I think there is a serious glitch in Arrow 0.3.0( also in 0.1.0, related > bug: https://issues.apache.org/jira/browse/ARROW-855). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ARROW-998) [Doc] File format documents incorrect schema location
[ https://issues.apache.org/jira/browse/ARROW-998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16004703#comment-16004703 ] Wes McKinney commented on ARROW-998: I think it's in both places > [Doc] File format documents incorrect schema location > - > > Key: ARROW-998 > URL: https://issues.apache.org/jira/browse/ARROW-998 > Project: Apache Arrow > Issue Type: Bug >Reporter: Brian Hulette > > The documentation for the file format makes it look like the schema is at the > beginning of the file, since it "contains" the streaming format > (https://github.com/apache/arrow/blob/master/format/IPC.md#file-format), but > in reality the schema is in the footer > (https://github.com/apache/arrow/blob/master/format/File.fbs#L29) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ARROW-998) [Doc] File format documents incorrect schema location
Brian Hulette created ARROW-998: --- Summary: [Doc] File format documents incorrect schema location Key: ARROW-998 URL: https://issues.apache.org/jira/browse/ARROW-998 Project: Apache Arrow Issue Type: Bug Reporter: Brian Hulette The documentation for the file format makes it look like the schema is at the beginning of the file, since it "contains" the streaming format (https://github.com/apache/arrow/blob/master/format/IPC.md#file-format), but in reality the schema is in the footer (https://github.com/apache/arrow/blob/master/format/File.fbs#L29) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ARROW-997) [Java] Implement transfer in FixedSizeListVector
Emilio Lahr-Vivaz created ARROW-997: --- Summary: [Java] Implement transfer in FixedSizeListVector Key: ARROW-997 URL: https://issues.apache.org/jira/browse/ARROW-997 Project: Apache Arrow Issue Type: Task Affects Versions: 0.3.0 Reporter: Emilio Lahr-Vivaz Assignee: Emilio Lahr-Vivaz -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ARROW-996) [Website] Add 0.3 release announce in Japanese
Kouhei Sutou created ARROW-996: -- Summary: [Website] Add 0.3 release announce in Japanese Key: ARROW-996 URL: https://issues.apache.org/jira/browse/ARROW-996 Project: Apache Arrow Issue Type: Improvement Components: Website Reporter: Kouhei Sutou -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ARROW-995) [Website] 0.3 release announce has a typo in reference
[ https://issues.apache.org/jira/browse/ARROW-995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kouhei Sutou updated ARROW-995: --- Summary: [Website] 0.3 release announce has a typo in reference (was: [Website] Fix a typo) > [Website] 0.3 release announce has a typo in reference > -- > > Key: ARROW-995 > URL: https://issues.apache.org/jira/browse/ARROW-995 > Project: Apache Arrow > Issue Type: Bug > Components: Website >Reporter: Kouhei Sutou >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ARROW-995) [Website] Fix a typo
Kouhei Sutou created ARROW-995: -- Summary: [Website] Fix a typo Key: ARROW-995 URL: https://issues.apache.org/jira/browse/ARROW-995 Project: Apache Arrow Issue Type: Bug Components: Website Reporter: Kouhei Sutou Priority: Minor -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ARROW-994) Arrow is unable to reuse Memory chunk in the Pool.
[ https://issues.apache.org/jira/browse/ARROW-994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deng Changchun updated ARROW-994: - Labels: Leak Memory (was: ) Description: See the Attachment ( MemoryLeakTest.java), it just want to test whether Arrow can reuse memory chunk in the Pool or not. However, it didn't all the time. So, I think there is a serious glitch in Arrow 0.3.0( also in 0.1.0, related bug: https://issues.apache.org/jira/browse/ARROW-855). was: See the Attachment ( MemoryLeakTest.java), it just want to test whether Arrow can't reuse memory chunk in the Pool or not. However, it didn't all the time. So, I think there is a serious glitch in Arrow 0.3.0( also in 0.1.0, related bug: https://issues.apache.org/jira/browse/ARROW-855), > Arrow is unable to reuse Memory chunk in the Pool. > -- > > Key: ARROW-994 > URL: https://issues.apache.org/jira/browse/ARROW-994 > Project: Apache Arrow > Issue Type: Bug > Components: Java - Memory, Java - Vectors >Affects Versions: 0.3.0 > Environment: Arrow 0.3.0 > java version "1.7.0_79" > Windows 7 64bits > IntelliJ IDEA 14.0 ( run the test) >Reporter: Deng Changchun >Priority: Critical > Labels: Leak, Memory > Attachments: MemoryLeakTest.java > > > See the Attachment ( MemoryLeakTest.java), it just want to test whether Arrow > can reuse memory chunk in the Pool or not. However, it didn't all the time. > So, I think there is a serious glitch in Arrow 0.3.0( also in 0.1.0, related > bug: https://issues.apache.org/jira/browse/ARROW-855). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ARROW-994) Arrow is unable to reuse Memory chunk in the Pool.
Deng Changchun created ARROW-994: Summary: Arrow is unable to reuse Memory chunk in the Pool. Key: ARROW-994 URL: https://issues.apache.org/jira/browse/ARROW-994 Project: Apache Arrow Issue Type: Bug Components: Java - Memory, Java - Vectors Affects Versions: 0.3.0 Environment: Arrow 0.3.0 java version "1.7.0_79" Windows 7 64bits IntelliJ IDEA 14.0 ( run the test) Reporter: Deng Changchun Priority: Critical Attachments: MemoryLeakTest.java See the Attachment ( MemoryLeakTest.java), it just want to test whether Arrow can't reuse memory chunk in the Pool or not. However, it didn't all the time. So, I think there is a serious glitch in Arrow 0.3.0( also in 0.1.0, related bug: https://issues.apache.org/jira/browse/ARROW-855), -- This message was sent by Atlassian JIRA (v6.3.15#6346)
