Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Low performance while using `latest` as `schema.id`
See original GitHub issueLooks like SchemaLoader uses unchached call to get the latest version id:
This happens quite often and results in a huge amount of http requests to schema registry. This value could be cached for some time period, and the time period should be configurable.
Issue Analytics
- State:
- Created 3 years ago
- Comments:15 (1 by maintainers)
Top Results From Across the Web
Docs: clarify semantics of schema ids? · Issue #158 - GitHub
@miguno I think one potential problem in trying to use schema IDs for ... In that case, the concept of asking for the...
Read more >17 Ways to Mess Up Self-Managed Schema Registry - Confluent
If there isn't, it is possible to end up with duplicate schema IDs, depending on the view of the current primary instance. Mistake...
Read more >Schema Inference With ID - ksqlDB Documentation
Here's what you can do with schema inference with IDs in ksqlDB: Declare streams and tables on Kafka topics with supported key and...
Read more >Replicate Avro Messages To Target, Conflicting Schema ...
Is it ok to copy the topic with Replicator when the target schema registry has the same schema ID but with a different...
Read more >Monitor performance by using the Query Store - SQL Server
x), SQL Server 2017 (14.x), SQL Server 2019 (15.x). It is enabled by default in the READ_WRITE mode for new databases starting with...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hi @agolovenko , my comments on your comments.
The method you’re referring to is
getLatestSchemaMetadata, right? This oneIf yes, then of course it has to constantly query Schema Registry for the latest version, however, this only happens when getting the schema to be used by Catalyst, as you can browse here to confirm
The subsequent calls can and must be cached since they are based on the id available on top of the payload for each record, as you can see here
Anyway, thank you very much for coming back and we’ll soon release an improvement for this.
You are welcome. Since there seems to be no issue any more, I’m closing this ticket. Please open a new one if you have any problems.