Bradley Grantham created ARROW-4413:
---
Summary: [Python] pyarrow.hdfs.connect() failing
Key: ARROW-4413
URL: https://issues.apache.org/jira/browse/ARROW-4413
Project: Apache Arrow
Issue Type
Good to track this issue in a JIRA.
There is also the transitive issue of making external references to Flatbuffer
and Parquet (...Thrift?), with an informative/normative flag, and concrete
dated/versioned external specification, not just a github link to a moving
target.
Mike
-Origina
Krisztian Szucs created ARROW-4414:
--
Summary: [C++] Stop using cmake COMMAND_EXPAND_LISTS because it
breaks package builds for older distros
Key: ARROW-4414
URL: https://issues.apache.org/jira/browse/ARROW-4414
Krisztian Szucs created ARROW-4415:
--
Summary: [Doc] Port run_site docker to the new compose setup
Key: ARROW-4415
URL: https://issues.apache.org/jira/browse/ARROW-4415
Project: Apache Arrow
Krisztian Szucs created ARROW-4416:
--
Summary: [CI] Build gandiva in cpp docker image
Key: ARROW-4416
URL: https://issues.apache.org/jira/browse/ARROW-4416
Project: Apache Arrow
Issue Type: B
Antoine Pitrou created ARROW-4417:
-
Summary: [C++] Doc build broken
Key: ARROW-4417
URL: https://issues.apache.org/jira/browse/ARROW-4417
Project: Apache Arrow
Issue Type: Bug
Compo
See https://issues.apache.org/jira/browse/ARROW-1789
I have wanted for a while to create a single-document specification.
If anyone wants to help with this project I would appreciate it.
On Tue, Jan 29, 2019 at 4:35 AM Mike French wrote:
>
> Good to track this issue in a JIRA.
>
> There is also
Zhijun Fu created ARROW-4418:
Summary: [Plasma] replace event loop with boost::asio for plasma
store
Key: ARROW-4418
URL: https://issues.apache.org/jira/browse/ARROW-4418
Project: Apache Arrow
I
hi Manuel,
Adding a couple more folks from Apache Arrow to the thread to make
sure they see this discussion.
On Tue, Jan 22, 2019 at 3:48 AM Manuel Klimek wrote:
>
> Sorry if I'm missing something fundamental, but it seems like a new manylinux
> standard would come with the same problem of basi
David Li created ARROW-4419:
---
Summary: Deal with body buffers in FlightData
Key: ARROW-4419
URL: https://issues.apache.org/jira/browse/ARROW-4419
Project: Apache Arrow
Issue Type: Improvement
Krisztian Szucs created ARROW-4420:
--
Summary: [INTEGRATION] Pin spark's version to the recently
released arrow 0.12 patch
Key: ARROW-4420
URL: https://issues.apache.org/jira/browse/ARROW-4420
Project
Wes McKinney created ARROW-4421:
---
Summary: [Flight][C++] Handle large Flight data messages
Key: ARROW-4421
URL: https://issues.apache.org/jira/browse/ARROW-4421
Project: Apache Arrow
Issue Type
Anurag Khandelwal created ARROW-4422:
Summary: [Plasma] Enforce memory limit in plasma, rather than
relying on dlmalloc_set_footprint_limit
Key: ARROW-4422
URL: https://issues.apache.org/jira/browse/ARROW-4422
I did not hear back from Malu yet so I went ahead and removed his
contributions from the donation. I have attached an audit of all the
contributions and the status of each. I don't believe any ICLAs are needed
at this time.
Thanks,
Andy.
On Mon, Jan 28, 2019 at 7:03 PM Wes McKinney wrote:
> hi
It looks the mailing list doesn't allow attachments, so here is a link to
the audit:
https://github.com/andygrove/datafusion/blob/master/docs/DataFusion%20Contributors.pdf
On Tue, Jan 29, 2019 at 6:43 PM Andy Grove wrote:
>
> I did not hear back from Malu yet so I went ahead and removed his
>
Thanks Andy. This looks good, thank you for the thorough analysis.
I'll kick off the IP clearance vote soon so we can get this merged
within ~3 days
On Tue, Jan 29, 2019 at 9:12 PM Andy Grove wrote:
>
> It looks the mailing list doesn't allow attachments, so here is a link to
> the audit:
>
> htt
I've been struggling a bit with the workflow and I think I see what I'm
doing wrong now but wanted to confirm.
I've been running the following to keep my fork up to date:
git checkout master
git fetch upstream
git merge upstream/master
git push origin
And then to update my branch I have been doi
hi Andy,
yes, in this project I recommend never using "git merge". Merge
commits just make branches harder to maintain when master is not using
"merge" for merging patches.
It is semantically simpler in the case of conflicts with master to use
"git rebase -i" to combine your changes into a single
Got it. Thanks for the clarification.
On Tue, Jan 29, 2019 at 10:30 PM Wes McKinney wrote:
> hi Andy,
>
> yes, in this project I recommend never using "git merge". Merge
> commits just make branches harder to maintain when master is not using
> "merge" for merging patches.
>
> It is semantically
> On Jan 30, 2019, at 11:05 AM, Andy Grove wrote:
>
> Got it. Thanks for the clarification.
>
> On Tue, Jan 29, 2019 at 10:30 PM Wes McKinney wrote:
>
>> hi Andy,
>>
>> yes, in this project I recommend never using "git merge". Merge
>> commits just make branches harder to maintain when ma
20 matches
Mail list logo
