When a key contains characters that are invalid for identifiers, you’ll have to quote the name. .”OPEN.BTC” Or for older versions of jq, use an index. .[“OPEN.BTC”] Example … | jq ‘.”OPEN.BTC”‘
The problem is that jq is still just outputting lines of text; you can’t necessarily preserve each array element as a single unit. That said, as long as a newline is not a valid character in any object, you can still output each object on a separate line. get_json_array | jq -c ‘.[]’ | while … Read more
We can solve this problem by two ways. They are: Input string: // test.json { “keys”: [“key1″,”key2″,”key3”] } Approach 1: 1) Use jq -r (output raw strings, not JSON texts) . KEYS=$(jq -r ‘.keys’ test.json) echo $KEYS # Output: [ “key1”, “key2”, “key3” ] 2) Use @sh (Converts input string to a series of space-separated … Read more
Slurp it up with the -s option. $ jq -s ‘.’ <<< ‘{ “a”: 1 } { “b”: 2 }’ [ { “a”: 1 }, { “b”: 2 } ] As another option, reading the values using inputs is a much more flexible alternative. You’ll usually want to use this in conjunction with the -n … Read more
Borrowing from this answer which does all of the hard work of turning the JSON into key=value pairs, you could get these into the environment by looping over the jq output and exporting them: for s in $(echo $values | jq -r “to_entries|map(\”\(.key)=\(.value|tostring)\”)|.[]” ); do export $s done If the variables being loaded contain embedded … Read more
You set values of an object using the = operator. |= on the other hand is used to update a value. It’s a subtle but important difference. The context of the filters changes. Since you are setting a property to a constant value, use the = operator. .shipping.local = false Just note that when setting … Read more
-c is what you likely need Using the output you posted above, you can process it further: jq -c . input To Give; {“key”:”SEA-739″,”status”:”Open”,”assignee”:null} {“key”:”SEA-738″,”status”:”Resolved”,”assignee”:”[email protected]”} Or you can just change your original command FROM jq -r ‘(.issues[] | {key, status: .fields.status.name, assignee: .fields.assignee.emailAddress})’ TO jq -c ‘(.issues[] | {key, status: .fields.status.name, assignee: .fields.assignee.emailAddress})’
Using the @tsv filter has much to recommend it, mainly because it handles numerous “edge cases” in a standard way: .[] | [.id, .name] | @tsv Adding the headers can be done like so: jq -r ‘[“ID”,”NAME”], [“–“,”——“], (.[] | [.id, .name]) | @tsv’ The result: ID NAME — —— 12 George 18 Jack 19 … Read more
To get the top-level keys as a stream, you can use the built-in function keys[]. So one solution to your particular problem would be: jq -r ‘keys[] as $k | “\($k), \(.[$k] | .ip)”‘ keys produces the key names in sorted order; if you want them in the original order, use keys_unsorted. Another alternative, which … Read more
Here is a generic JSON-to-CSV converter that makes just one major assumption and one minor assumption. The major assumption is that all the JSON entities are conformal. In your case, it means that all corresponding objects have the same keys (though they may be in different order). If this assumption is ever violated, an error … Read more