ka-weihe

icon indicating an email [email protected]

icon location Copenhagen, Denmark

Results 9 comments of ka-weihe

Update benchmarks

@gustf

Update benchmarks

Any updates on this? @gustf

Terribly slow

I have created an implementation that is quite a lot faster than js-levenshtein. Take a look: https://github.com/ka-weihe/fastest-levenshtein

Retry model on connection errors

Does it actually retry after the initial connection for you guys? https://github.com/dbt-msft/dbt-sqlserver/issues/507

Native filters doesn't update their cached values after Refresh Dashboard

@rusackas This is still an issue in Superset 4.0.1. Can you open the issue again?

Meta node can only handle ~600 Kafka sources.

Thank you for the detailed response! A few follow-up questions: 1. **Why does it create a consumer per source, even when unused?** It seems that each `KafkaSplitEnumerator` creates its own...

Meta node can only handle ~600 Kafka sources.

> This seems to be the Kafka library's limitation. Even just for fetching metadata, we need to create consumers. And the consumers will immediately connect to all brokers (instead of...

Meta node can only handle ~600 Kafka sources.

@xxchan The Reusable Source Executor seems like a great step forward, especially for consolidating multiple topics through a shared topic. However, it doesn't fully address the issue of resource constraints...

Meta node can only handle ~600 Kafka sources.

@xxchan I don’t quite understand what you mean by “supported client reuse on Meta.” Could you elaborate on how this works and how it impacts the resource utilization issues we've...