Opened 4 years ago

Closed 3 years ago

#5464 closed defect (fixed)

sqlalchemy is not supported as kombu transport

Reported by: Boris Bobrov Owned by:
Priority: major Milestone: 1.0
Component: programming Keywords: celery, kombu, large
Cc: Christopher Allan Webber Parent Tickets:

Description

sqlalchemy cannot be used as a kombu transport any more. It was removed: https://github.com/celery/celery/issues/3274#issuecomment-228324848, kombu commit 1cd4e07f9ebb2fdbde0f86054e963f6bbd17e698.
For now i have capped kombu and celery to <4.0, but we need to figure out what to do.

Subtickets

Change History (7)

comment:1 Changed 4 years ago by ayleph

It looks like capping at "<4.0" doesn't prevent 4.0.0rc3 from being downloaded. Stack Overflow suggests using a syntax like "<4.0a0".

https://stackoverflow.com/a/14405269

Version 0, edited 4 years ago by ayleph (next)

comment:2 Changed 4 years ago by ayleph

I downloaded latest stable branch from git and the "<4.0" stuff seemed to work fine when following the build instructions for py2 and py3. I don't know why it didn't work for the user in IRC.

comment:3 Changed 4 years ago by jerome

I had the same issue but 474a56 didn't fixed that. I had to specify "<4.0a0" as suggested by ayleph, otherwise celery==4.0.0rc3 and kombu==4.0.0rc3 was installed.

comment:4 in reply to:  3 Changed 4 years ago by ayleph

Replying to jerome:

I had to specify "<4.0a0" as suggested by ayleph, otherwise celery==4.0.0rc3 and kombu==4.0.0rc3 was installed.

Thanks for confirming that worked for you. I've pushed that change to master in d37c6f6 and cherry-picked onto stable.

comment:5 Changed 4 years ago by Christopher Allan Webber

Per our discussions in today's meeting, we'll move to a more official broker for those who are running celery separately. Considering that it's widely packaged, and that Redis is a little bit less certain (it was the original topic of removal in that bug, but has since been preserved), we will probably go with RabbitMQ. This will mean changing our docs and etc.

comment:6 Changed 4 years ago by Ben Sturmfels

Keywords: large added

Marking as "large" assuming that this will require a significant infrastructure change to fully resolve.

comment:7 Changed 3 years ago by Boris Bobrov

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.