redis / redis/RedisInsight

[Feature Request] Automatically Save and Display Queried Keys to Improve Search Efficiency

Open
#4,493 3 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature
Dominant language
TypeScript
Stars
8.8k
Forks
491
Avg merge
1d 22h
Merged PRs (30d)
49

Description

Problem description

Currently, when using RedisInsight for database management and monitoring, if you need to query the same key repeatedly, you must re-enter that key each time. This is not only time-consuming but also reduces work efficiency. It is suggested to add a feature that automatically saves the keys used in queries and displays them in a list format, allowing users to directly click on these keys for quick searches.

How often do you encounter this problem

This issue frequently arises during my daily use, especially when debugging or analyzing data patterns where I need to access the same keys repeatedly. This situation occurs almost daily, particularly when dealing with large datasets.

Alternatives considered

I have considered using other tools or scripts to keep track of commonly used keys, but doing so not only adds extra workload but also does not integrate well with RedisInsight’s graphical interface. Additionally, while some command-line tools can achieve similar results through history records, they lack the intuitiveness and ease of use provided by RedisInsight.

Additional information

Adding this feature would not only significantly enhance user experience but also strengthen RedisInsight's competitive edge as a Redis management tool. It will make the data retrieval process more efficient, reduce unnecessary repetitive operations, and allow users to focus more on data analysis and application development.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue does not name any files, tests, or entry points, so first trace the RedisInsight query interface and its existing query-history behavior. The requested outcome is to save queried keys, display them in a list, and let users select a key to repeat its search; the storage scope and UI details still need definition.

Written by the indexing model from the issue text.

Assessment

Tech stack
redis, typescript
Domain
database
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.