[
https://issues.apache.org/jira/browse/AVRO-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971978#action_12971978
]
Philip Zeyliger commented on AVRO-709:
--
Justin,
This is really close to being committed
[
https://issues.apache.org/jira/browse/AVRO-663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971941#action_12971941
]
Scott Carey commented on AVRO-663:
--
as far as the shade-plugin there are other things it can
[
https://issues.apache.org/jira/browse/AVRO-663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971939#action_12971939
]
Philip Zeyliger commented on AVRO-663:
--
There's also "shade". http://maven.apache.org/p
[
https://issues.apache.org/jira/browse/AVRO-663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971937#action_12971937
]
Thiruvalluvan M. G. commented on AVRO-663:
--
+1
Some projects call it fatjar. In fac
[
https://issues.apache.org/jira/browse/AVRO-663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971933#action_12971933
]
Scott Carey commented on AVRO-663:
--
After AVRO-647 we now produce several separate artifacts
Awesome! Thanks for doing the hard work, Scott!
On Wed, Dec 15, 2010 at 4:53 PM, Scott Carey wrote:
> AVRO-647 has been committed. The Java build now uses Maven, and produces
> several output jars.
>
> There are a few remaining tasks including:
> * Documentation.build / test instructions, a
[
https://issues.apache.org/jira/browse/AVRO-478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Carey resolved AVRO-478.
--
Resolution: Not A Problem
I do not think this is a problem anymore with the maven build. However, if it
[
https://issues.apache.org/jira/browse/AVRO-478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971921#action_12971921
]
Scott Carey commented on AVRO-478:
--
I think this ticket is invalid.
1: It doesn't matter t
[
https://issues.apache.org/jira/browse/AVRO-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Carey resolved AVRO-348.
--
Resolution: Duplicate
Fix Version/s: 1.5.0
Fixed as part of AVRO-647.
> Avro ivy dependencies inc
[
https://issues.apache.org/jira/browse/AVRO-644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Carey resolved AVRO-644.
--
Resolution: Not A Problem
This is no longer a problem for me.
> Java tests fail in ipc.trace.TestFileSpa
AVRO-647 has been committed. The Java build now uses Maven, and produces
several output jars.
There are a few remaining tasks including:
* Documentation.build / test instructions, artifact descriptions,
deploy/release instructions.
* Tie-in with global build.
For more information, see the
[
https://issues.apache.org/jira/browse/AVRO-159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Carey resolved AVRO-159.
--
Resolution: Fixed
Fixed as part of AVRO-647
> maven-avro-plugin: Allow maven builds to use avro
> --
[
https://issues.apache.org/jira/browse/AVRO-545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Carey resolved AVRO-545.
--
Resolution: Duplicate
Fixed as part of AVRO-647
> Move mapreduce bindings out of avro jar
>
[
https://issues.apache.org/jira/browse/AVRO-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Carey updated AVRO-647:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk.
> Break avro.jar in
This is my fault as part of AVRO-647. We will clean this up in another
follow-on ticket.
On Dec 15, 2010, at 3:07 PM, wrote:
> The Buildbot has detected a new failure of avro-java6-ubuntu on ASF Buildbot.
> Full details are available at:
> http://ci.apache.org/builders/avro-java6-ubuntu/build
The Buildbot has detected a new failure of avro-java6-ubuntu on ASF Buildbot.
Full details are available at:
http://ci.apache.org/builders/avro-java6-ubuntu/builds/43
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: bb-vm_ubuntu
Build Reason:
Build Source Stamp: [branch avro/trun
[
https://issues.apache.org/jira/browse/AVRO-572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971872#action_12971872
]
Scott Carey commented on AVRO-572:
--
Not fixed as part of AVRO-159 and AVRO-647. AVRO-647
GenericRecord.toString can produce invalid JSON
---
Key: AVRO-713
URL: https://issues.apache.org/jira/browse/AVRO-713
Project: Avro
Issue Type: Bug
Components: java
Affects Versions:
On 12/15/2010 01:13 PM, Jay Kreps wrote:
Is this a known issue? I think the fix is just to add another special
case in GenericData.toString()...
This does look like a bug and I don't think there's an issue for it in
Jira. Can you please file one?
Arguably GenericData.Record#toString() and G
The output from GenericRecord.toString in Java is not valid JSON, for
example a record with the schema:
{
"type": "record",
"name": "TestRecord",
"fields" : [
{"name":"enum_field",
"type":{"type":"enum",
"symbols":["a", "b"],
"name":"MyEnumType"}},
define memcmp'able encoding
---
Key: AVRO-712
URL: https://issues.apache.org/jira/browse/AVRO-712
Project: Avro
Issue Type: New Feature
Components: spec
Reporter: Doug Cutting
It would be usefu
21 matches
Mail list logo