Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Push Publishing: Clear Pushed Assets Table if a Bundle was deleted #8195

Closed
joseorsini opened this issue Sep 30, 2015 · 5 comments
Closed

Push Publishing: Clear Pushed Assets Table if a Bundle was deleted #8195

joseorsini opened this issue Sep 30, 2015 · 5 comments

Comments

@joseorsini
Copy link
Contributor

Reproduced in 3.2.4. Steps:

  1. Clone demo.dotcms.com site.
  2. Once the new site is created, add this new one and demo.dotcms.com site to the same Push Publishing bundle.
  3. Push the Bundle to a Receiver side.
  4. Once the Push Pub is finished, delete the bundle in Sender side, from the Publishing Queue -> Status/History Tab.
  5. Go to the DB and Query the publishing_pushed_assets table according to the bundle Id you just deleted. Rows are still there on DB and they're not cleared.

If we allow the History of all Push Pub to be deleted, we should delete all referenced assets to each bundle we delete.

@rogelio-blanco
Copy link

In progress - Card#307

@jtesser jtesser closed this as completed Dec 3, 2015
@jtesser jtesser removed this from the 3.3 milestone Dec 3, 2015
@austindlawless
Copy link
Contributor

What was the resolution on this?

@jtesser
Copy link
Contributor

jtesser commented Dec 3, 2015

should be in 3.3

@austindlawless
Copy link
Contributor

Excellent.

@jtesser
Copy link
Contributor

jtesser commented Dec 3, 2015

Well FWIW we fixed the performance issue here which I was confused on and thought was referencing.

But deleting a old bundle should not delete the push history. This is on purpose

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants