Add support for Redis over Unix socket

[stevecj]

Currently, there does not seem to be support for use of Redis through a Unix socket. When I attempt to specify a URI with a schema of "redis-socket", I get a key error. Looking in the code, there is apparently support for "redis", and "rediss", but no other kinds of Redis schema.

Presumably, an implementation of this would support the same "redis-socket://" form of URI that is supported by Lettuce (see https://github.com/redis/lettuce/wiki/Redis-URI-and-connection-details)

[stevecj]

Since there seems to be little activity here, I also created celery/celery#9860 about this.

[auvipy]

please stop doing activities which seems to be like spamming. you dont need to open multiple same issue across the repos of this project. you should have start a discussion first as per the projects guideline. also you didnt follow any issues template at all, which made your issue of very low quality. hence much less traction. if you are up for contribution, feel free to come up with a draft pr to address this issue. or you can wait for others to claim the issue. thanks for understanding.

[stevecj]

@auvipy Thanks for the advice. Should I close these and try to ask again more appropriately?

I feel kind of dumb for not noticing that kombu is a subproject of celery. I thought it was an external dependency.

[auvipy]

Currently, there does not seem to be support for use of Redis through a Unix socket. When I attempt to specify a URI with a schema of "redis-socket", I get a key error. Looking in the code, there is apparently support for "redis", and "rediss", but no other kinds of Redis schema.

Presumably, an implementation of this would support the same "redis-socket://" form of URI that is supported by Lettuce (see https://github.com/redis/lettuce/wiki/Redis-URI-and-connection-details)

is this supported in redis-py already?

[stevecj]

@auvipy Per https://redis.readthedocs.io/en/latest/connections.html#redis.Redis.from_url, redis-py supports a unix:// schema, but of course, that's not a great name for a schema. It only makes sense to use in a limited context that is already constrained to refer to Redis and nothing else. I just opened a discussion about this at redis/redis-py#3742 .

It looks like the structure for that is not the same as Lettuce's "redis-socket://", so maybe it would be better to use the structure that redis-py supports but with a schema name such as "redis+unix://", "redis-unix://", or "redis+socket://", all of which specifically identify Redis and are different from the "redis-socket://" schema name (with a dash, not a plus) used by Lettuce.