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] Visualization of Secondary Index Content

Enable visualization of the actual content stored in ClickHouse secondary indexes (Skip Indexes) to better understand and debug index usage. This will help debug index effectiveness, optimize performance, and troubleshoot issues with queries not using expected indexes.

Original Source

@@ylw510 | 0 pts | 3/14/2026

## Feature Description Enable visualization of the actual content stored in ClickHouse secondary indexes (Skip Indexes) to better understand and debug index usage. ## Use Cases 1. **Debug index effectiveness**: View the actual values stored in indexes to verify that indexes are correctly built 2. **Performance optimization**: Analyze index distribution to determine if indexes are effective 3. **Troubleshooting**: When queries don't use expected indexes, view index content to diagnose issues 4. **Learning and understanding**: Help users better understand how ClickHouse indexes work ## Current State Currently, we can view index information through: - `system.data_skipping_indices` table: View index definitions and metadata - `system.query_log.skip_indices` column (#87862): View which indexes were used - `EXPLAIN` statement: View index usage in query plans - `mergeTreeIndex` table function: View primary key index and marks files - `mergeTreeTextIndex` table function: View text index

Discussion

Loading comments...