+1 md5 on src looks good and all tests are passing
Patrick
Doug Cutting wrote:
I have created a candidate build for Avro release 1.3.2.
Changes are listed at:
http://tinyurl.com/yf4rlj4
Please download, test, and vote by 30 March.
http://people.apache.org/~cutting/avro-1.3.2-rc0/
Thank
+1
Doug Cutting wrote:
Please vote as to whether you think Avro should become a top-level
Apache project, as discussed previously on this list.
I've included below a draft board resolution. It lists all current
committers as the initial members of the project management committee
(PMC) and
+1 -- full set of tests passed on src archive, md5s pass
Patrick
Doug Cutting wrote:
I have created a candidate build for Avro release 1.3.1.
Changes are listed at:
http://tinyurl.com/avro131
Please download, test, and vote by 16 March.
http://people.apache.org/~cutting/avro-1.3.1-rc0/
Have you phased out md5s purposely?
Patrick
Doug Cutting wrote:
I have created a candidate build for Avro release 1.3.1.
Changes are listed at:
http://tinyurl.com/avro131
Please download, test, and vote by 16 March.
http://people.apache.org/~cutting/avro-1.3.1-rc0/
Thanks,
Doug
[
https://issues.apache.org/jira/browse/AVRO-450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841522#action_12841522
]
Patrick Hunt commented on AVRO-450:
---
FF to remove blocker status if this is a k
ut are familiar with Maven as a user.
On Mar 3, 2010, at 11:31 PM, Patrick Hunt wrote:
I've updated the Avro starter kit now that 1.3.0 is released:
http://bit.ly/32T6Mk
For those not familiar, this is a starter kit, a project template
if you will, intended to bootstrap your Avro based pro
Issue Type: Bug
Components: python, ruby
Affects Versions: 1.3.0
Reporter: Patrick Hunt
Priority: Blocker
Errors are generated when attempting to have python client call ruby server
(and vice-versa). I noticed this issue when updating the quickstart, however
th
I've updated the Avro starter kit now that 1.3.0 is released:
http://bit.ly/32T6Mk
For those not familiar, this is a starter kit, a project template if you
will, intended to bootstrap your Avro based project. You’ll learn how to
declare a protocol, generate and compile your code, and run a wor
+1, looks sharp! I did a 'build.sh test' in the toplevel of src pkg. md5
for that file looks good as well.
Btw, "build.sh test" finished with this:
...
RPC INTEROP TESTS PASS
share/test/interop/bin/test_rpc_interop.sh: line 43: kill: (4981) - No
such process
this means everything is OK righ
Doug Cutting wrote:
Patrick Hunt wrote:
I tried installing "yajl-ruby" using gem and that failed as "mkmf" was
not available. It seems that there is also a requirement that
"ruby-dev" be installed, not just ruby. You might save some hassle by
putting that in
Doug Cutting wrote:
Patrick Hunt wrote:
I cannot build on Ubuntu Karmic (with all latest apt patches from
canonical applied), avro ruby requires echoe which requires a version
of gem (not echoe but gem, see below) not avail on Karmic. This seems
like it's going to cause problems for a
-1, one blocker and a number of usability issues
I cannot build on Ubuntu Karmic (with all latest apt patches from
canonical applied), avro ruby requires echoe which requires a version of
gem (not echoe but gem, see below) not avail on Karmic. This seems like
it's going to cause problems for a
[
https://issues.apache.org/jira/browse/AVRO-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12800866#action_12800866
]
Patrick Hunt commented on AVRO-338:
---
I hate writing shell scripts in gen
[
https://issues.apache.org/jira/browse/AVRO-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12800820#action_12800820
]
Patrick Hunt commented on AVRO-338:
---
Thiru you might want to reconsider - check
[
https://issues.apache.org/jira/browse/AVRO-319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12800377#action_12800377
]
Patrick Hunt commented on AVRO-319:
---
fwiw in zookeeper we've seen a few major c
[
https://issues.apache.org/jira/browse/AVRO-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12799397#action_12799397
]
Patrick Hunt commented on AVRO-136:
---
I'm happy to take another stab at this, ho
I think https://issues.apache.org/jira/browse/AVRO-136 would be really
useful to get out. I took a first stab at it a while ago, I have 0
experience with python packaging via pypi though and I wondered if I was
doing the right thing... anyone have experience with python packaging
via pypi that
Congratulations Jeff, well deserved! Keep up the good work.
Patrick
Doug Cutting wrote:
The Hadoop PMC has voted to add Jeff Hammerbacher as an Avro committer.
Welcome, Jeff!
Doug
[
https://issues.apache.org/jira/browse/AVRO-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12782502#action_12782502
]
Patrick Hunt commented on AVRO-240:
---
fyi, noticed this recently, it's a python
[
https://issues.apache.org/jira/browse/AVRO-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12780282#action_12780282
]
Patrick Hunt commented on AVRO-202:
---
wow. wrong tla there ;-) "dyslexics of
[
https://issues.apache.org/jira/browse/AVRO-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12780160#action_12780160
]
Patrick Hunt commented on AVRO-202:
---
Re "Added 'datafile' to module lis
Sounds good to me, having more interoperability testing is a must IMO.
To that end I've been fooling with an avro schema fuzzer which you can
glance at here: http://bit.ly/cDHST
It's no where near ready yet, in particular I'm currently fuzzing at the
protocol level and I should probably be do
[
https://issues.apache.org/jira/browse/AVRO-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Hunt updated AVRO-202:
--
Hadoop Flags: [Reviewed]
I'm fine with the patch the way it is currently, +1. I don't see how
[
https://issues.apache.org/jira/browse/AVRO-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Hunt updated AVRO-202:
--
Attachment: AVRO-202.patch
fixed two issues with the patch
1) patch failed to apply against latest trunk
[
https://issues.apache.org/jira/browse/AVRO-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779758#action_12779758
]
Patrick Hunt commented on AVRO-199:
---
as I said, my personal preference. I have many s
[
https://issues.apache.org/jira/browse/AVRO-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779753#action_12779753
]
Patrick Hunt commented on AVRO-202:
---
instead you could change a test like src/tes
[
https://issues.apache.org/jira/browse/AVRO-208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779730#action_12779730
]
Patrick Hunt commented on AVRO-208:
---
How could it be otw? Is it ever legal to have
[
https://issues.apache.org/jira/browse/AVRO-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779727#action_12779727
]
Patrick Hunt commented on AVRO-199:
---
Unfort the indentation is lost in my prior com
[
https://issues.apache.org/jira/browse/AVRO-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Hunt updated AVRO-199:
--
Status: Open (was: Patch Available)
This patch looks good to me in general, the use of '"xx
[
https://issues.apache.org/jira/browse/AVRO-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Hunt updated AVRO-199:
--
Status: Patch Available (was: Open)
> Clean up schemas in testio
[
https://issues.apache.org/jira/browse/AVRO-201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Hunt updated AVRO-201:
--
Hadoop Flags: [Reviewed]
+1, ready for commit
I reviewed the patch and it looks fine, no new tests but
[
https://issues.apache.org/jira/browse/AVRO-201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Hunt updated AVRO-201:
--
Attachment: AVRO-201.patch
This updated patch fixes the license header on the new file to be consistent
[
https://issues.apache.org/jira/browse/AVRO-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Hunt updated AVRO-203:
--
Hadoop Flags: [Reviewed]
+1, this patch looks good to me, ready for commit.
> Add single space betw
[
https://issues.apache.org/jira/browse/AVRO-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Hunt updated AVRO-202:
--
Status: Open (was: Patch Available)
-1, please add a test for this
I reviewed the patch and tested in
Affects Versions: 1.2.0
Reporter: Patrick Hunt
For records/enums/etc... with names that begin with lower case letters:
"response": {"name":"e1", "type":"enum", "symbols":["AA", "BB"]},
generates a
java
Affects Versions: 1.2.0
Reporter: Patrick Hunt
the java specific compiler flags ambiguous unions but not enums
"response": {"name":"E1", "type":"enum", "symbols":["AA", "AA"]},
--
This messa
ython
Affects Versions: 1.2.0
Reporter: Patrick Hunt
Priority: Minor
The python parser doesn't flag these as ambiguous (java flags the union, but
not the enum)
"response": {"name":"E1", "type":"enum", "symbo
: Bug
Components: java, python
Affects Versions: 1.2.0
Reporter: Patrick Hunt
According to the spec (if I'm reading it correctly)
--
Primitive type names are also defined type names. Thus, for example, the schema
"string" is equivalent to:
{"type": "
Same problem for enums btw. If you use symbols:["long", "null"] etc...
the java will fail to compile (fine for python though on both these issues).
Patrick
Doug Cutting wrote:
Patrick Hunt wrote:
Re 153 - last night I noticed that if you spec a record/enum/etc...
with a n
Re 153 - last night I noticed that if you spec a record/enum/etc... with
a name that starts with lower case it fails to compile in Java:
* start with [A-Za-z_]
Add this to 153 or a new JIRA?
Patrick
Doug Cutting wrote:
Jeff Hammerbacher wrote:
In the Avro spec, namespaces are defined for pr
198
Project: Avro
Issue Type: Bug
Components: spec
Affects Versions: 1.2.0
Reporter: Patrick Hunt
The protocol declaration section of the spec has
A protocol is a JSON object with the following attributes:
* name, string, to distinguish it from ot
[
https://issues.apache.org/jira/browse/AVRO-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12769098#action_12769098
]
Patrick Hunt commented on AVRO-159:
---
Update: I had a chat with Hiram on IRC and he
[
https://issues.apache.org/jira/browse/AVRO-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768286#action_12768286
]
Patrick Hunt commented on AVRO-159:
---
another issue that I think also needs to be han
[
https://issues.apache.org/jira/browse/AVRO-159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Hunt updated AVRO-159:
--
Attachment: AVRO-159.patch
The attached patch does the following:
1) protocol, schema compiler, and
[
https://issues.apache.org/jira/browse/AVRO-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768013#action_12768013
]
Patrick Hunt commented on AVRO-159:
---
Hiram, I took a quick look at this and it dif
I've updated the Avro starter kit now that 1.2.0 is released:
http://bit.ly/32T6Mk
For those not familiar, this is a starter kit, a project template if you
will, intended to bootstrap your Avro based project. You’ll learn how to
declare a protocol, generate and compile your code, and run a wor
[
https://issues.apache.org/jira/browse/AVRO-151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12766425#action_12766425
]
Patrick Hunt commented on AVRO-151:
---
Sounds good, I think your point "This wi
[
https://issues.apache.org/jira/browse/AVRO-151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12766403#action_12766403
]
Patrick Hunt commented on AVRO-151:
---
Matt, Re Thiru's comment, also a lesson l
[
https://issues.apache.org/jira/browse/AVRO-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12766401#action_12766401
]
Patrick Hunt commented on AVRO-146:
---
Philip, donno about clever, afaict ant-eclipse is
Congrats Thiru!
Doug Cutting wrote:
The Hadoop PMC has voted to make Thiruvalluvan M. G. an Avro committer.
Congratulations, Thiru!
Doug
[
https://issues.apache.org/jira/browse/AVRO-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12765335#action_12765335
]
Patrick Hunt commented on AVRO-146:
---
fyi, not sure what approach is better but we rece
+1, md5 matches, rat is clean, build/tests successful (ubuntu jaunty)
Patrick
Doug Cutting wrote:
I have created a candidate build for Avro release 1.2.0. This adds
support for HTTP-based RPC to Java, improves namespace handling, and
includes a number of other bug fixes and improvements.
Pl
[
https://issues.apache.org/jira/browse/AVRO-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12762772#action_12762772
]
Patrick Hunt commented on AVRO-136:
---
Yes, you do need setuptools to be installed
[
https://issues.apache.org/jira/browse/AVRO-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Hunt updated AVRO-136:
--
Attachment: AVRO-136.patch
This patch includes changes to generate both a distutils source package and a
Versions: 1.1.0
Reporter: Patrick Hunt
Assignee: Patrick Hunt
Fix For: 1.2.0
Add support for building and releasing python eggs via python's setuptools.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment t
Anyone know, is there a procedure/policy for pushing Apache developed
(Avro say, although we face the same issue in ZooKeeper) python eggs to
pypi?
http://pypi.python.org/pypi
The reason I ask is, pushing to pypi allows end users to use
easy_install to easily install/setup locally:
http://pea
[
https://issues.apache.org/jira/browse/AVRO-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Hunt updated AVRO-130:
--
Component/s: python
> "bad file descriptor" error after shutting down python ipc
Type: Bug
Affects Versions: 1.1.0
Environment: python 2.6, ubuntu (jaunty)
Reporter: Patrick Hunt
I see the following error after shutting down the ipc.SocketServer:
--
Closed: Connection-('127.0.0.1', 35220)
Exception in thread SocketServe
I've put together an Avro quick start, it's currently hosted on github:
http://github.com/phunt/avro-rpc-quickstart
this is basically a template/blueprint project that shows how to build &
run an Avro RPC based project using either Ant/Ivy or Maven. As part of
the work to support Maven I've al
[
https://issues.apache.org/jira/browse/AVRO-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12759719#action_12759719
]
Patrick Hunt commented on AVRO-124:
---
Makes sense. However I was thinking, why is
[
https://issues.apache.org/jira/browse/AVRO-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12759666#action_12759666
]
Patrick Hunt commented on AVRO-123:
---
Q: seems to be alot of boxing/unboxing going on
Affects Versions: 1.1.0
Reporter: Patrick Hunt
Priority: Blocker
The release artifact includes the ivy jar, but no license file, notice, etc...
I believe that you don't intend to ship this, but it snuck into the release
based on it being in the lib directory?
[
https://issues.apache.org/jira/browse/AVRO-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Hunt updated AVRO-123:
--
Attachment: AVRO-123.patch
> int argument types in protocol messages cause NoSuchMethodExcept
Components: java
Affects Versions: 1.1.0
Reporter: Patrick Hunt
Priority: Blocker
See attached patch for a test that reproduces:
[junit] org.apache.avro.AvroRuntimeException:
java.lang.NoSuchMethodException:
org.apache.avro.TestProtocolSpecific$TestImpl.add(int
[
https://issues.apache.org/jira/browse/AVRO-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Hunt updated AVRO-122:
--
Assignee: Patrick Hunt
Status: Patch Available (was: Open)
> ivy task does not enjoy be
[
https://issues.apache.org/jira/browse/AVRO-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Hunt updated AVRO-122:
--
Attachment: AVRO-122.patch
This patch puts a guard on ivy-init task (it will only be run once)
>
Affects Versions: 1.1.0
Reporter: Patrick Hunt
Priority: Minor
This same issue exists in ZOOKEEPER-535
---
Ant resolves the same dependencies multiple times if multiple targets are run
on the command line:
"ant b c", where b and c both depend on
+1, md5 correct, tests pass and c docs link now works.
Patrick
Doug Cutting wrote:
I have created a third candidate build for Avro release 1.1.0.
This fixes AVRO-114.
Please download, test and vote by 15 September.
http://people.apache.org/~cutting/avro-1.1.0-candidate-2/
Thanks!
Doug
+1, the tests pass and md5 is correct.
HOWEVER: I did notice that the c API is missing from doc/api/ directory,
is this correct or not? (the doc/index.html link to c api is broken,
java/python are both fine).
Patrick
Doug Cutting wrote:
I have created a second candidate build for Avro relea
+1, md5 matches, ant test passes (ubuntu jaunty), and RAT comes up clean.
Patrick
Matt Massie wrote:
I ran "ant test-c" on my Macbook (MacOS X 10.5.8) and "ant test" on CentOS
5.3 64-bit and it passed.
+1
-Matt
On Fri, Sep 4, 2009 at 10:18 AM, Doug Cutting wrote:
I have created a candid
Congratulations Avro team, this is great to see!
Doug Cutting wrote:
With 8 +1 votes (3 from PMC members) and no -1 votes, this passes.
I will push out the release.
Doug
+1 tests were successful and licensing looks fine.
Patrick
Doug Cutting wrote:
I have created a fourth candidate build for Avro release 1.0.0, fixing C
unit tests on Mac OS X.
Please download, test and vote by 14 July.
http://people.apache.org/~cutting/avro-1.0.0-candidate-3/
Thanks!
Doug
+1, all tests pass and licensing looks good
Patrick
Doug Cutting wrote:
I have created a third candidate build for Avro release 1.0.0. This adds
a few more license headers, plus fixes Python problems on Mac OS X.
Please download, test and vote by 13 July.
http://people.apache.org/~cutting/av
Shouldn't the version of the release be 1.0.0?
Not necessarily a show stopper but I tried generating the api docs and
noticed that the title is : Avro 1.0.1-dev API
build.xml has 1.0.1 rather than 1.0.0
The pom seems correct though.
Patrick
Patrick Hunt wrote:
Doug Cutting wrote:
I
Doug Cutting wrote:
I have created a second candidate build for Avro release 1.0.0.
Mostly this adds missing license headers and notices.
-1, tests all pass however a few files are still flagged by RAT, a few
of those seem valid:
---
The full list of from rat attached, here'
Patrick Hunt wrote:
Are you including licenses/notices for any/all that need it in lib/*.jar
and lib/py/*?
for example (I didn't look at them all) ASM requires binary
distributions to maintain the license, I don't see it in lib directory
or in the jar itself:
http://a
Doug Cutting wrote:
Patrick Hunt wrote:
* rat tool reports a number of issues with licensing (see attached) of
source code files
Wow, that was a big attachment!
Weird, looks like RAT includes all that by default. I just attached the
output of the command. bummer.
C and C++ sources need
Should I put the Apache license at the top of all *.[c,h] files?
In general yes, it's required of all Apache projects, in this case item 2:
http://www.apache.org/legal/src-headers.html#headers
here's an example from hadoop common:
http://svn.apache.org/repos/asf/hadoop/common/trunk/src/native/s
[
https://issues.apache.org/jira/browse/AVRO-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Hunt updated AVRO-4:
Status: Patch Available (was: Open)
> difficult to develop Avro in Ecli
[
https://issues.apache.org/jira/browse/AVRO-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Hunt updated AVRO-4:
Attachment: AVRO-4.patch
This patch fixes the compiler output to be in the correct subdirectory based on
[
https://issues.apache.org/jira/browse/AVRO-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Hunt reassigned AVRO-4:
---
Assignee: Patrick Hunt
> difficult to develop Avro in Ecli
: Patrick Hunt
A fresh checkout of Avro cannot be compiled in eclipse due to tests relying on
generated code.
You can generate the needed code using ant, however eclipse still has issues
due to the fact that the generated
code is not placed in a directory hierarchy that mimics the package
[
https://issues.apache.org/jira/browse/AVRO-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Hunt updated AVRO-3:
Status: Patch Available (was: Open)
> ValueReader does not detect EOF, infinite loop resu
[
https://issues.apache.org/jira/browse/AVRO-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Hunt updated AVRO-3:
Attachment: AVRO-3.patch
Latest patch merges in the individual patches from Doug and I into a single
patch
[
https://issues.apache.org/jira/browse/AVRO-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Hunt updated AVRO-3:
Attachment: AVRO-3.patch
This patch checks for EOF condition in the input stream.
> ValueReader does
Versions: 1.0
Environment: Ubuntu 8.10, single core
Reporter: Patrick Hunt
Priority: Critical
readLong() will hang (100%cpu infinite loop) when the end of the stream is
reached. in.read() returns -1 but that's not checked for. I suspect you want to
86 matches
Mail list logo
