RequestHunt is a community-driven platform that collects and curates feature requests from X (Twitter), Reddit, and GitHub. We help product teams discover what features real users are asking for, making it easier to validate product ideas and prioritize feature development based on actual user demand.

How does RequestHunt collect feature requests?

RequestHunt uses AI-powered extraction to automatically collect feature requests from social media platforms including X, Reddit, and GitHub. The platform monitors discussions, issues, and posts to identify genuine user feature requests, extracting key information like the requested feature, product mentioned, and user sentiment.

Who uses RequestHunt?

RequestHunt is used by product managers, founders, developers, and product teams who want to discover what features real users are requesting. It's particularly valuable for startups looking to validate ideas, established companies prioritizing their roadmap, and developers building products that solve real user problems.

Is RequestHunt free to use?

Yes, browsing and searching feature requests on RequestHunt is completely free. We also offer API access for developers who want to integrate feature request data into their own applications. Check our pricing page for API plan details.

How often is RequestHunt data updated?

RequestHunt continuously collects feature requests from Reddit, X (Twitter), GitHub, YouTube, LinkedIn, and Amazon. You can also trigger on-demand scraping via the API or web interface to get the freshest data for any topic.

[ClickHouse] Enable Unity Catalog integration for streaming tables and materialized views

Request to allow Unity Catalog integration to read streaming tables and materialized views, addressing the issue of missing storage locations.

Original Source

@@samuelperezh | 0 pts | 3/13/2026

### Company or project name _No response_ ### Describe the unexpected behaviour When using the DataLakeCatalog engine with Databricks Unity Catalog, ClickHouse cannot read streaming tables (TABLE_STREAMING_LIVE_TABLE) or materialized views (TABLE_MATERIALIZED_VIEW). These table types are excluded from READABLE_TABLES and their storage location is stored in the properties JSON field rather than the top-level storage_location field, so ClickHouse fails to resolve where the data lives. ### Which ClickHouse versions are affected? All versions ### How to reproduce 1. Create a database using the DataLakeCatalog engine pointing to a Databricks Unity Catalog endpoint `CREATE DATABASE database ENGINE = DataLakeCatalog('databricks_workspace_url') SETTINGS warehouse = 'warehouse', catalog_credential = 'personal_access_token', catalog_type = 'unity'` 2. Have a streaming table or materialized view in the catalog (Databricks Lakeflow Pipeline) 3. Attempt to query it: SELECT * FROM catalog.sch

Discussion

Loading comments...