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

ASF GitHub Bot commented on AVRO-2153:
--------------------------------------

thiru-apache commented on issue #294: AVRO-2153 Clearer error msg while parsing 
- specify which node had a …
URL: https://github.com/apache/avro/pull/294#issuecomment-408692300
 
 
   @nicksbyman It looks like `boost::format` does not work in your environment. 
While this patch will fix the specific problem you faced (by sidestepping 
`boost::format`), there are many other places we use `boost::format`. Either we 
get to the bottom of why this does not work in your environment or get rid of 
`boost::format` altogether. I don't think fixing a single instance is a good 
idea.
   
   By the way, I had difficulty creating an Ubuntu instance with boost 1.66.0. 
By any chance is there an AWS AMI with the relevant software that I can use to 
understand the problem better? Thank you.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


> Generating C++ code with avrogencpp produces unclear error message
> ------------------------------------------------------------------
>
>                 Key: AVRO-2153
>                 URL: https://issues.apache.org/jira/browse/AVRO-2153
>             Project: Avro
>          Issue Type: Bug
>          Components: c++
>            Reporter: Nick Byman
>            Priority: Minor
>
> If you put a bad name for a json node in an avro file, you can sometimes get: 
> "Exception: boost::too_many_args: format-string referred", when avro is 
> trying to tell you the name of the bad json node, because the node's name 
> isn't passed to boost::format correctly. 



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

Reply via email to