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

Emit Enabled default configuration #366

Closed
enumag opened this issue Apr 11, 2019 · 1 comment · Fixed by #382 or prooph/event-store-client#106
Closed

Emit Enabled default configuration #366

enumag opened this issue Apr 11, 2019 · 1 comment · Fixed by #382 or prooph/event-store-client#106

Comments

@enumag
Copy link
Member

enumag commented Apr 11, 2019

This is not exactly a bug per se but it certainly caused a wtf moment for me.

So this morning I noticed that my projection was not running. When I checked it's status, I found this:

  "status": "Faulted (Enabled)",
  "stateReason": "'emit' is not allowed by the projection/configuration/mode",

Then I digged what the emit option is, which was easy to find here even with the error.

Then I checked how the projection was created. Prooph has a hard-coded &emit=1 here which got me confused.

The problem was that I'm using ProjectionsManager::updateQuery() when migrating to a new version. This method however has the $emitEnabled option which I did not notice and it defaults to false.

Maybe it's intended but it certainly caught me off-guard. When creating a projection there is no way to turn off the emit option, yet when updating it gets disabled by default.

Feel free to close this if this is intended. Just wanted to share my experience.

@enumag
Copy link
Member Author

enumag commented Sep 24, 2019

ping @prolic

prolic added a commit that referenced this issue Nov 23, 2019
prolic added a commit to prooph/event-store-client that referenced this issue Nov 23, 2019
prolic added a commit that referenced this issue Nov 23, 2019
ChrisSanderser added a commit to ChrisSanderser/event-store that referenced this issue Jan 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant