Re: AppVeyor build taking longer than usual?

Thanks Wes. I didn't know that we can enable Appveyor build on our fork. On Mon, Jul 31, 2017 at 10:18 PM, Wes McKinney wrote: > Also, if you aren't touching any C++ or Python code (or associated CI > scripts), you can generally ignore the Appveyor build result. > > On Tue, Aug 1, 2017 at 1:09

Re: AppVeyor build taking longer than usual?

Also, if you aren't touching any C++ or Python code (or associated CI scripts), you can generally ignore the Appveyor build result. On Tue, Aug 1, 2017 at 1:09 AM, Wes McKinney wrote: > hi Siddharth, > > Appveyor seems especially bad today, this is the worst I've seen it > backed up in a while. I

Re: AppVeyor build taking longer than usual?

hi Siddharth, Appveyor seems especially bad today, this is the worst I've seen it backed up in a while. I'm partially responsible for triggering more builds today than usual. But in general, this can happen now and then. Because we are in the queue with all the other ASF projects sometimes it can

AppVeyor build taking longer than usual?

Hi All, I created a PR 4 hours ago and the AppVeyor build still hasn't finished. The Travis CI build ran fine. Is this expected? I am surprised since for all my previous PRs, both checks used to get done in 1-2 hours. In fact, the 3 latest 3 PRs (923, 924, 925) are in a similar situation. Thank

[jira] [Created] (ARROW-1301) [C++/Python] Add remaining supported libhdfs UNIX-like filesystem APIs

Wes McKinney created ARROW-1301: --- Summary: [C++/Python] Add remaining supported libhdfs UNIX-like filesystem APIs Key: ARROW-1301 URL: https://issues.apache.org/jira/browse/ARROW-1301 Project: Apache Ar

[jira] [Created] (ARROW-1300) Fix ListVector Tests

SIDDHARTH TEOTIA created ARROW-1300: --- Summary: Fix ListVector Tests Key: ARROW-1300 URL: https://issues.apache.org/jira/browse/ARROW-1300 Project: Apache Arrow Issue Type: Bug Com

[jira] [Created] (ARROW-1299) Publish nightly API documentation against master somewhere

Wes McKinney created ARROW-1299: --- Summary: Publish nightly API documentation against master somewhere Key: ARROW-1299 URL: https://issues.apache.org/jira/browse/ARROW-1299 Project: Apache Arrow

[jira] [Created] (ARROW-1298) C++: Add prefix to jemalloc functions to guard against issues when using multiple allocators in the same process

Jeff Knupp created ARROW-1298: - Summary: C++: Add prefix to jemalloc functions to guard against issues when using multiple allocators in the same process Key: ARROW-1298 URL: https://issues.apache.org/jira/browse/ARRO

Arrow 0.6.0 release planning and timeline

hi all, We're already 40 patches into the next Arrow version. I just created https://issues.apache.org/jira/browse/ARROW-1297 as a tracking issue so that any blocking issues can be tracked as we push forward to 0.6.0 You can track the status of the release here (accessible from the "Projects" tab

[jira] [Created] (ARROW-1297) 0.6.0 Release

Wes McKinney created ARROW-1297: --- Summary: 0.6.0 Release Key: ARROW-1297 URL: https://issues.apache.org/jira/browse/ARROW-1297 Project: Apache Arrow Issue Type: Task Reporter: Wes M

Re: [Java] Strange reset() method in FixedValueVectors

Thanks Siddharth. Your explanation is very helpful. It's a bit strange though that reset() doesn't release the current ArrowBuf though. This means the the size of underlying ArrowBuf doesn't change until the next realloc/allocateNew is called. This could cause the Vector holds more memory than nee

[jira] [Created] (ARROW-1296) [Java] templates/FixValueVectors reset() method doesn't set allocationSizeInBytes correctly

Li Jin created ARROW-1296: - Summary: [Java] templates/FixValueVectors reset() method doesn't set allocationSizeInBytes correctly Key: ARROW-1296 URL: https://issues.apache.org/jira/browse/ARROW-1296 Project: