Data and AI struggles

1,730 problems · 342 companies

Databases

Queries run too slowly and are hard to tune

5 posts from 5 people5d activeSteady, +1 this week

Posts per day

Posts per day5 posts, Sep 18 to Nov 9

The posts behind it

GitHub issuesapache/superset · iyamgNov 5

missing a `dttm` index on `logs` table results in full table scan when visiting Activity Log

### Bug description * For the activity log page, the request is `GET /api/v1/log/` ordered by `dttm desc` (`ORDER BY dttm DESC LIMIT 25`) * The only index on `logs` is `(user_id, dttm)`, from migration `cdcf3d64daf4` * Therefore, visiting the activity page causes full table...

Stack OverflowStack Overflow [databricks] · HomboyNov 2

Does the order of columns matter in Liquid Clustered Tables in Databricks?

In Databricks, when working with Liquid Clustered Tables, does the order in which columns are specified in the CLUSTER BY clause matter?. For example, are the following two statements equivalent in terms of data organization and query performance?. CREATE TABLE table1 (...)...

1 replies
GitHub issuesduckdb/duckdb · h4nsmullerOct 13

SELECT DISTINCT / GROUP BY on a VARIANT column is 10-15x slower than on the equivalent STRUCT: first() round-trips the physical VARIANT through create_sort_key (1.2 KB per row) on top of the variant_comparator collation key

### What happens? `SELECT DISTINCT v FROM t` over a VARIANT column holding a 28-field object (built with `struct_pack(...)::VARIANT`) on 1 M rows takes 9.4 s wall / 32 s CPU with 4 threads (39 s wall single-threaded), while the same query over the STRUCT column the VARIANT was...

GitHub issuesClickHouse/ClickHouse · alexey-milovidovOct 12

BigQuery is slow

# `bigquery()` reads through `tabledata.list`, which makes wide tables unusable ## The finding The `bigquery()` table function reads **23 rows per second** from `chrome-ux-report.all.202501`, a 26-million-row table. Not 23 thousand. At that rate the table takes **13 days**, and...

GitHub issuesmicrosoft/semantic-kernel · ericdeloreficeSep 24

Python: RedisCollection.ensure_collection_deleted can return successfully without deleting the index

### Describe the bug `RedisCollection.ensure_collection_deleted` can return successfully without deleting anything. `collection_exists()` reaches Redis to answer, so it can fail for reasons unrelated to whether the index is there - a timeout, an authentication failure, an...

Companies and products named

1 post
1 post
1 post
1 post
About this problem

Evidence

5 posts from 5 people in 5 places, about 1 a week over 43 days. Mostly on microsoft/semantic-kernel, duckdb/duckdb, ClickHouse/ClickHouse. Tools named alongside: Redis, DuckDB, AWS, BigQuery.

Frustration Frustration 2 of 3· Seen on GitHub issues, Stack Overflow

How it was grouped

Posts that state a pain and match the "slow-queries" rule. First post Sep 24, 2026, latest Nov 5, 2026. Corroborated: 3 or more posts from 2 or more people or places. Method

The same problem elsewhere

PostgreSQL queries run too slowly and are hard to tune

8 posts from 8 people on Reddit, Stack Overflow, GitHub issues.

ClickHouse queries run too slowly and are hard to tune

3 posts from 2 people on GitHub issues.

History

Momentum went from rising to steady.

Nov 9, 2026

Momentum went from steady to rising.

Nov 6, 2026

Momentum went from fading to steady.

Nov 4, 2026

Momentum went from steady to fading.

Oct 20, 2026

Corroborated: 3 or more posts from 2 or more people or places.

Oct 15, 2026

Momentum went from fading to steady.

Oct 15, 2026

Momentum went from steady to fading.

Oct 13, 2026

Momentum went from fading to steady.

Oct 9, 2026

Momentum went from new to fading.

Oct 2, 2026

Momentum went from fading to new.

Sep 27, 2026

First seen with 1 post.

Sep 25, 2026