base on This gem adds a Redis::Namespace class which can be used to namespace Redis keys. redis-namespace =============== Redis::Namespace provides an interface to a namespaced subset of your [redis][] keyspace (e.g., keys with a common beginning), and requires the [redis-rb][] gem. ```ruby require 'redis-namespace' # => true redis_connection = Redis.new # => #<Redis client v3.1.0 for redis://127.0.0.1:6379/0> namespaced_redis = Redis::Namespace.new(:ns, redis: redis_connection) # => #<Redis::Namespace v1.5.0 with client v3.1.0 for redis://127.0.0.1:6379/0/ns> namespaced_redis.set('foo', 'bar') # redis_connection.set('ns:foo', 'bar') # => "OK" # Redis::Namespace automatically prepended our namespace to the key # before sending it to our redis client. namespaced_redis.get('foo') # => "bar" redis_connection.get('foo') # => nil redis_connection.get('ns:foo') # => "bar" namespaced_redis.del('foo') # => 1 namespaced_redis.get('foo') # => nil redis_connection.get('ns:foo') # => nil ``` Redis::Namespace also supports `Proc` as a namespace and will take the result string as namespace at runtime. ```ruby redis_connection = Redis.new namespaced_redis = Redis::Namespace.new(Proc.new { Tenant.current_tenant }, redis: redis_connection) ``` Installation ============ Redis::Namespace is packaged as the redis-namespace gem, and hosted on rubygems.org. From the command line: $ gem install redis-namespace Or in your Gemfile: ```ruby gem 'redis-namespace' ``` Caveats ======= `Redis::Namespace` provides a namespaced interface to `Redis` by keeping an internal registry of the method signatures in `Redis` provided by the [redis-rb][] gem; we keep track of which arguments need the namespace added, and which return values need the namespace removed. Blind Passthrough ----------------- If your version of this gem doesn't know about a particular command, it can't namespace it. Historically, this has meant that Redis::Namespace blindly passes unknown commands on to the underlying redis connection without modification which can lead to surprising effects. As of v1.5.0, blind passthrough has been deprecated, and the functionality will be removed entirely in 2.0. If you come across a command that is not yet supported, please open an issue on the [issue tracker][] or submit a pull-request. Administrative Commands ----------------------- The effects of some redis commands cannot be limited to a particular namespace (e.g., `FLUSHALL`, which literally truncates all databases in your redis server, regardless of keyspace). Historically, this has meant that Redis::Namespace intentionally passes administrative commands on to the underlying redis connection without modification, which can lead to surprising effects. As of v1.6.0, the direct use of administrative commands has been deprecated, and the functionality will be removed entirely in 2.0; while such commands are often useful for testing or administration, their meaning is inherently hidden when placed behind an interface that implies it will namespace everything. The prefered way to send an administrative command is on the redis connection itself, which is publicly exposed as `Redis::Namespace#redis`: ```ruby namespaced.redis.flushall() # => "OK" ``` 2.x Planned Breaking Changes ============================ As mentioned above, 2.0 will remove blind passthrough and the administrative command passthrough. By default in 1.5+, deprecation warnings are present and enabled; they can be silenced by initializing `Redis::Namespace` with `warning: false` or by setting the `REDIS_NAMESPACE_QUIET` environment variable. Early opt-in ------------ To enable testing against the 2.x interface before its release, in addition to deprecation warnings, early opt-in to these changes can be enabled by initializing `Redis::Namespace` with `deprecations: true` or by setting the `REDIS_NAMESPACE_DEPRECATIONS` environment variable. This should only be done once all warnings have been addressed. Authors ======= While there are many authors who have contributed to this project, the following have done so on an ongoing basis with at least 5 commits: - Chris Wanstrath (@defunkt) - Ryan Biesemeyer (@yaauie) - Steve Klabnik (@steveklabnik) - Terence Lee (@hone) - Eoin Coffey (@ecoffey) [redis]: http://redis.io [redis-rb]: https://github.com/redis/redis-rb [issue tracker]: https://github.com/resque/redis-namespace/issues ", Assign "at most 3 tags" to the expected json: {"id":"6089","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"