fix(analytics): fix first_attempt filter value parsing for Payments #6667
+2
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Type of Change
Description
first_attempt
filter takes intrue
orfalse
as variants.'true'
or'false'
This works on latest clickhouse versions, but fails on the older clickhouse versions, with the error:
Now, internally converting
'true'
to'1'
and'false'
to'0'
to fix the issue, and this gets accepted in both the versions.The query which was previously running was:
Now the query which will run is:
Additional Changes
Motivation and Context
Fix the issue: #6666
How did you test it?
Hit the curl with first_attempt filter containing either
true
orfalse
:Response:
If smart retries are made, then these fields will show null:
And these fields will have some value:
Checklist
cargo +nightly fmt --all
cargo clippy