AnsweredAssumed Answered exposes symbols from internal protobuffer library

Question asked by heathbar on Apr 12, 2013
Latest reply on Apr 15, 2013 by heathbar
The shared library seems to export not only symbols required for the public api, but also symbols from a library used internally (protocol buffers).  This causes symbol collisions when a user's  code uses a newer version of the popular protocolbuffers library.  A workaround is for the user to revert to the older version to match the version used internally by mapr.  Unfortunately protocol buffers 2.4.1 is missing some useful features... like pickle support in the python API. 

It would be nice if the library was compiled to expose only the symbols required by the public API so the user is not forced to use an old version of protocol buffers in their own codebase.

Can I request a formal bug-fix ticket for this issue?