-
-
Notifications
You must be signed in to change notification settings - Fork 265
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reading messages from a C# producer #409
Comments
Does the rest of the data look fine? |
In most cases no :( The rest data looks like �Ĥ��� till the end of body. |
are you maybe using compression in c# and did not configure it on the php side? |
Compression? Hmm.. Could you please point me to the manuals describing this? |
php-rdkafka is basically just a wrapper around librdkafka, configuration settings can be found here: |
Unfortunately no. |
I see the official C# client is also just a wrapper for librdkafka, so i am sure we can get it to work. Do you use avro schemas for producing messages? |
I think it's just the fact that C# in this case saves floating point number in binary format, which is not something PHP can recover on it's own (@dobryakov even mentioned that exponent has to be known). I think your library @nick-zh (https://github.com/jobcloud/php-kafka-lib) supports avro schemas, so it might work in this case? |
@nick-zh @Steveb-p We are using jobcloud library too. Doesn't work out-of-the-box at the moment. We use the hack with |
Thx guys for the feedback, i will have some time over the holidays, but there are a lot of topics i want to tackle, so can't promise anything. But i will try to find out where stuff is being done differently and if we can recover from it. |
Hello, we have a problem with decoding messages containing Decimal values (in terms of C# data types).
For example, when producer (based on C# application) send us value like "1234.56", we receive message and get in PHP data something like "\000\000\000\000�Ĥ���]Hf47b6ffc".
Is there any idea how to solve it?
The text was updated successfully, but these errors were encountered: