-
Notifications
You must be signed in to change notification settings - Fork 245
feat: add sharded state COMPASS-8279 #6304
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
Conversation
cebd5db to
9c255d6
Compare
d6f86a3 to
3709b00
Compare
packages/compass-global-writes/src/components/states/shard-key-correct.tsx
Outdated
Show resolved
Hide resolved
packages/compass-global-writes/src/components/states/shard-key-correct.tsx
Show resolved
Hide resolved
packages/compass-global-writes/src/components/states/shard-key-correct.tsx
Show resolved
Hide resolved
packages/compass-global-writes/src/components/states/shard-key-correct.tsx
Outdated
Show resolved
Hide resolved
packages/compass-global-writes/src/components/states/shard-key-correct.tsx
Show resolved
Hide resolved
packages/compass-global-writes/src/components/states/shard-key-correct.tsx
Outdated
Show resolved
Hide resolved
packages/compass-global-writes/src/components/states/shard-key-correct.tsx
Outdated
Show resolved
Hide resolved
| const store = setupStore(options, services, connectionInfo); | ||
| return renderWithActiveConnection( | ||
| <Provider store={store}>{component}</Provider>, | ||
| connectionInfo | ||
| ); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just FYI, we specifically added these helpers so you don't need to manually wire providers and run activate methods
|
GitHub collapsed the |
…-correct.tsx Co-authored-by: Sergey Petushkov <petushkov.sergey@gmail.com>
51f69f9 to
7d9dda9
Compare
packages/compass-global-writes/src/components/states/shard-key-correct.tsx
Outdated
Show resolved
Hide resolved
| }, | ||
| }); | ||
| await store.dispatch(fetchClusterShardingData()); | ||
| // expect(store.getState().status).to.equal('SHARD_KEY_CORRECT'); // no idea why this does not work |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is the state not matching or the check? What state do you see here? (we probably want to either remove this comment altogether or resolve, a bit weird to just leave this comment 🙂)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was seeing NOT_READY. Putting the check behind waitFor helped, but I'm not sure why it was needed 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ah right! I was looking at this code and read it wrong 🤦 outside of tests it currently doesn't make difference if we wait for this one, since the fetchClusterShardingData is not awaited.
Co-authored-by: Sergey Petushkov <petushkov.sergey@gmail.com>
d573635 to
e61b120
Compare

Description
SHARD_KEY_INVALID,SHARD_KEY_MISMATCHorSHARDING_ERROR, but doesn't add the UI for them (will be added in https://jira.mongodb.org/browse/COMPASS-8278 and https://jira.mongodb.org/browse/COMPASS-8349)Checklist
Motivation and Context
Open Questions
Dependents
Types of changes