Queries regarding the Java ResolvingDecoder cache

[Achanta Vamsi]

Hi,

Currently in GenericDatumReader, whenever a ResolvingDecoder is
constructed, a ThreadLocal cache with a WeakHashMap is used to cache the
resolver. The getResolver() api is currently marked as Unstable.

In a scenario when the Schemas are huge (10^6 chars and deeply nested) and
there are lots of threads, this leads to lot of memory usage and frequent
garbage collections.

Could someone help me with how to go about in such a scenario - can we
write a concurrent cache with still Identity values and be functionally
correct?
Or should I use a limited no of threads always when using
GenericDatumReader so that the memory increase is controlled?

Please suggest.
-- 
Thanks
Vamsi

[jira] [Commented] (AVRO-1989) Ruby schema validation for fixed types should use bytesize in error message

[Hudson (JIRA)]

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

Hudson commented on AVRO-1989:
--

SUCCESS: Integrated in Jenkins build AvroJava #606 (See 
[https://builds.apache.org/job/AvroJava/606/])
AVRO-1989: Ruby schema validation should  use bytesize in error msg (github: 
[https://github.com/apache/avro/commit/c62a8f9d11c85c18a9df1f28d23fe0396f7766b9])
* (edit) lang/ruby/lib/avro/schema_validator.rb
* (edit) lang/ruby/test/test_schema_validator.rb


> Ruby schema validation for fixed types should use bytesize in error message
> ---
>
> Key: AVRO-1989
> URL: https://issues.apache.org/jira/browse/AVRO-1989
> Project: Apache Avro
>  Issue Type: Bug
>  Components: ruby
>Affects Versions: 1.9.0
>Reporter: Sean Busbey
>Assignee: Fokko Driesprong
>Priority: Minor
> Fix For: 1.9.0
>
> Attachments: AVRO-1989.0.patch
>
>
> From AVRO-1886:
> I'd like to get one thing improved, but it's fine as a follow-on.
> {code}
>  +   when :fixed
>  +  if datum.is_a? String
>  +message = "expected fixed with size #{expected_schema.size}, 
> got \"#{datum}\" with size #{datum.size}"
>  +result.add_error(path, message) unless datum.bytesize == 
> expected_schema.size
>  +  else
>  +result.add_error(path, "expected fixed with size 
> #{expected_schema.size}, got #{actual_value_message(datum)}")
>  +  end
> {code}
> the message here should use datum.bytesize instead of datum.size.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (AVRO-1989) Ruby schema validation for fixed types should use bytesize in error message

[Fokko Driesprong (JIRA)]

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

Fokko Driesprong reassigned AVRO-1989:
--

Assignee: Fokko Driesprong  (was: Sean Busbey)

> Ruby schema validation for fixed types should use bytesize in error message
> ---
>
> Key: AVRO-1989
> URL: https://issues.apache.org/jira/browse/AVRO-1989
> Project: Apache Avro
>  Issue Type: Bug
>  Components: ruby
>Affects Versions: 1.9.0
>Reporter: Sean Busbey
>Assignee: Fokko Driesprong
>Priority: Minor
> Fix For: 1.9.0
>
> Attachments: AVRO-1989.0.patch
>
>
> From AVRO-1886:
> I'd like to get one thing improved, but it's fine as a follow-on.
> {code}
>  +   when :fixed
>  +  if datum.is_a? String
>  +message = "expected fixed with size #{expected_schema.size}, 
> got \"#{datum}\" with size #{datum.size}"
>  +result.add_error(path, message) unless datum.bytesize == 
> expected_schema.size
>  +  else
>  +result.add_error(path, "expected fixed with size 
> #{expected_schema.size}, got #{actual_value_message(datum)}")
>  +  end
> {code}
> the message here should use datum.bytesize instead of datum.size.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (AVRO-1989) Ruby schema validation for fixed types should use bytesize in error message

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on AVRO-1989:
---

Commit c62a8f9d11c85c18a9df1f28d23fe0396f7766b9 in avro's branch 
refs/heads/master from Fokko Driesprong
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=c62a8f9 ]

AVRO-1989: Ruby schema validation should  use bytesize in error msg (#451)

* AVRO-1989: Ruby schema validation should use bytesize in error msg

* AVRO-1989: Add a test to verify the behaviour

* AVRO-1989: Add a test to verify the behaviour


> Ruby schema validation for fixed types should use bytesize in error message
> ---
>
> Key: AVRO-1989
> URL: https://issues.apache.org/jira/browse/AVRO-1989
> Project: Apache Avro
>  Issue Type: Bug
>  Components: ruby
>Affects Versions: 1.9.0
>Reporter: Sean Busbey
>Assignee: Fokko Driesprong
>Priority: Minor
> Fix For: 1.9.0
>
> Attachments: AVRO-1989.0.patch
>
>
> From AVRO-1886:
> I'd like to get one thing improved, but it's fine as a follow-on.
> {code}
>  +   when :fixed
>  +  if datum.is_a? String
>  +message = "expected fixed with size #{expected_schema.size}, 
> got \"#{datum}\" with size #{datum.size}"
>  +result.add_error(path, message) unless datum.bytesize == 
> expected_schema.size
>  +  else
>  +result.add_error(path, "expected fixed with size 
> #{expected_schema.size}, got #{actual_value_message(datum)}")
>  +  end
> {code}
> the message here should use datum.bytesize instead of datum.size.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (AVRO-1989) Ruby schema validation for fixed types should use bytesize in error message

[Fokko Driesprong (JIRA)]

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

Fokko Driesprong updated AVRO-1989:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Ruby schema validation for fixed types should use bytesize in error message
> ---
>
> Key: AVRO-1989
> URL: https://issues.apache.org/jira/browse/AVRO-1989
> Project: Apache Avro
>  Issue Type: Bug
>  Components: ruby
>Affects Versions: 1.9.0
>Reporter: Sean Busbey
>Assignee: Fokko Driesprong
>Priority: Minor
> Fix For: 1.9.0
>
> Attachments: AVRO-1989.0.patch
>
>
> From AVRO-1886:
> I'd like to get one thing improved, but it's fine as a follow-on.
> {code}
>  +   when :fixed
>  +  if datum.is_a? String
>  +message = "expected fixed with size #{expected_schema.size}, 
> got \"#{datum}\" with size #{datum.size}"
>  +result.add_error(path, message) unless datum.bytesize == 
> expected_schema.size
>  +  else
>  +result.add_error(path, "expected fixed with size 
> #{expected_schema.size}, got #{actual_value_message(datum)}")
>  +  end
> {code}
> the message here should use datum.bytesize instead of datum.size.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (AVRO-1989) Ruby schema validation for fixed types should use bytesize in error message

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on AVRO-1989:
---

Commit c62a8f9d11c85c18a9df1f28d23fe0396f7766b9 in avro's branch 
refs/heads/master from Fokko Driesprong
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=c62a8f9 ]

AVRO-1989: Ruby schema validation should  use bytesize in error msg (#451)

* AVRO-1989: Ruby schema validation should use bytesize in error msg

* AVRO-1989: Add a test to verify the behaviour

* AVRO-1989: Add a test to verify the behaviour


> Ruby schema validation for fixed types should use bytesize in error message
> ---
>
> Key: AVRO-1989
> URL: https://issues.apache.org/jira/browse/AVRO-1989
> Project: Apache Avro
>  Issue Type: Bug
>  Components: ruby
>Affects Versions: 1.9.0
>Reporter: Sean Busbey
>Assignee: Fokko Driesprong
>Priority: Minor
> Fix For: 1.9.0
>
> Attachments: AVRO-1989.0.patch
>
>
> From AVRO-1886:
> I'd like to get one thing improved, but it's fine as a follow-on.
> {code}
>  +   when :fixed
>  +  if datum.is_a? String
>  +message = "expected fixed with size #{expected_schema.size}, 
> got \"#{datum}\" with size #{datum.size}"
>  +result.add_error(path, message) unless datum.bytesize == 
> expected_schema.size
>  +  else
>  +result.add_error(path, "expected fixed with size 
> #{expected_schema.size}, got #{actual_value_message(datum)}")
>  +  end
> {code}
> the message here should use datum.bytesize instead of datum.size.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (AVRO-1989) Ruby schema validation for fixed types should use bytesize in error message

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on AVRO-1989:
---

Commit c62a8f9d11c85c18a9df1f28d23fe0396f7766b9 in avro's branch 
refs/heads/master from Fokko Driesprong
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=c62a8f9 ]

AVRO-1989: Ruby schema validation should  use bytesize in error msg (#451)

* AVRO-1989: Ruby schema validation should use bytesize in error msg

* AVRO-1989: Add a test to verify the behaviour

* AVRO-1989: Add a test to verify the behaviour


> Ruby schema validation for fixed types should use bytesize in error message
> ---
>
> Key: AVRO-1989
> URL: https://issues.apache.org/jira/browse/AVRO-1989
> Project: Apache Avro
>  Issue Type: Bug
>  Components: ruby
>Affects Versions: 1.9.0
>Reporter: Sean Busbey
>Assignee: Fokko Driesprong
>Priority: Minor
> Fix For: 1.9.0
>
> Attachments: AVRO-1989.0.patch
>
>
> From AVRO-1886:
> I'd like to get one thing improved, but it's fine as a follow-on.
> {code}
>  +   when :fixed
>  +  if datum.is_a? String
>  +message = "expected fixed with size #{expected_schema.size}, 
> got \"#{datum}\" with size #{datum.size}"
>  +result.add_error(path, message) unless datum.bytesize == 
> expected_schema.size
>  +  else
>  +result.add_error(path, "expected fixed with size 
> #{expected_schema.size}, got #{actual_value_message(datum)}")
>  +  end
> {code}
> the message here should use datum.bytesize instead of datum.size.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (AVRO-2321) Replace hasattr with getattr

[Hudson (JIRA)]

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

Hudson commented on AVRO-2321:
--

SUCCESS: Integrated in Jenkins build AvroJava #605 (See 
[https://builds.apache.org/job/AvroJava/605/])
AVRO-2321: Avoid hasattr in Python 2 (#453) (fokko: 
[https://github.com/apache/avro/commit/2aa4946f42541369b31094538801c2caec251c67])
* (edit) lang/py/src/avro/protocol.py
* (edit) lang/py/src/avro/schema.py


> Replace hasattr with getattr
> 
>
> Key: AVRO-2321
> URL: https://issues.apache.org/jira/browse/AVRO-2321
> Project: Apache Avro
>  Issue Type: Improvement
>  Components: python
>Affects Versions: 1.8.2
>Reporter: Fokko Driesprong
>Assignee: Michael A. Smith
>Priority: Major
> Fix For: 1.9.0
>
>
> Please refer to the blog: https://hynek.me/articles/hasattr/



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (AVRO-2321) Replace hasattr with getattr

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on AVRO-2321:
---

Commit 2aa4946f42541369b31094538801c2caec251c67 in avro's branch 
refs/heads/master from Michael A. Smith
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=2aa4946 ]

AVRO-2321: Avoid hasattr in Python 2 (#453)



> Replace hasattr with getattr
> 
>
> Key: AVRO-2321
> URL: https://issues.apache.org/jira/browse/AVRO-2321
> Project: Apache Avro
>  Issue Type: Improvement
>  Components: python
>Affects Versions: 1.8.2
>Reporter: Fokko Driesprong
>Assignee: Michael A. Smith
>Priority: Major
> Fix For: 1.9.0
>
>
> Please refer to the blog: https://hynek.me/articles/hasattr/



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (AVRO-1816) Add support for logical decimal type for python AVRO

[Hudson (JIRA)]

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

Hudson commented on AVRO-1816:
--

SUCCESS: Integrated in Jenkins build AvroJava #604 (See 
[https://builds.apache.org/job/AvroJava/604/])
[AVRO-1816] Add support for logical decimal type for python AVRO (#82) (fokko: 
[https://github.com/apache/avro/commit/114fee5317ca2bb2b09864c66da99e86190faffb])
* (edit) lang/py/src/avro/io.py
* (edit) lang/py/test/test_io.py
* (edit) lang/py/test/test_schema.py
* (edit) lang/py/src/avro/schema.py
* (add) lang/py/src/avro/decimal_encoder.py
[AVRO-1816] Add support for logical decimal type for python AVRO 
(fokkodriesprong: 
[https://github.com/apache/avro/commit/e44acccf69a0b40f12f904144df67b345a5138ad])
* (delete) lang/py/src/avro/decimal_encoder.py


> Add support for logical decimal type for python AVRO
> 
>
> Key: AVRO-1816
> URL: https://issues.apache.org/jira/browse/AVRO-1816
> Project: Apache Avro
>  Issue Type: New Feature
>  Components: python
>Affects Versions: 1.9.0
>Reporter: Prem Santosh
>Assignee: Prem Santosh
>Priority: Major
> Fix For: 1.9.0
>
>
> Currently, python Avro does not seem to support a DECIMAL type. 
> I 
> [added|https://github.com/premsantosh/avro/commit/162bbb73bdb09c197722f33a0b4dcaf9f7c6f9b8]
>  support for encoding and decoding logical decimal type for python avro.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Jenkins build is back to normal : AvroJava #604

[Apache Jenkins Server]

See 

[jira] [Commented] (AVRO-1816) Add support for logical decimal type for python AVRO

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on AVRO-1816:
---

Commit 114fee5317ca2bb2b09864c66da99e86190faffb in avro's branch 
refs/heads/master from Prem Santosh
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=114fee5 ]

[AVRO-1816] Add support for logical decimal type for python AVRO (#82)

* Added decimal logical type support for python avro

* Fixed issues with encoder and decoder [variable length]

* Revamped logical schema design

* Fixed bug with bytes packed in decimal encoder

* Fixed exponent scale


> Add support for logical decimal type for python AVRO
> 
>
> Key: AVRO-1816
> URL: https://issues.apache.org/jira/browse/AVRO-1816
> Project: Apache Avro
>  Issue Type: New Feature
>  Components: python
>Affects Versions: 1.9.0
>Reporter: Prem Santosh
>Assignee: Prem Santosh
>Priority: Major
> Fix For: 1.9.0
>
>
> Currently, python Avro does not seem to support a DECIMAL type. 
> I 
> [added|https://github.com/premsantosh/avro/commit/162bbb73bdb09c197722f33a0b4dcaf9f7c6f9b8]
>  support for encoding and decoding logical decimal type for python avro.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (AVRO-1816) Add support for logical decimal type for python AVRO

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on AVRO-1816:
---

Commit e44acccf69a0b40f12f904144df67b345a5138ad in avro's branch 
refs/heads/master from Fokko Driesprong
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=e44accc ]

[AVRO-1816] Add support for logical decimal type for python AVRO

Remove empty file


> Add support for logical decimal type for python AVRO
> 
>
> Key: AVRO-1816
> URL: https://issues.apache.org/jira/browse/AVRO-1816
> Project: Apache Avro
>  Issue Type: New Feature
>  Components: python
>Affects Versions: 1.9.0
>Reporter: Prem Santosh
>Assignee: Prem Santosh
>Priority: Major
> Fix For: 1.9.0
>
>
> Currently, python Avro does not seem to support a DECIMAL type. 
> I 
> [added|https://github.com/premsantosh/avro/commit/162bbb73bdb09c197722f33a0b4dcaf9f7c6f9b8]
>  support for encoding and decoding logical decimal type for python avro.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (AVRO-1816) Add support for logical decimal type for python AVRO

[Fokko Driesprong (JIRA)]

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

Fokko Driesprong updated AVRO-1816:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Add support for logical decimal type for python AVRO
> 
>
> Key: AVRO-1816
> URL: https://issues.apache.org/jira/browse/AVRO-1816
> Project: Apache Avro
>  Issue Type: New Feature
>  Components: python
>Affects Versions: 1.9.0
>Reporter: Prem Santosh
>Assignee: Prem Santosh
>Priority: Major
> Fix For: 1.9.0
>
>
> Currently, python Avro does not seem to support a DECIMAL type. 
> I 
> [added|https://github.com/premsantosh/avro/commit/162bbb73bdb09c197722f33a0b4dcaf9f7c6f9b8]
>  support for encoding and decoding logical decimal type for python avro.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (AVRO-2321) Replace hasattr with getattr

[Fokko Driesprong (JIRA)]

Fokko Driesprong created AVRO-2321:
--

 Summary: Replace hasattr with getattr
 Key: AVRO-2321
 URL: https://issues.apache.org/jira/browse/AVRO-2321
 Project: Apache Avro
  Issue Type: Improvement
  Components: python
Affects Versions: 1.8.2
Reporter: Fokko Driesprong
Assignee: Michael A. Smith
 Fix For: 1.9.0


Please refer to the blog: https://hynek.me/articles/hasattr/



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (AVRO-1343) Python: validate too permissive on records with extra fields

[Fokko Driesprong (JIRA)]

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

Fokko Driesprong updated AVRO-1343:
---
Fix Version/s: (was: 1.9.0)
   1.10.0

> Python: validate too permissive on records with extra fields
> 
>
> Key: AVRO-1343
> URL: https://issues.apache.org/jira/browse/AVRO-1343
> Project: Apache Avro
>  Issue Type: Bug
>  Components: python
>Reporter: Jeremy Kahn
>Assignee: Jeremy Kahn
>Priority: Major
> Fix For: 1.10.0
>
> Attachments: AVRO-1343-tests.patch, AVRO-1343-validate.patch
>
>
> Python's validator silently accepts (generic) records with extra fields and 
> considers them valid.
> For example, {{io.validate}} silently considers that the schema:
> {noformat}{"type": "record",
>  "name": "Test",
>  "fields": [{"name": "f", "type": "long"}]}
> {noformat}
> should accept records like:
> {noformat}{'f': 5, 'extra_field': "abc"}{noformat}
> but this is problematic.
> This is *especially* problematic for encoding unions, because internally the 
> Python serializer uses {{validate}} to find the appropriate schema with which 
> to encode a given object.
> In the current implementation, union schema selection is the *last* schema 
> that {{validate(schema, obj)}} returns {{True}} for.  If {{validate}} isn't 
> picky, this encoding will frequently guess wrong.
> I will attach two patches: one to the tests and one to the {{validate}} 
> function.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (AVRO-1443) SpecificRecord builders should share more functionality with GenericRecord builders

[Fokko Driesprong (JIRA)]

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

Fokko Driesprong updated AVRO-1443:
---
Fix Version/s: (was: 1.9.0)
   1.10.0

> SpecificRecord builders should share more functionality with GenericRecord 
> builders
> ---
>
> Key: AVRO-1443
> URL: https://issues.apache.org/jira/browse/AVRO-1443
> Project: Apache Avro
>  Issue Type: Bug
>  Components: java
>Affects Versions: 1.7.5, 1.7.6
>Reporter: Christophe Taton
>Assignee: Christophe Taton
>Priority: Major
> Fix For: 1.10.0
>
> Attachments: AVRO-1443.20140126-182111-0800.diff, 
> AVRO-1443.20140202-182611-0800.svndiff, AVRO-1443.20140204-124549-0800.diff
>
>
> Ideally, wherever a generic record builder is expected, one should be able to 
> supply a builder for a specific record.
> That could happen by making SpecificRecordBuilderBase (and 
> SpecificErrorBuilderBase?) a subclass of GenericRecordBuilder.
> Since SpecificRecordBase implements GenericRecord, it should be possible with 
> minimal effort.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (AVRO-1435) Convert avro-tools jar to be a bundle.

[Fokko Driesprong (JIRA)]

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

Fokko Driesprong updated AVRO-1435:
---
Fix Version/s: (was: 1.9.0)
   1.10.0

> Convert avro-tools jar to be a bundle.
> --
>
> Key: AVRO-1435
> URL: https://issues.apache.org/jira/browse/AVRO-1435
> Project: Apache Avro
>  Issue Type: Improvement
>  Components: java
>Reporter: Doug Cutting
>Assignee: Doug Cutting
>Priority: Major
> Fix For: 1.10.0
>
> Attachments: AVRO-1435.patch
>
>
> All of the Avro jars except avro-tools were converted to bundles in AVRO-987. 
>  We should probably convert avro-tools-nodeps to be a bundle, since some 
> folks might wish to consume it that way.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (AVRO-1514) Clean up perl API dependencies

[Fokko Driesprong (JIRA)]

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

Fokko Driesprong updated AVRO-1514:
---
Fix Version/s: (was: 1.9.0)
   1.10.0

> Clean up perl API dependencies
> --
>
> Key: AVRO-1514
> URL: https://issues.apache.org/jira/browse/AVRO-1514
> Project: Apache Avro
>  Issue Type: Improvement
>  Components: perl
>Reporter: John Karp
>Assignee: John Karp
>Priority: Minor
> Fix For: 1.10.0
>
> Attachments: AVRO-1514-0.patch
>
>
> If we assume a non-ancient perl (>=5.8.1), we can clean up the dependencies:
> (build) Module::Install: bundle it
> (build) Module::Install::ReadmeFromPod: keep
> (build) Module::Install::Repository: remove, hardcode repository value 
> instead of autodetecting
> (build) Test::More 0.88: keep, but note requisite version built in starting 
> at 5.10.1
> (test) Test::Exception: keep
> (test) Test::Pod: declare (missing in Makefile.PL)
> (test/run) Math::BigInt: don't declare, now built-in
> (run) JSON::XS: replace with JSON to not tie to a backend
> (run) parent: keep, but note built-in starting at 5.10.1
> (run) Compress::Zlib: keep, but note built-in starting at 5.9.3
> (run) IO::String: replace with perl 5.8 functionality
> (run) Encode: don't declare, now built-in
> (run) Regexp::Common: keep
> (run) Object::Tiny: keep
> (run) Try::Tiny: keep



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)