[
https://issues.apache.org/jira/browse/BEAM-13777?focusedWorklogId=723259&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-723259
]
ASF GitHub Bot logged work on BEAM-13777:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 08/Feb/22 22:57
Start Date: 08/Feb/22 22:57
Worklog Time Spent: 10m
Work Description: OneCricketeer commented on pull request #16652:
URL: https://github.com/apache/beam/pull/16652#issuecomment-1033144523
Were there no tests that were checking this before?
Doesn't seem any tests were added to check this still works.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 723259)
Time Spent: 0.5h (was: 20m)
> confluent schema registry cache capacity
> ----------------------------------------
>
> Key: BEAM-13777
> URL: https://issues.apache.org/jira/browse/BEAM-13777
> Project: Beam
> Issue Type: Bug
> Components: sdk-java-core
> Reporter: Mostafa Aghajani
> Assignee: Mostafa Aghajani
> Priority: P2
> Fix For: 2.37.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Change cache capacity should be specified as input parameter instead of
> default max integer. The usage can be quite different case by case and a
> default Integer max value can lead to error like this depending on the setup:
> {{Exception in thread "main" java.lang.OutOfMemoryError: Java heap space}}
> Some documentation link on the parameter:
> [https://docs.confluent.io/5.4.2/clients/confluent-kafka-dotnet/api/Confluent.SchemaRegistry.CachedSchemaRegistryClient.html#Confluent_SchemaRegistry_CachedSchemaRegistryClient_DefaultMaxCachedSchemas]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
