Hey Ryan,
You're not the first to ask. Check out
http://www.mail-archive.com/avro-dev@hadoop.apache.org/msg01230.html. If you
can bring some PHP hackers to the Avro Hackathon on Thursday (
http://avrohackathon.eventbrite.com), it would be great to get something
started on this front.
Later,
Jeff
Hi all,
Has anyone else been thinking about this? Right now thrift's strength
over the competitors is it has a PHP implementation. Protobuf does
not. Avro probably should have one.
The first obvious "C extension" comes to mind, but making the whole
thing seamless as well as being "PHP-like" I do
[
https://issues.apache.org/jira/browse/AVRO-196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12778676#action_12778676
]
Justin SB commented on AVRO-196:
You're probably right that this is too big a change for avro
[
https://issues.apache.org/jira/browse/AVRO-204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Banachowski updated AVRO-204:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed revision 881076.
[
https://issues.apache.org/jira/browse/AVRO-204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Banachowski updated AVRO-204:
---
Status: Patch Available (was: Open)
> change the way symbolic references are tracked
> ---
[
https://issues.apache.org/jira/browse/AVRO-204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Banachowski updated AVRO-204:
---
Attachment: AVRO-204.patch
> change the way symbolic references are tracked
> -
change the way symbolic references are tracked
--
Key: AVRO-204
URL: https://issues.apache.org/jira/browse/AVRO-204
Project: Avro
Issue Type: Improvement
Components: c++
Repor
[
https://issues.apache.org/jira/browse/AVRO-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eelco Hillenius resolved AVRO-200.
--
Resolution: Won't Fix
AVRO-80 will fix this as a side effect.
> Let Utf8 implement java.io.Seria
[
https://issues.apache.org/jira/browse/AVRO-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12778561#action_12778561
]
Eelco Hillenius commented on AVRO-200:
--
Ah. I missed AVRO-80. Very sorry about that. Thi
[
https://issues.apache.org/jira/browse/AVRO-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12778550#action_12778550
]
Doug Cutting commented on AVRO-200:
---
Have you been following AVRO-80? My intent is to chan
[
https://issues.apache.org/jira/browse/AVRO-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12778545#action_12778545
]
Eelco Hillenius commented on AVRO-200:
--
I'm using the introspection based API, and for t
[
https://issues.apache.org/jira/browse/AVRO-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Hammerbacher updated AVRO-153:
---
Summary: Naming conventions for avro schemas, records and protocols (was:
Naming conventions f
[
https://issues.apache.org/jira/browse/AVRO-153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12778511#action_12778511
]
Jeff Hammerbacher commented on AVRO-153:
Pulling in some comments from Doug on the de
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 name that starts with
Patrick Hunt wrote:
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?
Do we want to enforce naming conventions or just leave them conventions?
If the
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
> What do folks think is best here? Should we require all values that don't
> have a default values to be present, i.e., record fields with a default
> value are optional, all others are mandatory?
>
Thrift allows entries in a struct to be marked "optional", which may be an
option to make explici
I think AVRO-153 is fine for this. Thanks!
Doug
Jeff Hammerbacher wrote:
Hey Doug,
Great, would you like to do the work on the spec under the aegis of 153 or
shall I open another ticket for adding namespaces to the schema portion of
the spec?
Thanks,
Jeff
On Mon, Nov 16, 2009 at 11:36 AM, D
[
https://issues.apache.org/jira/browse/AVRO-198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12778480#action_12778480
]
Doug Cutting commented on AVRO-198:
---
Good catch.
Java's protocol parser currently only req
Hey Doug,
Great, would you like to do the work on the spec under the aegis of 153 or
shall I open another ticket for adding namespaces to the schema portion of
the spec?
Thanks,
Jeff
On Mon, Nov 16, 2009 at 11:36 AM, Doug Cutting wrote:
> Jeff Hammerbacher wrote:
>
>> In the Avro spec, namespa
[
https://issues.apache.org/jira/browse/AVRO-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12778479#action_12778479
]
Doug Cutting commented on AVRO-200:
---
Wouldn't all Avro data-representation classes need to
Jeff Hammerbacher wrote:
In the Avro spec, namespaces are defined for protocols, but not for named
schemas. Yet in both the Java and Python codebases, it appears that schemas
can have a namespace. Should the code be removed, or the spec be updated?
The spec should be updated. Schemas can speci
I think it's like the "seen" tables used in Java: it contains the set of
schemas that are on the stack. Schemas can be circular, so this is
required to prevent infinite loops.
Doug
Jeff Hammerbacher wrote:
I think I know, but I want to hear it articulated. A docstring with this
information w
Scott Banachowski wrote:
Regarding union resolution, the spec says to take the first match when
comparing them. What if the first match is "promotable"? I would expect
preference for the first "exact" match, if both an exact and promotable
match existed.
Good question. I agree, and that's wh
[
https://issues.apache.org/jira/browse/AVRO-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Banachowski updated AVRO-197:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed revision 880888.
[
https://issues.apache.org/jira/browse/AVRO-52?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12778344#action_12778344
]
Philip Zeyliger commented on AVRO-52:
-
Sure. Would be great for the quickstart(s) to be p
[
https://issues.apache.org/jira/browse/AVRO-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Hammerbacher reassigned AVRO-203:
--
Assignee: Jeff Hammerbacher
> Add single space between "#" and text in license headers fo
[
https://issues.apache.org/jira/browse/AVRO-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Hammerbacher updated AVRO-203:
---
Attachment: AVRO-203.patch
> Add single space between "#" and text in license headers for Pytho
Add single space between "#" and text in license headers for Python files
-
Key: AVRO-203
URL: https://issues.apache.org/jira/browse/AVRO-203
Project: Avro
Issue Type: T
[
https://issues.apache.org/jira/browse/AVRO-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Hammerbacher reassigned AVRO-202:
--
Assignee: Jeff Hammerbacher
> Add __all__ listing to avro module
> --
Add __all__ listing to avro module
--
Key: AVRO-202
URL: https://issues.apache.org/jira/browse/AVRO-202
Project: Avro
Issue Type: Task
Components: python
Reporter: Jeff Hammerbacher
[
https://issues.apache.org/jira/browse/AVRO-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Hammerbacher updated AVRO-202:
---
Attachment: AVRO-202.patch
> Add __all__ listing to avro module
> -
[
https://issues.apache.org/jira/browse/AVRO-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Hammerbacher reassigned AVRO-199:
--
Assignee: Jeff Hammerbacher
> Clean up schemas in testio.py
> ---
[
https://issues.apache.org/jira/browse/AVRO-201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Hammerbacher reassigned AVRO-201:
--
Assignee: Jeff Hammerbacher
> Move DataFile[Reader|Writer] from io.py into datafile.py
>
[
https://issues.apache.org/jira/browse/AVRO-169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Hammerbacher reassigned AVRO-169:
--
Assignee: Jeff Hammerbacher
> Typo in the specification
> -
>
>
[
https://issues.apache.org/jira/browse/AVRO-161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12778293#action_12778293
]
Jeff Hammerbacher commented on AVRO-161:
bq. I think we would have to move DataFileWr
[
https://issues.apache.org/jira/browse/AVRO-161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Hammerbacher reassigned AVRO-161:
--
Assignee: Jeff Hammerbacher
> Add test to Python bindings for opening a non-empty file ob
Move DataFile[Reader|Writer] from io.py into datafile.py
-
Key: AVRO-201
URL: https://issues.apache.org/jira/browse/AVRO-201
Project: Avro
Issue Type: Task
Components: python
[
https://issues.apache.org/jira/browse/AVRO-201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Hammerbacher updated AVRO-201:
---
Attachment: AVRO-201.patch
Patch implements this separation.
> Move DataFile[Reader|Writer] fr
[
https://issues.apache.org/jira/browse/AVRO-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12778283#action_12778283
]
Jeff Hammerbacher commented on AVRO-136:
Hey Patrick,
Are you still planning to work
[
https://issues.apache.org/jira/browse/AVRO-52?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12778282#action_12778282
]
Jeff Hammerbacher commented on AVRO-52:
---
Does Patrick Hunt's Avro RPC Quickstart on Gith
Hey,
In the Avro spec, namespaces are defined for protocols, but not for named
schemas. Yet in both the Java and Python codebases, it appears that schemas
can have a namespace. Should the code be removed, or the spec be updated?
Thanks,
Jeff
42 matches
Mail list logo
