Re: [jira] [Created] (AVRO-1794) Update docs after migration to git

[Nges B]

ok.
thanks for the updates

On 2/4/16, Ryan Blue (JIRA)  wrote:
> Ryan Blue created AVRO-1794:
> ---
>
>  Summary: Update docs after migration to git
>  Key: AVRO-1794
>  URL: https://issues.apache.org/jira/browse/AVRO-1794
>  Project: Avro
>   Issue Type: Task
>   Components: doc
> Reporter: Ryan Blue
>
>
> The [vote to move to
> git|https://mail-archives.apache.org/mod_mbox/avro-dev/201602.mbox/%3C56AFB9B9.8000304%40apache.org%3E]
> just passed. Once the INFRA ticket is completed, we will need to [update
> docs|https://avro.apache.org/version_control.html].
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.3.4#6332)
>


-- 
"it is good to dream and work for the dreams than not to dream"

[jira] [Created] (AVRO-1795) Python2: Cannot parse nested schemas

[Jakob Homan (JIRA)]

Jakob Homan created AVRO-1795:
-

 Summary: Python2: Cannot parse nested schemas
 Key: AVRO-1795
 URL: https://issues.apache.org/jira/browse/AVRO-1795
 Project: Avro
  Issue Type: Bug
  Components: python
Affects Versions: 1.8.0
Reporter: Jakob Homan
Assignee: Jakob Homan


In the Java client, one can parse nested schemas by loading the nested schema 
before the nesting schema.  

For example, a header can be defined in one file:
{code:javascript}{ "namespace": "python.avro",
  "type": "record",
  "name": "header",
  "fields": [
 { "name": "header_field", "type": "string" }
   ]
}{code}
and then included in another schema:
{code:javascript}{ "namespace": "python.avro",
  "type": "record",
  "name": "event",
  "fields": [
 {  "name": "header", "type": "python.avro.header" },
 {  "name": "event_field", "type": "string" }
  ]
}{code}
As long as one instantiates the Parser and loads the header first, the schemas 
will be reconciled and merged correctly.

However, the Python client does not support this.  The {{parse}} method of the 
{{schema.py}} file always instantiates a new Names object to hold the schemas:
{code}def parse(json_string):
  """Constructs the Schema from the JSON text."""
  # TODO(hammer): preserve stack trace from JSON parse
  # parse the JSON
  try:
json_data = json.loads(json_string)
  except:
raise SchemaParseException('Error parsing JSON: %s' % json_string)

  # Initialize the names object
  names = Names()

  # construct the Avro Schema object
  return make_avsc_object(json_data, names){code}

Some possible fixes for this are:
1) Create a separate Parser class to mimic the Schema.Parser Java approach, 
while deprecating the current parse method. 
2) Include Names as a global variable to the parse method, allowing multiple 
parse calls to populate the same namespace.  This breaks current behavior (and 
at least one unit test depends on it), so would be backwards compatible.
3) Create a new parse method that returns not only the schema, but also the 
Names instance and accepts that instance.  This keeps the code nice and 
functional while exposing the Names class, which previously had been not 
particularly public.

I like the first approach.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Moved to git!

[Ryan Blue]

The new git repository is live! You can clone it from here:

  https://git-wip-us.apache.org/repos/asf/avro.git

It looks like the commit hashes are identical to the ones in the github 
mirror, so it should just appear like trunk has been renamed to master 
if you've already cloned the github mirror. In that case, just run this:


  git remote add apache https://git-wip-us.apache.org/repos/asf/avro.git

The old SVN repository is still RW so we can change the site/ folders, 
so please remember to push to the git repo's master instead of 
committing code changes to SVN. Does anyone know if we still use those 
folders? If not, then we can probably switch it over to read-only.


There are a few tasks that we will still need to do, like updating docs 
[1] and the build.sh script. These are good starter issues if anyone out 
there wants to become a contributor!


rb


[1]: https://issues.apache.org/jira/browse/AVRO-1794

--
Ryan Blue

[jira] [Commented] (AVRO-1778) IPC/RPC for JavaScript

[Ryan Blue (JIRA)]

[ 
https://issues.apache.org/jira/browse/AVRO-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15133065#comment-15133065
 ] 

Ryan Blue commented on AVRO-1778:
-

So I posted that and then started the switch to git. :) The repo is currently 
read-only for the move and then we'll have to push to the new one. Should be 
good to go once INFRA-11205 is done.

> IPC/RPC for JavaScript
> --
>
> Key: AVRO-1778
> URL: https://issues.apache.org/jira/browse/AVRO-1778
> Project: Avro
>  Issue Type: Improvement
>  Components: javascript
>Reporter: Matthieu Monsch
>Assignee: Ryan Blue
> Attachments: AVRO-1778.patch
>
>
> This patch adds protocols to the JavaScript implementation.
> The API was designed to:
> + Be simple and idiomatic. The `Protocol` class added here is heavily 
> inspired by node.js' core `EventEmitter` to keep things as familiar as 
> possible [1]. Getting a client and server working is straightforward and 
> requires very few lines of code [2].
> + Support arbitrary transports, both stateful and stateless. Built-in node.js 
> streams are supported out of the box (e.g. TCP/UNIX sockets, or even 
> stdin/stdout). Exchanging messages over a custom transport requires 
> implementing a single simple function (see [3] for an example).
> + Work both server-side and in the browser!
> Ps: I also tested against both the Java and Python implementations over HTTP 
> and communication worked. 
> [1] https://github.com/mtth/avsc/wiki/API#ipc--rpc
> [2] https://github.com/mtth/avsc/wiki/Advanced-usage#remote-procedure-calls
> [3] https://github.com/mtth/avsc/wiki/Advanced-usage#transient-streams



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AVRO-1749) Maven plugin goal: automatic schemas (.avsc) generation from Java classes (.java)

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/AVRO-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15133249#comment-15133249
 ] 

ASF GitHub Bot commented on AVRO-1749:
--

Github user asfgit closed the pull request at:

https://github.com/apache/avro/pull/67


> Maven plugin goal: automatic schemas (.avsc) generation from Java classes 
> (.java)
> -
>
> Key: AVRO-1749
> URL: https://issues.apache.org/jira/browse/AVRO-1749
> Project: Avro
>  Issue Type: New Feature
>  Components: java
>Reporter: Matheus Santana
>Priority: Minor
>
> Current maven plugin includes goals for generating Java code (classes and 
> interfaces) from IDL (.avdl files) and Avro protocol / schemas definitions 
> (.avpr / .avsc).
> It would be nice to provide a goal for automatic [induced schemas from Java 
> code|https://avro.apache.org/docs/current/api/java/org/apache/avro/tool/InduceSchemaTool.html].



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AVRO-1063) Ruby client should use multi_json rather than being locked down to yajl

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/AVRO-1063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15133225#comment-15133225
 ] 

ASF GitHub Bot commented on AVRO-1063:
--

Github user asfgit closed the pull request at:

https://github.com/apache/avro/pull/8


> Ruby client should use multi_json rather than being locked down to yajl
> ---
>
> Key: AVRO-1063
> URL: https://issues.apache.org/jira/browse/AVRO-1063
> Project: Avro
>  Issue Type: Improvement
>  Components: ruby
>Reporter: Paul Dlug
>Assignee: Duke
>Priority: Minor
> Fix For: 1.7.6
>
> Attachments: AVRO-1063-build.patch, AVRO-1063.diff, gemfile.patch
>
>
> The avro ruby client uses yajl for JSON serialization which is just one of 
> many suitable JSON implementations for ruby. The multi_json gem provides a 
> wrapper for JSON serialization selecting the fastest library available (Oj is 
> now even faster than Yajl) and falling back to a pure ruby implementation 
> bundled with multi_json. Requiring yajl also precludes the ruby gem from 
> being used under jruby since it requires a C extension.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AVRO-695) Cycle Reference Support

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/AVRO-695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15133234#comment-15133234
 ] 

ASF GitHub Bot commented on AVRO-695:
-

Github user asfgit closed the pull request at:

https://github.com/apache/avro/pull/23


> Cycle Reference Support
> ---
>
> Key: AVRO-695
> URL: https://issues.apache.org/jira/browse/AVRO-695
> Project: Avro
>  Issue Type: New Feature
>  Components: spec
>Affects Versions: 1.7.6
>Reporter: Moustapha Cherri
>Assignee: Ryan Blue
> Fix For: 1.8.0
>
> Attachments: AVRO-695.patch, AVRO-695.patch, PERF_8000_cycles.zip, 
> avro-1.4.1-cycle.patch.gz, avro-1.4.1-cycle.patch.gz, 
> avro_circular_references.zip, avro_circular_refs6.patch, 
> avro_circular_refs7.patch, avro_circular_refs_2014_06_14.zip, 
> circular_refs_and_nonstring_map_keys_2014_06_25.zip
>
>   Original Estimate: 672h
>  Remaining Estimate: 672h
>
> This is a proposed implementation to add cycle reference support to Avro. It 
> basically introduce a new type named Cycle. Cycles contains a string 
> representing the path to the other reference.
> For example if we have an object of type Message that have a member named 
> previous with type Message too. If we have have this hierarchy:
> message
>   previous : message2
> message2
>   previous : message2
> When serializing the cycle path for "message2.previous" will be "previous".
> The implementation depend on ANTLR to evaluate those cycle at read time to 
> resolve them. I used ANTLR 3.2. This dependency is not mandated; I just used 
> ANTLR to speed thing up. I kept in this implementation the generated code 
> from ANTLR though this should not be the case as this should be generated 
> during the build. I only updated the Java code.
> I did not make full unit testing but you can find "avrotest.Main" class that 
> can be used a preliminary test.
> Please do not hesitate to contact me for further clarification if this seems 
> interresting.
> Best regards,
> Moustapha Cherri



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AVRO-1554) Avro should have support for common constructs like UUID and Date

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/AVRO-1554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15133228#comment-15133228
 ] 

ASF GitHub Bot commented on AVRO-1554:
--

Github user asfgit closed the pull request at:

https://github.com/apache/avro/pull/19


> Avro should have support for common constructs like UUID and Date
> -
>
> Key: AVRO-1554
> URL: https://issues.apache.org/jira/browse/AVRO-1554
> Project: Avro
>  Issue Type: Bug
>  Components: java
>Affects Versions: 1.7.6
>Reporter: Sachin Goyal
> Attachments: AVRO-1554.patch, AVRO-1554_2.patch, AVRO-1554_3.patch, 
> CustomEncodingUnionBug.zip
>
>
> Consider the following code:
> {code}
> public class AvroExample
> {
> public static void main (String [] args) throws Exception
> {
> ReflectData rdata = ReflectData.AllowNull.get();
> Schema schema = rdata.getSchema(Temp.class);
> 
> ReflectDatumWriter datumWriter = 
>new ReflectDatumWriter (Temp.class, rdata);
> DataFileWriter fileWriter = 
>new DataFileWriter (datumWriter);
> ByteArrayOutputStream baos = new ByteArrayOutputStream();
> fileWriter.create(schema, baos);
> fileWriter.append(new Temp());
> fileWriter.close();
> byte[] bytes = baos.toByteArray();
> GenericDatumReader datumReader = 
> new GenericDatumReader ();
> SeekableByteArrayInput avroInputStream = 
> new SeekableByteArrayInput(bytes);
> DataFileReader fileReader = 
> new DataFileReader(avroInputStream, 
> datumReader);
> schema = fileReader.getSchema();
> GenericRecord record = null;
> record = fileReader.next(record);
> System.out.println (record);
> System.out.println (record.get("id"));
> }
> }
> class Temp
> {
> UUID id = UUID.randomUUID();
> Date date = new Date();
> BigInteger bi = BigInteger.TEN;
> }
> {code}
> Output from this code is:
> {code:javascript}
> {"id": {}, "date": {}, "bi": "10"}
> {code}
> UUID and Date type fields are very common in Java and can be found a lot in 
> third-party code as well (where it may be difficult to put annotations).
> So Avro should include a default serialization/deserialization support for 
> such fields.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AVRO-1583) Add stdin support to tojson

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/AVRO-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15133247#comment-15133247
 ] 

ASF GitHub Bot commented on AVRO-1583:
--

Github user asfgit closed the pull request at:

https://github.com/apache/avro/pull/65


> Add stdin support to tojson
> ---
>
> Key: AVRO-1583
> URL: https://issues.apache.org/jira/browse/AVRO-1583
> Project: Avro
>  Issue Type: Improvement
>  Components: java
>Affects Versions: 1.7.7
>Reporter: Clément MATHIEU
>Assignee: Clément MATHIEU
> Fix For: 1.8.0
>
> Attachments: AVRO-1583.patch
>
>
> Unlike most of the avro tools tojson does not currently support reading from 
> stdin. Adding this support would be quite conveniant. For example a pipe of 
> concat and tojson is much easier to use that having to write a shell script 
> to create a local file.
> Source code said that stdin is not supported because we need a seekable 
> stream, however I believe this comment is outdated since it just works and 
> other tools have no issue dealing with stdin.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AVRO-1717) [Github] Support for optional fields when converting json to avro

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/AVRO-1717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15133243#comment-15133243
 ] 

ASF GitHub Bot commented on AVRO-1717:
--

Github user asfgit closed the pull request at:

https://github.com/apache/avro/pull/47


> [Github] Support for optional fields when converting json to avro
> -
>
> Key: AVRO-1717
> URL: https://issues.apache.org/jira/browse/AVRO-1717
> Project: Avro
>  Issue Type: Bug
>Reporter: Bartosz Wojtkiewicz
>
> Currently there is an issue when we want to convert json object to avro using 
> schema that allows optional fields (fields of type 'null'). When json object 
> does not explicitly have such field with 'null' value then is treated as not 
> conforming to schema. I added few test cases that illustrate this problem.
> PR: https://github.com/apache/avro/pull/47



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] avro pull request: AVRO-1702 Add LogicalType support to c++ librar...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/avro/pull/46


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (AVRO-1649) SchemaCompatability should be more descriptive when schemas are incompatible

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/AVRO-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15133232#comment-15133232
 ] 

ASF GitHub Bot commented on AVRO-1649:
--

Github user asfgit closed the pull request at:

https://github.com/apache/avro/pull/24


> SchemaCompatability should be more descriptive when schemas are incompatible
> 
>
> Key: AVRO-1649
> URL: https://issues.apache.org/jira/browse/AVRO-1649
> Project: Avro
>  Issue Type: Improvement
>  Components: java
>Affects Versions: 1.7.7
>Reporter: Bob Cotton
>Priority: Minor
>
> When resolving schema incompatibilities it would be nice to have a more 
> descriptive error message when schemas are not compatible. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AVRO-1764) Allow YAML files as Map to be added in RecordSchema

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/AVRO-1764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15133245#comment-15133245
 ] 

ASF GitHub Bot commented on AVRO-1764:
--

Github user asfgit closed the pull request at:

https://github.com/apache/avro/pull/61


> Allow YAML files as Map to be added in RecordSchema
> ---
>
> Key: AVRO-1764
> URL: https://issues.apache.org/jira/browse/AVRO-1764
> Project: Avro
>  Issue Type: Improvement
>  Components: java
>Affects Versions: 1.9.0
>Reporter: Tiago Lima
>
> I did this little improvement to allow me to add annotations to generated 
> files. 
> So, if I want to add persistence's annotation to the generated files, I will 
> have to add some "javaAnnotations` in schema. This is a bad idea, because my 
> client also will have these annotations. Maybe I just have to create a *new 
> layer* using the *Decorator Pattern* to add those annotations, but I don't 
> want this level of complexity in my application. I just want that my Avro 
> Objects have some custom annotations.
> Because of that, we should have the opportunity to add custom configuration 
> to be accessed via velocity template (record.vm). So, I added an attribute in 
> RecordSchema (called metadata) that read an YAML file, which has the same 
> name of the Record, to be loaded as a Map. Now, I just have to overwrite the 
> record.vm from velocity to call metadata.
> {code:title=record.vm|borderStyle=solid}
> #set ($indexName = 
> $schema.getMetadata().get('persistence').get('elasticsearch').get('indexName'))
> #set ($type = 
> $schema.getMetadata().get('persistence').get('elasticsearch').get('type'))
> @Document(indexName = "$indexName", type = "$type")
> {code}
> This can also be used to add validations and any kind of behaviour to the 
> Avro Object.
> I just opened a PR that is just a preview of a solution.
> Thanks.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AVRO-1704) Standardized format for encoding messages with Avro

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/AVRO-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15133238#comment-15133238
 ] 

ASF GitHub Bot commented on AVRO-1704:
--

Github user asfgit closed the pull request at:

https://github.com/apache/avro/pull/43


> Standardized format for encoding messages with Avro
> ---
>
> Key: AVRO-1704
> URL: https://issues.apache.org/jira/browse/AVRO-1704
> Project: Avro
>  Issue Type: Improvement
>Reporter: Daniel Schierbeck
>
> I'm currently using the Datafile format for encoding messages that are 
> written to Kafka and Cassandra. This seems rather wasteful:
> 1. I only encode a single record at a time, so there's no need for sync 
> markers and other metadata related to multi-record files.
> 2. The entire schema is inlined every time.
> However, the Datafile format is the only one that has been standardized, 
> meaning that I can read and write data with minimal effort across the various 
> languages in use in my organization. If there was a standardized format for 
> encoding single values that was optimized for out-of-band schema transfer, I 
> would much rather use that.
> I think the necessary pieces of the format would be:
> 1. A format version number.
> 2. A schema fingerprint type identifier, i.e. Rabin, MD5, SHA256, etc.
> 3. The actual schema fingerprint (according to the type.)
> 4. Optional metadata map.
> 5. The encoded datum.
> The language libraries would implement a MessageWriter that would encode 
> datums in this format, as well as a MessageReader that, given a SchemaStore, 
> would be able to decode datums. The reader would decode the fingerprint and 
> ask its SchemaStore to return the corresponding writer's schema.
> The idea is that SchemaStore would be an abstract interface that allowed 
> library users to inject custom backends. A simple, file system based one 
> could be provided out of the box.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AVRO-1569) ReflectData.AllowNull fails with polymorphism

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/AVRO-1569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15133229#comment-15133229
 ] 

ASF GitHub Bot commented on AVRO-1569:
--

Github user asfgit closed the pull request at:

https://github.com/apache/avro/pull/22


> ReflectData.AllowNull fails with polymorphism
> -
>
> Key: AVRO-1569
> URL: https://issues.apache.org/jira/browse/AVRO-1569
> Project: Avro
>  Issue Type: Bug
>Affects Versions: 1.7.6
>Reporter: Sachin Goyal
>
> UnresolvedUnionException is thrown if the following structure is serialized 
> with ReflectData.AllowNull
> (Plain ReflectData works fine)
> {code}
> class Base 
> {
>Integer a = 5;
> }
> class Derived extends Base
> {
> String b = "Foo";
> }
> class PolymorphicDO
> {
>Base obj = new Derived();
> }
> // Serialization code:
> ReflectData rdata = ReflectData.AllowNull.get();
> Schema schema = rdata.getSchema(PolymorphicDO.class);
> ReflectDatumWriter datumWriter = new ReflectDatumWriter 
> (PolymorphicDO.class, rdata);
> DataFileWriter fileWriter = new DataFileWriter (datumWriter);
> fileWriter.create(schema, new ByteArrayOutputStream());
> fileWriter.append(new PolymorphicDO());
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] avro pull request: AVRO-1749 Java: Introduce induce Maven plugin g...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/avro/pull/67


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (AVRO-680) Allow for non-string keys

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/AVRO-680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15133230#comment-15133230
 ] 

ASF GitHub Bot commented on AVRO-680:
-

Github user asfgit closed the pull request at:

https://github.com/apache/avro/pull/17


> Allow for non-string keys
> -
>
> Key: AVRO-680
> URL: https://issues.apache.org/jira/browse/AVRO-680
> Project: Avro
>  Issue Type: Improvement
>Affects Versions: 1.7.6, 1.7.7
>Reporter: Jeremy Hanna
>Assignee: Sachin Goyal
> Fix For: 1.8.0
>
> Attachments: AVRO-680.patch, AVRO-680.patch, AVRO-680.patch, 
> PERF_8000_cycles.zip, isMap_Call_Hierarchy.png, non_string_map_keys.zip, 
> non_string_map_keys2.zip, non_string_map_keys3.zip, 
> non_string_map_keys4.patch, non_string_map_keys5.patch, 
> non_string_map_keys6.patch, non_string_map_keys7.patch, 
> non_string_map_perf.txt, non_string_map_perf2.txt, original_perf.txt
>
>
> Based on an email thread back in April, Doug Cutting proposed a possible 
> solution for having non-string keys:
> Stu Hood wrote:
> > I can understand the reasoning behind AVRO-9, but now I need to look for an 
> > alternative to a 'map' that will allow me to store an association of bytes 
> > keys to values.
> A map of Foo has the same binary format as an array of records, each
> with a string field and a Foo field.  So an application can use an array
> schema similar to this to represent map-like structures with, e.g.,
> non-string keys.
> Perhaps we could establish standard properties that indicate that a
> given array of records should be represented in a map-like way if
> possible?  E.g.,:
> {"type": "array", "isMap": true, "items": {"type":"record", ...}}
> Doug



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] avro pull request: Protect from struct redefinition errors

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/avro/pull/62


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (AVRO-1493) Avoid the "Turkish Locale Problem"

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/AVRO-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15133250#comment-15133250
 ] 

ASF GitHub Bot commented on AVRO-1493:
--

Github user asfgit closed the pull request at:

https://github.com/apache/avro/pull/63


> Avoid the "Turkish Locale Problem"
> --
>
> Key: AVRO-1493
> URL: https://issues.apache.org/jira/browse/AVRO-1493
> Project: Avro
>  Issue Type: Bug
>  Components: java
>Affects Versions: 1.7.6
> Environment: Hadoop trunk build error on mac-os with turkish locale.
>Reporter: Serkan Taş
> Fix For: 1.7.8
>
>
> Locale dependent String.toUpperCase(), String.toLowerCase() causes unexpected 
> behavior if the the locale is Turkish
> Not sure about String.equalsIgnoreCase(..).
> Here is the error :
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-compiler-plugin:2.5.1:testCompile 
> (default-testCompile) on project hadoop-common: Compilation failure
> [ERROR] 
> /Users/serkan/programlar/dev/hadooptest/hadoop-trunk/hadoop-common-project/hadoop-common/target/generated-test-sources/java/org/apache/hadoop/io/serializer/avro/AvroRecord.java:[10,244]
>  unmappable character for encoding UTF-8
> [ERROR] -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.maven.plugins:maven-compiler-plugin:2.5.1:testCompile 
> (default-testCompile) on project hadoop-common: Compilation failure
> /Users/serkan/programlar/dev/hadooptest/hadoop-trunk/hadoop-common-project/hadoop-common/target/generated-test-sources/java/org/apache/hadoop/io/serializer/avro/AvroRecord.java:[10,244]
>  unmappable character for encoding UTF-8
> I f i check the code i discovered the reason for error :
>  public static final org.apache.avro.Schema SCHEMA$ = new 
> org.apache.avro.Schema.Parser().parse("{\"type\":\"record\",\"name\":\"AvroRecord\",\"namespace\":\"org.apache.hadoop.io.serializer.avro\",\"fields\":[{\"name\":\"intField\",\"type\":\"Ýnt\"}]}");
> For the code generated from schema, locale dependent capitalization of letter 
> "i" turns in to "Ý" should be the same for "I" to "ı".
> Same bug exist in OPENEJB-1071, OAK-260, IBATIS-218.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] avro pull request: Avro 1748

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/avro/pull/52


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (AVRO-1695) Add LogicalType support to the Ruby library

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/AVRO-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15133239#comment-15133239
 ] 

ASF GitHub Bot commented on AVRO-1695:
--

Github user asfgit closed the pull request at:

https://github.com/apache/avro/pull/44


> Add LogicalType support to the Ruby library
> ---
>
> Key: AVRO-1695
> URL: https://issues.apache.org/jira/browse/AVRO-1695
> Project: Avro
>  Issue Type: New Feature
>  Components: ruby
>Reporter: Daniel Schierbeck
>
> It would be nice if the Ruby library had feature parity. I would be willing 
> to contribute work if someone could review and merge the code.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] avro pull request: stdin support for getschema

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/avro/pull/65


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (AVRO-1649) SchemaCompatability should be more descriptive when schemas are incompatible

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/AVRO-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15133241#comment-15133241
 ] 

ASF GitHub Bot commented on AVRO-1649:
--

Github user asfgit closed the pull request at:

https://github.com/apache/avro/pull/49


> SchemaCompatability should be more descriptive when schemas are incompatible
> 
>
> Key: AVRO-1649
> URL: https://issues.apache.org/jira/browse/AVRO-1649
> Project: Avro
>  Issue Type: Improvement
>  Components: java
>Affects Versions: 1.7.7
>Reporter: Bob Cotton
>Priority: Minor
>
> When resolving schema incompatibilities it would be nice to have a more 
> descriptive error message when schemas are not compatible. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AVRO-1649) SchemaCompatability should be more descriptive when schemas are incompatible

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/AVRO-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15133236#comment-15133236
 ] 

ASF GitHub Bot commented on AVRO-1649:
--

Github user asfgit closed the pull request at:

https://github.com/apache/avro/pull/33


> SchemaCompatability should be more descriptive when schemas are incompatible
> 
>
> Key: AVRO-1649
> URL: https://issues.apache.org/jira/browse/AVRO-1649
> Project: Avro
>  Issue Type: Improvement
>  Components: java
>Affects Versions: 1.7.7
>Reporter: Bob Cotton
>Priority: Minor
>
> When resolving schema incompatibilities it would be nice to have a more 
> descriptive error message when schemas are not compatible. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AVRO-1702) Add LogicalType support to c++ library

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/AVRO-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15133242#comment-15133242
 ] 

ASF GitHub Bot commented on AVRO-1702:
--

Github user asfgit closed the pull request at:

https://github.com/apache/avro/pull/46


> Add LogicalType support to c++ library
> --
>
> Key: AVRO-1702
> URL: https://issues.apache.org/jira/browse/AVRO-1702
> Project: Avro
>  Issue Type: New Feature
>  Components: c++
>Reporter: peter liu
>Assignee: peter liu
>
> I'd like to port the logicaltype support to c++ library



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] avro pull request: Proposed schema IDL for Python

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/avro/pull/53


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (AVRO-1663) C Library does not handle enum's namespace

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/AVRO-1663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15133237#comment-15133237
 ] 

ASF GitHub Bot commented on AVRO-1663:
--

Github user asfgit closed the pull request at:

https://github.com/apache/avro/pull/34


> C Library does not handle enum's namespace
> --
>
> Key: AVRO-1663
> URL: https://issues.apache.org/jira/browse/AVRO-1663
> Project: Avro
>  Issue Type: Bug
>  Components: c
>Affects Versions: 1.7.7
>Reporter: Thomas Sanchez
>Assignee: Martin Kleppmann
> Fix For: 1.8.0
>
> Attachments: AVRO-1663-2.patch, AVRO-1663-3.patch, AVRO-1663-4.patch, 
> AVRO-1663.patch
>
>
> {code}{
>   "type": "record",
>   "name": "EventName",
>   "namespace": "com.company.avro.schemas",
>   "fields": [
> {"name": "eventname_model",
>  "type": {
>"type": "enum",
>"namespace": "com.company.models",
>"name": "EventName",
>"symbols": [""]
>  }
> }
>  ]
> }
> {code}
> Such a schema is perfectly valid but the C library does no handle it because 
> it does not parse the namespace field.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AVRO-1647) Add missing aliases attribute to the schema

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/AVRO-1647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15133231#comment-15133231
 ] 

ASF GitHub Bot commented on AVRO-1647:
--

Github user asfgit closed the pull request at:

https://github.com/apache/avro/pull/21


> Add missing aliases attribute to the schema 
> 
>
> Key: AVRO-1647
> URL: https://issues.apache.org/jira/browse/AVRO-1647
> Project: Avro
>  Issue Type: Improvement
>  Components: ruby
>Reporter: Peter Ableda
>Priority: Minor
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AVRO-1369) MacOSX build fatal error: 'byteswap.h' file not found

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/AVRO-1369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15133226#comment-15133226
 ] 

ASF GitHub Bot commented on AVRO-1369:
--

Github user asfgit closed the pull request at:

https://github.com/apache/avro/pull/11


> MacOSX build fatal error: 'byteswap.h' file not found
> -
>
> Key: AVRO-1369
> URL: https://issues.apache.org/jira/browse/AVRO-1369
> Project: Avro
>  Issue Type: Bug
>  Components: c
>Affects Versions: 1.7.5
> Environment: Mac OS X 10.8.4
>Reporter: thinker0
> Fix For: 1.7.6
>
> Attachments: byteswap-h-mac-osx-patch.diff
>
>
> {code}
> $ brew -v install avro-c
> Homebrew 0.9.4
> ==> Downloading 
> http://www.apache.org/dyn/closer.cgi?path=avro/avro-1.7.5/c/avro-c-1.7.5.tar.gz
> Already downloaded: /Library/Caches/Homebrew/avro-c-1.7.5.tar.gz
> tar xf /Library/Caches/Homebrew/avro-c-1.7.5.tar.gz
> ==> cmake . -DCMAKE_INSTALL_PREFIX=/usr/local/Cellar/avro-c/1.7.5 
> -DCMAKE_BUILD_TYPE=None -DCMAKE_FIND_FRAMEWORK=LAST -Wno-dev
> cmake . -DCMAKE_INSTALL_PREFIX=/usr/local/Cellar/avro-c/1.7.5 
> -DCMAKE_BUILD_TYPE=None -DCMAKE_FIND_FRAMEWORK=LAST -Wno-dev
> -- The C compiler identification is Clang 4.2.0
> -- The CXX compiler identification is Clang 4.2.0
> -- Check for working C compiler: /usr/local/Library/ENV/4.3/cc
> -- Check for working C compiler: /usr/local/Library/ENV/4.3/cc -- works
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Check for working CXX compiler: /usr/local/Library/ENV/4.3/c++
> -- Check for working CXX compiler: /usr/local/Library/ENV/4.3/c++ -- works
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - done
> -- Found ZLIB: /usr/lib/libz.dylib (found version "1.2.5")
> Enabled deflate codec
> -- Found Snappy: /usr/local/lib/libsnappy.dylib
> Enabled snappy codec
> -- Found PkgConfig: /usr/local/bin/pkg-config (found version "0.28")
> -- checking for module 'liblzma'
> --   package 'liblzma' not found
> Disabled lzma codec. liblzma not found.
> -- Searching for asciidoc...
> CMake Warning at docs/CMakeLists.txt:51 (message):
>   asciidoc not found.  HTML documentation will *NOT* be built.
> -- Configuring done
> -- Generating done
> -- Build files have been written to: /tmp/avro-c-lfmK/avro-c-1.7.5
> ==> make install
> make install
> Scanning dependencies of target avro-static
> Scanning dependencies of target avro-shared
> [  1%] [  2%] [  2%] [  3%] [  6%] [  6%] [  6%] [  7%] Building C object 
> src/CMakeFiles/avro-shared.dir/array.o
> Building C object src/CMakeFiles/avro-static.dir/array.o
> Building C object src/CMakeFiles/avro-shared.dir/allocation.o
> Building C object src/CMakeFiles/avro-static.dir/consumer.o
> Building C object src/CMakeFiles/avro-shared.dir/codec.o
> Building C object src/CMakeFiles/avro-static.dir/codec.o
> Building C object src/CMakeFiles/avro-static.dir/allocation.o
> Building C object src/CMakeFiles/avro-shared.dir/consumer.o
> /tmp/avro-c-lfmK/avro-c-1.7.5/src/codec.c:21:10: fatal error: 'byteswap.h' 
> file not found
> #include 
>  ^
> /tmp/avro-c-lfmK/avro-c-1.7.5/src/codec.c:21:10: fatal error: 'byteswap.h' 
> file not found
> #include 
>  ^
> 1 error generated.
> make[2]: *** [src/CMakeFiles/avro-shared.dir/codec.o] Error 1
> make[2]: *** Waiting for unfinished jobs
> 1 error generated.
> make[2]: *** [src/CMakeFiles/avro-static.dir/codec.o] Error 1
> make[2]: *** Waiting for unfinished jobs
> [  8%] [  9%] make[1]: *** [src/CMakeFiles/avro-shared.dir/all] Error 2
> make[1]: *** Waiting for unfinished jobs
> Building C object src/CMakeFiles/avro-static.dir/datafile.o
> Building C object src/CMakeFiles/avro-static.dir/consume-binary.o
> make[1]: *** [src/CMakeFiles/avro-static.dir/all] Error 2
> make: *** [all] Error 2
> {code}
> # 
> https://github.com/ferol/Lunchbox/commit/ae333fccd621778d88aced9533a135a25316cef1



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AVRO-1762) Allow putting additional objects into the Velocity template

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/AVRO-1762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15133246#comment-15133246
 ] 

ASF GitHub Bot commented on AVRO-1762:
--

Github user asfgit closed the pull request at:

https://github.com/apache/avro/pull/59


> Allow putting additional objects into the Velocity template
> ---
>
> Key: AVRO-1762
> URL: https://issues.apache.org/jira/browse/AVRO-1762
> Project: Avro
>  Issue Type: Improvement
>  Components: java
>Reporter: Matheus Santana
> Attachments: AVRO-1762.patch
>
>
> This JIRA proposes the ability to inject custom POJOs into the Velocity 
> template.
> It is possible [to override template directory 
> configuration|https://issues.apache.org/jira/browse/AVRO-963?jql=project%20%3D%20AVRO%20AND%20component%20%3D%20java%20AND%20text%20~%20%22template%22]
>  and thus make the compiler to generate customized code. However, 
> customization possibilities are constrained to [Velocity Template 
> Language|https://velocity.apache.org/engine/releases/velocity-1.5/user-guide.html#velocity_template_language_vtl:_an_introduction]
>  and [objects 
> injected|https://github.com/apache/avro/blob/trunk/lang/java/compiler/src/main/java/org/apache/avro/compiler/specific/SpecificCompiler.java#L339-L340]
>  into the template's context.
> The ability of injecting custom objects into the template's context would 
> leverage customization possibilities to the whole Java language itself. The 
> patch I'm about to attach modifies both compiler and maven-plugin in order to 
> provide client applications with the ability of easy injecting custom Java 
> objects into the Velocity templates' context.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AVRO-1684) Add date, time, and timestamp to specific object model classes

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/AVRO-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15133240#comment-15133240
 ] 

ASF GitHub Bot commented on AVRO-1684:
--

Github user asfgit closed the pull request at:

https://github.com/apache/avro/pull/37


> Add date, time, and timestamp to specific object model classes
> --
>
> Key: AVRO-1684
> URL: https://issues.apache.org/jira/browse/AVRO-1684
> Project: Avro
>  Issue Type: New Feature
>  Components: java
>Affects Versions: 1.7.7
>Reporter: Ryan Blue
>Assignee: Ryan Blue
> Fix For: 1.7.8
>
> Attachments: AVRO-1684.1.patch
>
>
> AVRO-1672 adds conversions for date, time, and timestamp. These should be 
> available to specific classes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AVRO-1746) JSON encoder and decoder for Ruby

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/AVRO-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15133244#comment-15133244
 ] 

ASF GitHub Bot commented on AVRO-1746:
--

Github user asfgit closed the pull request at:

https://github.com/apache/avro/pull/56


> JSON encoder and decoder for Ruby
> -
>
> Key: AVRO-1746
> URL: https://issues.apache.org/jira/browse/AVRO-1746
> Project: Avro
>  Issue Type: New Feature
>  Components: ruby
>Reporter: Saroj Yadav
>
> Hi,
> I am thinking of adding a JSON encoder and decoder for Ruby. What do you 
> think?
> Best,
> Saroj



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] avro pull request: Move management of the file stream into DataFil...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/avro/pull/68


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] avro pull request: AVRO-1762. Java: Put additional objects into Ve...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/avro/pull/59


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] avro pull request: AVRO-1764: YAML loader to add metadata properti...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/avro/pull/61


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (AVRO-1568) Allow Java polymorphism in Avro for third-party code

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/AVRO-1568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15133227#comment-15133227
 ] 

ASF GitHub Bot commented on AVRO-1568:
--

Github user asfgit closed the pull request at:

https://github.com/apache/avro/pull/20


> Allow Java polymorphism in Avro for third-party code
> 
>
> Key: AVRO-1568
> URL: https://issues.apache.org/jira/browse/AVRO-1568
> Project: Avro
>  Issue Type: Improvement
>Affects Versions: 1.7.6
>Reporter: Sachin Goyal
>
> A large number of Java designs interacting with databases with 
> Hibernate/Couchbase (perhaps, even otherwise) have Java polymorphism of the 
> form:
> {code:java}
> class Base 
> {
>Integer a = 5;
> }
> class Derived extends Base
> {
> String b = "Foo";
> }
> class PolymorphicDO
> {
>Base b = new Derived();
> }
> {code}
> Jackson handles this kind of field by using annotations such as:
> {code}
> @JsonTypeInfo(use = JsonTypeInfo.Id.CLASS, include = 
> JsonTypeInfo.As.PROPERTY, property = "@class”)
> {code}
> If such a thing can be added to Avro, all those Java designs could become 
> immediately usable with Avro. They would also become Hadoop compatible due to 
> AvroSerde.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] avro pull request: AVRO-680: Non-string map keys support

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/avro/pull/17


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] avro pull request: Install the Snappy packages to the Docker image

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/avro/pull/42


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] avro pull request: AVRO-1684: Add support for date, time, and time...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/avro/pull/37


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] avro pull request: [AVRO-1647] Ruby: Add aliases attribute to fiel...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/avro/pull/21


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] avro pull request: bugfix cant serialize json with characters >127...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/avro/pull/38


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] avro pull request: use bytesize on buffer string

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/avro/pull/13


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] avro pull request: AVRO-695: Support for circular references.

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/avro/pull/23


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] avro pull request: read doc fields from messages, fields, records

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/avro/pull/14


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] avro pull request: AVRO-607. Make SpecificData#getSchema thread-sa...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/avro/pull/30


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] avro pull request: AVRO-1649: Teach SchemaCompatability to be more...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/avro/pull/24


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] avro pull request: Snappy support for Ruby

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/avro/pull/31


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] avro pull request: AVRO-1493: Java: Schema fingerprint vary by loc...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/avro/pull/63


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] avro pull request: Depend on external libjansson and fix for AVRO-...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/avro/pull/57


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] avro pull request: Branch schema normalization python

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/avro/pull/48


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] avro pull request: Asynchronous processing of messages

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/avro/pull/50


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] avro pull request: AVRO-1746 - Support JSON encoding in Ruby

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/avro/pull/56


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] avro pull request: AVRO-1717: Support for optional fields when con...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/avro/pull/47


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] avro pull request: Java: Refactor Avro Maven Plugin test classes

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/avro/pull/60


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] avro pull request: AVRO-1649 - More informative messages for schem...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/avro/pull/33


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] avro pull request: AVRO-1569: Check base-classes too while resolvi...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/avro/pull/22


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] avro pull request: Fix dependency gem name

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/avro/pull/12


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Updated] (AVRO-1793) Python2: Retain stack trace and original exception when failing to parse schema

[Jakob Homan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AVRO-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jakob Homan updated AVRO-1793:
--
Status: Patch Available  (was: Open)

> Python2: Retain stack trace and original exception when failing to parse 
> schema
> ---
>
> Key: AVRO-1793
> URL: https://issues.apache.org/jira/browse/AVRO-1793
> Project: Avro
>  Issue Type: Improvement
>  Components: python
>Affects Versions: 1.8.0
>Reporter: Jakob Homan
>Assignee: Jakob Homan
> Attachments: AVRO-1793-2.patch, AVRO-1793.patch
>
>
> Currently when a parse call fails the original exception is swallowed and 
> replaced by a generic SchemaParseException.  We should keep the original 
> stack trace and include the actual exception message.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AVRO-1562) Add support for types extending Maps/Collections

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/AVRO-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15133233#comment-15133233
 ] 

ASF GitHub Bot commented on AVRO-1562:
--

Github user asfgit closed the pull request at:

https://github.com/apache/avro/pull/25


> Add support for types extending Maps/Collections
> 
>
> Key: AVRO-1562
> URL: https://issues.apache.org/jira/browse/AVRO-1562
> Project: Avro
>  Issue Type: Bug
>Affects Versions: 1.7.6
>Reporter: Sachin Goyal
> Attachments: custom_map_and_collections1.patch
>
>
> Consider the following code:
> {code}
> import java.io.ByteArrayOutputStream;
> import java.util.*;
> import org.apache.avro.Schema;
> import org.apache.avro.file.DataFileWriter;
> import org.apache.avro.reflect.ReflectData;
> import org.apache.avro.reflect.ReflectDatumWriter;
> public class AvroDerivingMaps
> {
> public static void main (String [] args) throws Exception
> {
> MapDerivedContainer orig = new MapDerivedContainer();
> ReflectData rdata = ReflectData.AllowNull.get();
> Schema schema = rdata.getSchema(MapDerivedContainer.class);
> System.out.println(schema);
> 
> ReflectDatumWriter datumWriter = new 
> ReflectDatumWriter (MapDerivedContainer.class, rdata);
> DataFileWriter fileWriter = new 
> DataFileWriter (datumWriter);
> ByteArrayOutputStream baos = new ByteArrayOutputStream();
> fileWriter.create(schema, baos);
> fileWriter.append(orig);
> fileWriter.close();
> }
> }
> class MapDerived extends HashMap
> {
> Integer a = 1;
> String b = "b";
> }
> class MapDerivedContainer
> {
> MapDerived2 map = new MapDerived2();
> }
> class MapDerived2 extends MapDerived
> {
> String c = "c";
> }
> {code}
> \\
> \\
> It throws the following exception:
> {code:javascript}
> {"type":"record","name":"MapDerivedContainer","namespace":"avro","fields":[{"name":"map","type":["null",{"type":"record","name":"MapDerived2","fields":[{"name":"c","type":["null","string"],"default":null},{"name":"a","type":["null","int"],"default":null},{"name":"b","type":["null","string"],"default":null}]}],"default":null}]}
> {code}
> {color:brown}
> Exception in thread "main" 
> org.apache.avro.file.DataFileWriter$AppendWriteException:
> org.apache.avro.UnresolvedUnionException: 
> Caused by: org.apache.avro.UnresolvedUnionException: Not in union 
> ["null",{"type":"record","name":"MapDerived2","namespace":"avro","fields":[{"name":"c","type":["null","string"],"default":null},{"name":"a","type":["null","int"],"default":null},{"name":"b","type":["null","string"],"default":null}]}]:
>  {}
>   at 
> org.apache.avro.generic.GenericData.resolveUnion(GenericData.java:600)
>   at 
> org.apache.avro.generic.GenericDatumWriter.resolveUnion(GenericDatumWriter.java:151)
>   at 
> org.apache.avro.generic.GenericDatumWriter.write(GenericDatumWriter.java:71)
>   at 
> org.apache.avro.reflect.ReflectDatumWriter.write(ReflectDatumWriter.java:145)
>   at 
> org.apache.avro.generic.GenericDatumWriter.writeField(GenericDatumWriter.java:114)
>   at 
> org.apache.avro.reflect.ReflectDatumWriter.writeField(ReflectDatumWriter.java:203)
>   at 
> org.apache.avro.generic.GenericDatumWriter.writeRecord(GenericDatumWriter.java:104)
>   at 
> org.apache.avro.generic.GenericDatumWriter.write(GenericDatumWriter.java:66)
>   at 
> org.apache.avro.reflect.ReflectDatumWriter.write(ReflectDatumWriter.java:145)
>   at 
> org.apache.avro.generic.GenericDatumWriter.write(GenericDatumWriter.java:58)
>   at org.apache.avro.file.DataFileWriter.append(DataFileWriter.java:290)
>   ... 1 more
> {color}
> \\
> \\
> It appears that ReflectData#createSchema() checks for "type instanceof 
> ParameterizedType" and because of this, it skips handling of the map.
> The same is not true of GenericData#isMap() and GenericData#resolveUnion() 
> fails because of this.
> The same may be true for classes extending ArrayList, Collection, Set etc.
> Also, note the schema for the class extending Map:
> {code:javascript}
> {  
>"type":"record",
>"name":"MapDerived2",
>"fields":[  
>   {  
>  "name":"c",
>  "type":[  
> "null",
> "string"
>  ],
>  "default":null
>   },
>   {  
>  "name":"a",
>  "type":[  
> "null",
> "int"
>  ],
>  "default":null
>   },
>   {  
>  "name":"b",
>  "type":[  
> "null",
> "string"
>  ],
>  "default":null
>   }
>]
> }
> {code}
> This schema ignores the Map completely.
> Probably, for such a class, the schema should look like:
> {code:javascript}
> {
>"type":"record",
>

[jira] [Commented] (AVRO-607) SpecificData.getSchema not thread-safe

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/AVRO-607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15133235#comment-15133235
 ] 

ASF GitHub Bot commented on AVRO-607:
-

Github user asfgit closed the pull request at:

https://github.com/apache/avro/pull/30


> SpecificData.getSchema not thread-safe
> --
>
> Key: AVRO-607
> URL: https://issues.apache.org/jira/browse/AVRO-607
> Project: Avro
>  Issue Type: Bug
>  Components: java
>Affects Versions: 1.3.3
>Reporter: Stephen Tu
> Attachments: AVRO-607.patch
>
>
> SpecificData.getSchema uses a WeakHashMap to cache schemas, but WeakHashMap 
> is not thread-safe, and the method itself is not synchronized. Seems like 
> this could lead to the data structure getting corrupted. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AVRO-1691) Error parsing schema if schema is json string

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/AVRO-1691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15133248#comment-15133248
 ] 

ASF GitHub Bot commented on AVRO-1691:
--

Github user asfgit closed the pull request at:

https://github.com/apache/avro/pull/57


> Error parsing schema if schema is json string
> -
>
> Key: AVRO-1691
> URL: https://issues.apache.org/jira/browse/AVRO-1691
> Project: Avro
>  Issue Type: Bug
>  Components: c
>Affects Versions: 1.7.7
>Reporter: Vikas Kumar
> Fix For: 1.8.0
>
> Attachments: AVRO-1691.patch
>
>
> I have a schema which looks like:
> "int"
> in file_read_header , I got an error: Cannot parse file header: Error parsing 
> JSON: '[' or '{' expected near '"int"'
> I see avro-c uses json_loadb from jansson which may be populating this error.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] avro pull request: AVRO-1762. Java: Put additional objects into Ve...

[embs]

GitHub user embs opened a pull request:

https://github.com/apache/avro/pull/71

AVRO-1762. Java: Put additional objects into Velocity template

Refer to [AVRO-1762](https://issues.apache.org/jira/browse/AVRO-1762) for 
more information.

(this PR was previously #59)

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/geteloquent/avro 
AVRO-1762-velocity-custom-objects

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/avro/pull/71.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #71


commit 1b5c7198bcc19db607cfd0031aa20c950460fc4f
Author: embs 
Date:   2015-11-25T18:57:49Z

AVRO-1762. Java: Put additional objects into Velocity template

It provides more flexibility when generating code with custom Velocity
templates.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] avro pull request: AVRO-1493: Java: Schema fingerprint vary by loc...

[krschultz]

GitHub user krschultz opened a pull request:

https://github.com/apache/avro/pull/69

AVRO-1493: Java: Schema fingerprint vary by locale

fixes https://issues.apache.org/jira/browse/AVRO-1493

was originally https://github.com/apache/avro/pull/63 before the SVN -> git 
migration

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/krschultz/avro AVRO-1493

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/avro/pull/69.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #69


commit e7de3f850f66afbb72813e542c21e45d3bf670e6
Author: Kevin Schultz 
Date:   2015-12-09T21:01:59Z

AVRO-1493: Java: Schema fingerprint vary by locale




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (AVRO-1493) Avoid the "Turkish Locale Problem"

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/AVRO-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15133346#comment-15133346
 ] 

ASF GitHub Bot commented on AVRO-1493:
--

GitHub user krschultz opened a pull request:

https://github.com/apache/avro/pull/69

AVRO-1493: Java: Schema fingerprint vary by locale

fixes https://issues.apache.org/jira/browse/AVRO-1493

was originally https://github.com/apache/avro/pull/63 before the SVN -> git 
migration

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/krschultz/avro AVRO-1493

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/avro/pull/69.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #69


commit e7de3f850f66afbb72813e542c21e45d3bf670e6
Author: Kevin Schultz 
Date:   2015-12-09T21:01:59Z

AVRO-1493: Java: Schema fingerprint vary by locale




> Avoid the "Turkish Locale Problem"
> --
>
> Key: AVRO-1493
> URL: https://issues.apache.org/jira/browse/AVRO-1493
> Project: Avro
>  Issue Type: Bug
>  Components: java
>Affects Versions: 1.7.6
> Environment: Hadoop trunk build error on mac-os with turkish locale.
>Reporter: Serkan Taş
> Fix For: 1.7.8
>
>
> Locale dependent String.toUpperCase(), String.toLowerCase() causes unexpected 
> behavior if the the locale is Turkish
> Not sure about String.equalsIgnoreCase(..).
> Here is the error :
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-compiler-plugin:2.5.1:testCompile 
> (default-testCompile) on project hadoop-common: Compilation failure
> [ERROR] 
> /Users/serkan/programlar/dev/hadooptest/hadoop-trunk/hadoop-common-project/hadoop-common/target/generated-test-sources/java/org/apache/hadoop/io/serializer/avro/AvroRecord.java:[10,244]
>  unmappable character for encoding UTF-8
> [ERROR] -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.maven.plugins:maven-compiler-plugin:2.5.1:testCompile 
> (default-testCompile) on project hadoop-common: Compilation failure
> /Users/serkan/programlar/dev/hadooptest/hadoop-trunk/hadoop-common-project/hadoop-common/target/generated-test-sources/java/org/apache/hadoop/io/serializer/avro/AvroRecord.java:[10,244]
>  unmappable character for encoding UTF-8
> I f i check the code i discovered the reason for error :
>  public static final org.apache.avro.Schema SCHEMA$ = new 
> org.apache.avro.Schema.Parser().parse("{\"type\":\"record\",\"name\":\"AvroRecord\",\"namespace\":\"org.apache.hadoop.io.serializer.avro\",\"fields\":[{\"name\":\"intField\",\"type\":\"Ýnt\"}]}");
> For the code generated from schema, locale dependent capitalization of letter 
> "i" turns in to "Ý" should be the same for "I" to "ı".
> Same bug exist in OPENEJB-1071, OAK-260, IBATIS-218.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AVRO-1749) Maven plugin goal: automatic schemas (.avsc) generation from Java classes (.java)

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/AVRO-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15133434#comment-15133434
 ] 

ASF GitHub Bot commented on AVRO-1749:
--

GitHub user embs opened a pull request:

https://github.com/apache/avro/pull/70

AVRO-1749 Java: Introduce induce Maven plugin goal

[AVRO-1749](https://issues.apache.org/jira/browse/AVRO-1749)

Maven plugin goal to induce Avro schemas and protocol from Java classes.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/embs/avro AVRO-1749-induce-mojo

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/avro/pull/70.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #70


commit a7371fadadcb940b95455ad85a48cfed3cfa75c4
Author: embs 
Date:   2016-01-23T15:00:55Z

AVRO-1749 Java: Introduce induce Maven plugin goal




> Maven plugin goal: automatic schemas (.avsc) generation from Java classes 
> (.java)
> -
>
> Key: AVRO-1749
> URL: https://issues.apache.org/jira/browse/AVRO-1749
> Project: Avro
>  Issue Type: New Feature
>  Components: java
>Reporter: Matheus Santana
>Priority: Minor
>
> Current maven plugin includes goals for generating Java code (classes and 
> interfaces) from IDL (.avdl files) and Avro protocol / schemas definitions 
> (.avpr / .avsc).
> It would be nice to provide a goal for automatic [induced schemas from Java 
> code|https://avro.apache.org/docs/current/api/java/org/apache/avro/tool/InduceSchemaTool.html].



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] avro pull request: AVRO-1749 Java: Introduce induce Maven plugin g...

[embs]

GitHub user embs opened a pull request:

https://github.com/apache/avro/pull/70

AVRO-1749 Java: Introduce induce Maven plugin goal

[AVRO-1749](https://issues.apache.org/jira/browse/AVRO-1749)

Maven plugin goal to induce Avro schemas and protocol from Java classes.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/embs/avro AVRO-1749-induce-mojo

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/avro/pull/70.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #70


commit a7371fadadcb940b95455ad85a48cfed3cfa75c4
Author: embs 
Date:   2016-01-23T15:00:55Z

AVRO-1749 Java: Introduce induce Maven plugin goal




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (AVRO-1762) Allow putting additional objects into the Velocity template

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/AVRO-1762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15133440#comment-15133440
 ] 

ASF GitHub Bot commented on AVRO-1762:
--

GitHub user embs opened a pull request:

https://github.com/apache/avro/pull/71

AVRO-1762. Java: Put additional objects into Velocity template

Refer to [AVRO-1762](https://issues.apache.org/jira/browse/AVRO-1762) for 
more information.

(this PR was previously #59)

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/geteloquent/avro 
AVRO-1762-velocity-custom-objects

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/avro/pull/71.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #71


commit 1b5c7198bcc19db607cfd0031aa20c950460fc4f
Author: embs 
Date:   2015-11-25T18:57:49Z

AVRO-1762. Java: Put additional objects into Velocity template

It provides more flexibility when generating code with custom Velocity
templates.




> Allow putting additional objects into the Velocity template
> ---
>
> Key: AVRO-1762
> URL: https://issues.apache.org/jira/browse/AVRO-1762
> Project: Avro
>  Issue Type: Improvement
>  Components: java
>Reporter: Matheus Santana
> Attachments: AVRO-1762.patch
>
>
> This JIRA proposes the ability to inject custom POJOs into the Velocity 
> template.
> It is possible [to override template directory 
> configuration|https://issues.apache.org/jira/browse/AVRO-963?jql=project%20%3D%20AVRO%20AND%20component%20%3D%20java%20AND%20text%20~%20%22template%22]
>  and thus make the compiler to generate customized code. However, 
> customization possibilities are constrained to [Velocity Template 
> Language|https://velocity.apache.org/engine/releases/velocity-1.5/user-guide.html#velocity_template_language_vtl:_an_introduction]
>  and [objects 
> injected|https://github.com/apache/avro/blob/trunk/lang/java/compiler/src/main/java/org/apache/avro/compiler/specific/SpecificCompiler.java#L339-L340]
>  into the template's context.
> The ability of injecting custom objects into the template's context would 
> leverage customization possibilities to the whole Java language itself. The 
> patch I'm about to attach modifies both compiler and maven-plugin in order to 
> provide client applications with the ability of easy injecting custom Java 
> objects into the Velocity templates' context.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AVRO-1793) Python2: Retain stack trace and original exception when failing to parse schema

[Matthieu Monsch (JIRA)]

[ 
https://issues.apache.org/jira/browse/AVRO-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15133735#comment-15133735
 ] 

Matthieu Monsch commented on AVRO-1793:
---

Thanks Jakob! Do you know if we should we wait for more reviews or commit this 
patch now? (I'm new here so not sure of the usual procedure.)

> Python2: Retain stack trace and original exception when failing to parse 
> schema
> ---
>
> Key: AVRO-1793
> URL: https://issues.apache.org/jira/browse/AVRO-1793
> Project: Avro
>  Issue Type: Improvement
>  Components: python
>Affects Versions: 1.8.0
>Reporter: Jakob Homan
>Assignee: Jakob Homan
> Attachments: AVRO-1793-2.patch, AVRO-1793.patch
>
>
> Currently when a parse call fails the original exception is swallowed and 
> replaced by a generic SchemaParseException.  We should keep the original 
> stack trace and include the actual exception message.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AVRO-1778) IPC/RPC for JavaScript

[Matthieu Monsch (JIRA)]

[ 
https://issues.apache.org/jira/browse/AVRO-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15133732#comment-15133732
 ] 

Matthieu Monsch commented on AVRO-1778:
---

Thanks Ryan. Will do. Awesome for the move to git!

> IPC/RPC for JavaScript
> --
>
> Key: AVRO-1778
> URL: https://issues.apache.org/jira/browse/AVRO-1778
> Project: Avro
>  Issue Type: Improvement
>  Components: javascript
>Reporter: Matthieu Monsch
>Assignee: Ryan Blue
> Attachments: AVRO-1778.patch
>
>
> This patch adds protocols to the JavaScript implementation.
> The API was designed to:
> + Be simple and idiomatic. The `Protocol` class added here is heavily 
> inspired by node.js' core `EventEmitter` to keep things as familiar as 
> possible [1]. Getting a client and server working is straightforward and 
> requires very few lines of code [2].
> + Support arbitrary transports, both stateful and stateless. Built-in node.js 
> streams are supported out of the box (e.g. TCP/UNIX sockets, or even 
> stdin/stdout). Exchanging messages over a custom transport requires 
> implementing a single simple function (see [3] for an example).
> + Work both server-side and in the browser!
> Ps: I also tested against both the Java and Python implementations over HTTP 
> and communication worked. 
> [1] https://github.com/mtth/avsc/wiki/API#ipc--rpc
> [2] https://github.com/mtth/avsc/wiki/Advanced-usage#remote-procedure-calls
> [3] https://github.com/mtth/avsc/wiki/Advanced-usage#transient-streams



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AVRO-1778) IPC/RPC for JavaScript

[Ryan Blue (JIRA)]

[ 
https://issues.apache.org/jira/browse/AVRO-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15132969#comment-15132969
 ] 

Ryan Blue commented on AVRO-1778:
-

+1. Thanks for the quick replies to my questions, [~mtth]. Since you're a 
committer now, can you commit the patch?

> IPC/RPC for JavaScript
> --
>
> Key: AVRO-1778
> URL: https://issues.apache.org/jira/browse/AVRO-1778
> Project: Avro
>  Issue Type: Improvement
>  Components: javascript
>Reporter: Matthieu Monsch
>Assignee: Ryan Blue
> Attachments: AVRO-1778.patch
>
>
> This patch adds protocols to the JavaScript implementation.
> The API was designed to:
> + Be simple and idiomatic. The `Protocol` class added here is heavily 
> inspired by node.js' core `EventEmitter` to keep things as familiar as 
> possible [1]. Getting a client and server working is straightforward and 
> requires very few lines of code [2].
> + Support arbitrary transports, both stateful and stateless. Built-in node.js 
> streams are supported out of the box (e.g. TCP/UNIX sockets, or even 
> stdin/stdout). Exchanging messages over a custom transport requires 
> implementing a single simple function (see [3] for an example).
> + Work both server-side and in the browser!
> Ps: I also tested against both the Java and Python implementations over HTTP 
> and communication worked. 
> [1] https://github.com/mtth/avsc/wiki/API#ipc--rpc
> [2] https://github.com/mtth/avsc/wiki/Advanced-usage#remote-procedure-calls
> [3] https://github.com/mtth/avsc/wiki/Advanced-usage#transient-streams



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AVRO-1794) Update docs after migration to git

[Ryan Blue (JIRA)]

Ryan Blue created AVRO-1794:
---

 Summary: Update docs after migration to git
 Key: AVRO-1794
 URL: https://issues.apache.org/jira/browse/AVRO-1794
 Project: Avro
  Issue Type: Task
  Components: doc
Reporter: Ryan Blue


The [vote to move to 
git|https://mail-archives.apache.org/mod_mbox/avro-dev/201602.mbox/%3C56AFB9B9.8000304%40apache.org%3E]
 just passed. Once the INFRA ticket is completed, we will need to [update 
docs|https://avro.apache.org/version_control.html].



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)