Skip to content

Commit 4e9f305

Browse files
fix: update correct server mode in parseable.json
Steps to reproduce issue - 1. start prism and query node with enterprise build, stop both nodes 2. start standalone/distributed-Query with same staging and s3 bucket -- No env change -- hence Deployment ID remains same, server_mode remains Prism Fix: for mode `All` and `Query` even for no env change, update server_mode in parseable.json in storage
1 parent d4bf193 commit 4e9f305

File tree

1 file changed

+15
-1
lines changed

1 file changed

+15
-1
lines changed

src/storage/store_metadata.rs

Lines changed: 15 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -117,9 +117,23 @@ pub async fn resolve_parseable_metadata(
117117
let mut overwrite_remote = false;
118118

119119
let res = match check {
120-
EnvChange::None(metadata) => {
120+
EnvChange::None(mut metadata) => {
121121
// overwrite staging anyways so that it matches remote in case of any divergence
122122
overwrite_staging = true;
123+
match PARSEABLE.options.mode {
124+
Mode::All => {
125+
metadata.server_mode.standalone_after_distributed()?;
126+
overwrite_remote = true;
127+
metadata.server_mode = PARSEABLE.options.mode;
128+
metadata.staging = PARSEABLE.options.staging_dir().to_path_buf();
129+
}
130+
Mode::Query => {
131+
overwrite_remote = true;
132+
metadata.server_mode = PARSEABLE.options.mode;
133+
metadata.staging = PARSEABLE.options.staging_dir().to_path_buf();
134+
}
135+
_=> {}
136+
}
123137
if PARSEABLE.options.mode == Mode::All {
124138
metadata.server_mode.standalone_after_distributed()?;
125139
}

0 commit comments

Comments
 (0)