![]() ![]() \"recordN\": \"someExpectedValN => null\" \"recordY\": \"someExpectedVal => null\", You can play with it and compare with real data. The following is a data emulation that gives the exact desired outputs. | stats values(Unique_key) as Unique_key count by value | stats values(discrepancyDetails.*) as discrepancyDetails.* To address 3, values need to be preserved in stats, then table calculated after transpose. | transpose header_field=legend column_name=Unique_key So, my previous search should address requirement 2 when bad.* are excluded (it cannot be combined into the same stats as 3 based on your illustration). After renaming the original discrepancyDetails.*, I should have excluded them before preceding. The illustration of desired output eliminates a lot of guess work. ![]() I am unable to figure out points 2 and 3 from the above requirements.ĭesired output for requirement 2 considering above sample json: Unique_keyĭesired output for requirement 3 considering above sample json: Unique_key | stats count(discrepancyDetails.*) as discrepancyDetails.* I was able to obtain the unique count of all the keys using the following query. figure out all the keys with null actual (from sample json "expected => actual") values and "#DEL" (deleted) values.I want to treat these keys as "record/" and replace the numeric strings with an empty value. For example, in the same JSON, we have two keys in the discrepancyDetails: "record/1" and "record/2". ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |