Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Byte Array raise a problem during consuming #54

Closed
mariomastrodicasa opened this issue Apr 13, 2022 · 1 comment · Fixed by #55
Closed

Byte Array raise a problem during consuming #54

mariomastrodicasa opened this issue Apr 13, 2022 · 1 comment · Fixed by #55
Assignees
@masesdevelopers
Labels
bug Something isn't working

Comments

@mariomastrodicasa
Copy link
Contributor

Describe the bug
Using byte[] creates problem during data extraction.

To Reproduce
Steps to reproduce the behavior:

  1. Use a consumer like KafkaConsumer<int, byte[]>
  2. Try to consume using Poll
  3. When data are received try to get the Value of the ConsumerRecord<int, byte[]>
  4. An exception is raised

Expected behavior
The byte[] received shall be available to the API user.

Desktop (please complete the following information):

  • OS: All
  • Version: latest

Additional context
The exceptions seems be raised from JCOBridge: check if the call wasn't done in the correct way.
@mariomastrodicasa mariomastrodicasa added the bug Something isn't working label Apr 13, 2022
@masesdevelopers
Copy link
Contributor

masesdevelopers commented Apr 13, 2022 •
edited
Loading

The issue comes from JCOBridge itself. When there are generics JVM reports them as java.lang.Object: this java.lang.Object must be analyzed to identify the real object and map it to the correct wrapper.

@masesdevelopers masesdevelopers mentioned this issue Apr 29, 2022
Merged
9 tasks
masesdevelopers added a commit that referenced this issue Apr 29, 2022
@masesdevelopers
Add a benchmark to verify performance (#55)
d98924f 
* Version upgrade

* #54 (comment)

* #53 (#53 (comment)): added comparing benchmark test

* Fix on classes

* #53: Added metrics classes

* Alignment to latest JNet

* #53: Fix file

* CLI improvements

* #53: Benchmark update

* Added command line arg for log path

* Added KNetTopicCopyBenchmark

* Added specialized classes to manage produce/consume

* Upgrade to JNet v1.4.1

* KNetConsumer is marked as evolving

* Fix issue when GC recover objects too early

* Aligned to JNetCore and fix memory management
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@masesdevelopers masesdevelopers

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add a benchmark to verify performance
2 participants
@mariomastrodicasa @masesdevelopers