问题[json](coding)

这是我的输入数据：

[
  {
    "UniqueID": 1,
    "Group": "alpha",
    "Type": "t/1"
  },
  {
    "UniqueID": 2,
    "Group": "alpha",
    "Type": "t/14"
  },
  {
    "UniqueID": 3,
    "Group": "beta",
    "Type": "t/11"
  },
  {
    "UniqueID": 4,
    "Group": "charlie",
    "Type": "t/10"
  },
  {
    "UniqueID": 5,
    "Group": "beta",
    "Type": "t/7"
  }
]

我希望得到：

{
  "alpha": ["t/1", "t/14"],
  "beta": ["t/11", "t/7"],
  "charlie": ["t/10"]
}

这就是我想要做的，但没有得到我所希望的结果。

[
  {
    "operation": "shift",
    "spec": {
      "*": {
        "Group": "&2.Type"
      }
    }
  },
  {
    "operation": "cardinality",
    "spec": {
      "*": "ONE"
    }
  }
]

有人能提供一些指导吗？我好像无法让它工作。谢谢

我必须使用 Nifi 中的 JOLT Transform 将 2 个数组（数字）的数组转换为单个数组，其中每个元素都有来自两个数组的一个值。

输入：

{
  "md": {
    "fn": "abcd"
  },
  "content": {
    "idc": "0",
    "lsr": "3",
    "lsc": "A",
    "array Of Arrays": [
      {
        "name": "step_1",
        "row": "2",
        "column": "A",
        "gph": {
          "a values": [
            0.23,
            1.39
          ],
          "t values": [
            0.3,
            1.9
          ]
        }
      },
      {
        "name": "step_2",
        "row": "3",
        "column": "A",
        "gph": {
          "a values": [
            0.56,
            2.49
          ],
          "t values": [
            1.4,
            2.8
          ]
        }
      }
    ]
  }
}

当前 JOLT 规格：

[
  {
    "operation": "shift",
    "spec": {
      "md": {
        "fn": "fn"
      },
      "content": {
        "idc": "idc",
        "lsr": "lsr",
        "lsc": "lsc",
        "array Of Arrays": {
          "*": {
            "name": "name[]",
            "s": "s[]",
            "p": "p[]",
            "gph": "&[]"
          }
        }
      }
    }
  },
  {
    "operation": "modify-default-beta",
    "spec": {
      "sop": "=concat(@(2,lsr),@(2,lsc))"
    }
  }
]

电流输出：

{
  "fn" : "abcd",
  "idc" : "0",
  "lsr" : "3",
  "lsc" : "A",
  "name" : [ "step_1", "step_2" ],
  "s" : [ "2", "3" ],
  "p" : [ "A", "A" ],
  "gph" : [ {
    "a values" : [ 0.23, 1.39 ],
    "t values" : [ 0.3, 1.9 ]
  }, {
    "a values" : [ 0.56, 2.49 ],
    "t values" : [ 1.4, 2.8 ]
  } ],
  "sop" : "3A"
}

预期输出：

{
  "fn" : "abcd",
  "idc" : "0",
  "array" : [
    {"name": "step_1", "sp": "2A", "a_value": 0.23, "t_value": 0.3},
    {"name": "step_1", "sp": "2A", "a_value": 1.39, "t_value": 1.9},
    {"name": "step_2", "sp": "3A", "a_value": 0.56, "t_value": 1.4},
    {"name": "step_2", "sp": "3A", "a_value": 2.49, "t_value": 2.8}
  ],
  "sop" : "3A"
}

考虑这个例子（这里有更多Vega 编辑器中的示例数据）

{
  "$schema": "https://vega.github.io/schema/vega-lite/v6.json",
  "data": {
    "name": "dataset",
    "values": [
    {
        "JobBeg": "2023-01-01T11:04:45",
        "JobEnd": "2023-01-01T18:04:45",
        "JobNum": "JN000",
        "Assigned_To": "David",
        "Midpoint": "2023-01-01T14:34:45"
    },
    {
        "JobBeg": "2023-01-01T15:07:31",
        "JobEnd": "2023-01-01T18:07:31",
        "JobNum": "JN001",
        "Assigned_To": "Bob",
        "Midpoint": "2023-01-01T16:37:31"
    }
]    
  },
  "layer": [
    {
      "mark": {"type":"bar", "stroke":"black","strokeWidth":2},
      "encoding": {
        "y": {
          "field": "Assigned_To",
          "type": "nominal",
          "title": "Assigned To"
        },
        "x": {
          "field": "JobBeg",
          "type": "temporal",
          "title": "Start Time",
          "axis":
          {
            "interval": "day",
            "step": 1
          }
        },
        "x2": {
          "field": "JobEnd",
          "title": "End Time"
        },
      "tooltip": [
        {
          "field": "JobBeg",
          "type": "temporal",
          "title": "Start Time",
          "format": "%Y-%m-%d %H:%M"
        },
        {
          "field": "JobEnd",
          "type": "temporal",
          "title": "End Time",
          "format": "%Y-%m-%d %H:%M"
        },
        {
          "field": "JobNum",
          "type": "nominal"
        }
      ]
      }
    },
    {
      "mark": {
        "type": "text",
        "align": "center",
        "baseline": "middle"
      },
      "encoding": {
        "y": {
          "field": "Assigned_To",
          "type": "nominal"
        },
        "x": {
          "field": "Midpoint",
          "type": "temporal"
        },
        "text": {
          "field": "JobNum",
          "type": "nominal"
        }
      }
    }
  ]
}

目前我正在使用作业开始/结束的中点将每个条形中的文本标记居中，但我无法找到将文本标记限制为条形大小的方法（即，如果持续时间很短，我不应该看到文本溢出条形）

我正在尝试用这种格式的json文件创建一个LSTM模型来预测手语句子。这个json文件包含每帧每只手（左手、右手）21个手部关键关节的坐标信息。以下是我的json时间序列数据的预览。

{

        "frame": 123,
        "hands": [
            {
                "hand": "Left",
                "landmarks": [
                    {
                        "x": 0.4636201858520508,
                        "y": 0.3758980929851532,
                        "z": 7.529240519943414e-08,
                        "body_part": "wrist"
                    },

   ...

                    {
                        "x": 0.4639311134815216,
                        "y": 0.2574789524078369,
                        "z": -0.013109659776091576,
                        "body_part": "pinky_tip"
                    }
                ]
            },

            {
                "hand": "Right",
                "landmarks": [
                    {
                        "x": 0.5393109321594238,
                        "y": 0.6190552711486816,
                        "z": 1.0587137921902467e-07,
                        "body_part": "wrist"
                    },
...

                    {
                        "x": 0.4721616506576538,
                        "y": 0.5990280508995056,
                        "z": -0.006831812672317028,
                        "body_part": "pinky_tip"
                    }
                ]
            }
        ]
    },

不同位置的坐标信息在每一帧中重复出现。我仍在修正这些 JSON 时间序列数据。因此，我还没有开始编写 LSTM 代码。不过，我很担心能否将这些 JSON 时间序列数据用于 LSTM。

我创建了一个 JSON 文件，其中包含多个对象，这些对象包含分配给字符串的命名值，如下所示，

{
    "Obj1" : {
        "Val1": "Obj 1, Test Value 1",
        "Val2": "Obj 1, Test Value 2",
        "Val3": "Obj 1, Test Value 3"
    },
    "Obj2" : {
        "Val1": "Obj 2, Test Value 1",
        "Val2": "Obj 2, Test Value 2",
        "Val3": "Obj 2, Test Value 3"
    }
}

我需要在 Next JS 中单独访问每个对象中的每个值，我尝试导入和解析数据，

import data from '~/data.json';
const obj1: any = JSON.parse(data["Obj1"]); // Side Note: What type should this const be?
console.log(obj1.Val1); // Desired Output: " Obj1, Test Value 1 "

但是，当我尝试这样做时，我遇到了这个错误，“类型为‘{Val1：string;}’的参数不能分配给类型为‘string’的参数。ts(2345)”

无论我怎么操作，都找不到解决此错误的方法。我的 JSON 或 TS 格式不正确吗？

我的数据采用以下简化格式

[
  {
    "a": "foo",
    "b": [
      {
        "x": 1,
        "y": true
      }
    ]
  },
  {
    "a": "foo",
    "b": [
      {
        "x": 1,
        "y": true
      },
      {
        "x": 99,
        "y": false
      }
    ]
  },
  {
    "a": "bar",
    "b": []
  }
]

我正在尝试获取每个 unique的所有条目数。我尝试先按 a 分组，这样至少可以得到“unique ”部分。但是，我不知道如何获取group_by 结果中所有条目数。单纯按like分组是行不通的。bajq '. | group_by(.a)[]abbjq '. | group_by(.a)[] | group_by(.b)[]'

或者，我尝试过jq -n 'jq '[ .[] | {a, n:(.b|length)} ] | group_by(.a)'但仍然不知道如何跨条目计数。

有什么建议吗？本例的最终答案是 3 个b条目foo，0 个b条目bar

我想在一个多维 JSON 对象（一个包含多个映射的映射）中提取键EN和ES（语言）以及属性。这怎么可能呢？

JSON：

{
  "EN": {
    "name": "name en",
    "description": "description en"
  },
  "ES": {
    "name": "name es",
    "description": "description es"
  }
}

这将获取每个带有翻译的地图，但我还想检索地图的父键（EN和ES）

SQL

SELECT jt.name, jt.description
FROM
    payment_term p,
    JSON_TABLE(
        p.document_languages, '$.*' COLUMNS (
            name TEXT PATH '$.name'
            description TEXT PATH '$.description'
        )
    ) as jt
WHERE p.id=31

这将输出

name     |   description
------------------------------
name en  |   description en
name es  |   description es

但我想要类似的东西

lang   |   name     |   description
------------------------------
en     |   name en  |   description en
es     |   name es  |   description es

我有一个 JSON：

[
  {
    "datetime": "2025-04-07T18:03:50+03:00",
    "title": "Theme Drive",
    "content": {
      "adPlacement": {
        "id": 4289485,
        "name": "otclick_OLV_apart_jan_mar_In_stream",
        "banners": {
          "href": [
            "https://api.adriver.ru/banners/12037384",
            "https://api.adriver.ru/banners/12043208",
            "https://api.adriver.ru/banners/11887226",
            "https://api.adriver.ru/banners/12028437"
          ]
        }
      }
    }
  }
]

我想构建下面的 json：将数组中的元素分成具有属性的对象banner_id，然后将数字存储为值banners/

我期望这个输出：

[
  {
    "banner_id": 12037384
  },
  {
    "banner_id": 12043208
  },
  {
    "banner_id": 11887226
  },
  {
    "banner_id": 12028437
  }
]

我写：

[
  {
    "operation": "shift",
    "spec": {
      "*": {
        "content": {
          "adPlacement": {
            "banners": {
              "href": {
                "*": "[&]"
              }
            }
          }
        }
      }
    }
  }
]

我刚刚得到了一个数组（与预期不符），而且我在处理 Banner_id 时遇到了麻烦。对于拆分，我尝试了类似这样的方法："banner_id": "=split('banners/', @(1,&))"，但它抛出了错误。如何达到预期的输出？

更新

第二种情况，里面有一个对象href：

[
   {
      "datetime":"2025-04-07T18:03:50+03:00",
      "title":"Theme Drive",
      "content":{
         "adPlacement":{
            "id":4289485,
            "name":"otclick_OLV_apart_jan_mar_In_stream",
            "banners":{
               "href":"https://api.adriver.ru/banners/12037384"
            }
         }
      }
   }
]

预期的：

[
  {
    "banner_id": 12037384
  }
]

我的结果：

[
  {
    "operation": "shift",
    "spec": {
      "*": {
        "content": {
          "adPlacement": {
            "banners": {
              "href": {
                "*": {
                  "*banners/*": {
                    "$(0,2)": "[&2].banner_id"
                  }
                },
                "*banners/*": {
                  "$(0,2)": "[0].banner_id"
                }
              }
            }
          }
        }
      }
    }
  },
  {
    "operation": "modify-overwrite-beta",
    "spec": {
      "*": {
        "banner_id": "=toInteger"
      }
    }
  }
]

我从 API 返回了一个非常长的 JSON 字符串。

基本上它看起来像这样： {"data":{.......},"needs_trial": false, "adjust_time": false,"attempts": 1234}

我需要该data部分内不包含“附录”的所有内容作为字符串。

我尝试在 Go 中解析 JSON 时采用通常的方法：

//fetch the data with http.Get into resp.Body

type MyData struct {
   Data map[string]interface{}
}

var data MyData
if err := json.NewDecoder(resp.Body).Decode(&data); err != nil {
    return err
}

我当然得到了正确的部分，但现在显然map[string]interface{}。我没能将其转换回字符串...

定义Data字段MyDataasstring也失败。

我不能直接将其剪掉，因为前缀部分是固定的（{"data":），但尾随部分不是。

我不敢相信我还没能做到这一点，因此在这里问...我已经在这上面花了这么多时间，我可以接受反对票...

我从 REST API 调用的输出中捕获了一个 dict/json 类型的对象，假设它位于一个名为ouput的变量/寄存器中。数据如下所示。为了完整起见，我分享了整个对象并做了一些基本的清理。请只关注我接下来要讨论的那一行 ;-)

            {
            "_create_time": 1724823837185,
            "_create_user": "system",
            "_last_modified_time": 1736218001919,
            "_last_modified_user": "nsx_policy",
            "_protection": "NOT_PROTECTED",
            "_revision": 1,
            "_system_owned": false,
            "display_name": "w1-vc1-c4n17.example.com",
            "host_switch_spec": {
                "host_switches": [
                    {
                        "cpu_config": [],
                        "ecmp_mode": "L3",
                        "host_switch_id": "50 01 cb 21 be 19 cb 38-78 bd 67 bc b3 0e 91 f1",
                        "host_switch_mode": "STANDARD",
                        "host_switch_name": "w1-vc1-c4-dvs",
                        "host_switch_profile_ids": [
                            {
                                "key": "UplinkHostSwitchProfile",
                                "value": "/infra/host-switch-profiles/6d7a0ed8-c86a-4190-9121-ce6f863226ae"
                            },
                            {
                                "key": "VtepHAHostSwitchProfile",
                                "value": "/infra/host-switch-profiles/0de8282e-7385-4e8e-a905-0c11960db728"
                            }
                        ],
                        "host_switch_type": "VDS",
                        "ip_assignment_spec": {
                            "ip_pool_id": "/infra/ip-pools/w1-nsx1-esxi-teps",
                            "resource_type": "StaticIpPoolSpec"
                        },
                        "is_migrate_pnics": false,
                        "not_ready": false,
                        "portgroup_transport_zone_id": "/infra/sites/default/enforcement-points/default/transport-zones/77166711-1f83-407f-8c27-a4e1b8b4e1e5",
                        "transport_zone_endpoints": [
                            {
                                "transport_zone_id": "/infra/sites/default/enforcement-points/default/transport-zones/4b367ddf-d4ac-460b-a884-24846ff4edf6",
                                "transport_zone_profile_ids": [
                                    {
                                        "profile_id": "/infra/transport-zone-profiles/52035bb3-ab02-4a08-9884-18631312e50a",
                                        "resource_type": "BfdHealthMonitoringProfile"
                                    }
                                ]
                            },
                            {
                                "transport_zone_id": "/infra/sites/default/enforcement-points/default/transport-zones/bc19b340-f0b5-46d8-9454-6d94d3288821",
                                "transport_zone_profile_ids": [
                                    {
                                        "profile_id": "/infra/transport-zone-profiles/52035bb3-ab02-4a08-9884-18631312e50a",
                                        "resource_type": "BfdHealthMonitoringProfile"
                                    }
                                ]
                            }
                        ],
                        "uplinks": [
                            {
                                "uplink_name": "uplink-2",
                                "vds_uplink_name": "uplink2"
                            },
                            {
                                "uplink_name": "uplink-1",
                                "vds_uplink_name": "uplink1"
                            }
                        ]
                    }
                ],
                "resource_type": "StandardHostSwitchSpec"
            },
            "id": "w1-vc1-c4n17-6adb838f-669c-48ca-b76f-e1238984ef93host-2171",
            "is_overridden": false,
            "maintenance_mode": "DISABLED",
            "marked_for_delete": false,
            "node_deployment_info": {
                "compute_collection_id": "6adb838f-669c-48ca-b76f-e1238984ef93:domain-c2147",
                "discovered_ip_addresses": [
                    "x.x.x.x",
                    "x.x.x.x"
                ],
                "discovered_node_id": "6adb838f-669c-48ca-b76f-e1238984ef93:host-2171",
                "fqdn": "w1-vc1-c4n17.example.com",
                "ip_addresses": [
                    "10.x.x.x"
                ],
                "managed_by_server": "10.x.x.x",
                "os_type": "ESXI",
                "os_version": "x.x.x"
            },
            "overridden": false,
            "owner_id": "1ae23909-d587-4683-a515-4c2001940803",
            "parent_path": "/infra/sites/default/enforcement-points/default",
            "path": "/infra/sites/default/enforcement-points/default/host-transport-nodes/w1-vc1-c4n17-6adb838f-669c-48ca-b76f-e1238984ef93host-2171",
            "realization_id": "c2c69a21-698a-4586-869a-7c0b0a651601",
            "relative_path": "w1-vc1-c4n17-6adb838f-669c-48ca-b76f-e1238984ef93host-2171",
            "remote_path": "",
            "resource_type": "HostTransportNode",
            "unique_id": "c2c69a21-698a-4586-869a-7c0b0a651601"
        }

我想通过更改以下行来更新该对象：

"host_switch_mode": "STANDARD",

到：

"host_switch_mode": "LEGACY",

我会将结果 JSON 作为消息体传递给 POST API 调用。我尝试过 anislbe 的组合过滤器，但没有得到预期的结果。例如：

- Name: example post/put API call
  uri:
    url: "https://{{ nsx }}/policy/api/v1/infra/host-transport-node-profiles/{{ id }}"
        force_basic_auth: yes
        validate_certs: no
        headers:
          Accept: "application/json"
          Content-Type: "application/json"
        user: "{{ username }}"
        password: "{{ password }}"
        method: PUT
        body: "{{ ouput | combine( {'host_switch_spec': {'host_switches': [ {'host_switch_mode': "LEGACY"},],}, }, recursive=true) }}"
        status_code: "200"
        body_format: json

使用组合过滤器，我看到的是，整个 host_switch_spec 部分被替换（因此丢失了其他属性，如 host_switch_name、host_switch_id 等），而不是仅仅合并相关行，这不是我想要的：

            "host_switch_spec": {
            "host_switches": [
                {
                    "host_switch_mode": "STANDARD"
                }
            ],
            "resource_type": "StandardHostSwitchSpec"
        },

我做错了什么？我查看了组合过滤器的手册页，并尝试了所有list_merge选项，但都无济于事。

更新：

为了简单起见，我在上一篇文章中没有提到的一个复杂问题是，我有一个包含这些“输出”数据对象的列表，我需要像下面这样循环处理它们。假设这个列表在变量“tn”中：

  # Modify the transport node json data on the fly and feed it to the API as message body
  - debug: 
      msg: 
        - "{{ item }}"
        - "{{ item | combine( {'host_switch_spec': {'host_switches': [ {'host_switch_mode': mode}, ], }, },) }}"
    with_items: "{{ tn }}"
    loop_control:
      label: "{{ item.display_name }}"

概括：

感谢大家的帮助和指导。我还没有完成端到端测试，但以下是我根据 Vladimir Botka 提供的精彩示例得出的结论：

      # how to modify the transport node json data on the fly and feed it to the API as message body
  - name: Testing switch mode update on the fly
    debug: 
      msg:
        #- "hs: {{ (item.host_switch_spec.host_switches + [ hs_update ]) | combine }}"
        #- "update: {{ {'host_switch_spec': {'host_switches': [ (item.host_switch_spec.host_switches + [ hs_update ]) | combine ]}} }}"
        #- "result: {{ item | combine({'host_switch_spec': {'host_switches': [ (item.host_switch_spec.host_switches + [ hs_update ]) | combine ]}}) }}"
        - "{{ item | combine({'host_switch_spec': {'host_switches': [ (item.host_switch_spec.host_switches + [ hs_update ]) | combine ]}}) }}"
    loop: "{{ tn }}"
    loop_control:
      label: "{{ item.display_name }}"
      index_var: counter
    vars:
      hs_update:
        host_switch_mode: "LEGACY"

结果看起来很有希望（显示最后一个-#24，并且仅显示部分以避免混乱）：

ok: [localhost] => (item=w11-vc1-c1n24.example.com) => {
"msg": [
    "24':' STANDARD",
    {
        "_create_time": 1743198123451,
        "_create_user": "system",
        "_last_modified_time": 1743445520238,
        "_last_modified_user": "system",
        "_protection": "NOT_PROTECTED",
        "_revision": 2,
        "_system_owned": false,
        "display_name": "w11-vc1-c1n24.example.com",
        "host_switch_spec": {
            "host_switches": [
                {
                    "cpu_config": [],
                    "ecmp_mode": "L3",
                    "host_switch_id": "50 1e 66 c9 c5 fb da b3-5e 1f 45 fc 2a 42 99 50",
                    "host_switch_mode": "LEGACY",
                    "host_switch_name": "w11-vc1-dvs",
                    "host_switch_profile_ids": [
                        {
                            "key": "UplinkHostSwitchProfile",
                            "value": "/infra/host-switch-profiles/ace9be64-9728-4340-968e-a62dae6a3d00"
                        },
                        {
                            "key": "VtepHAHostSwitchProfile",
                            "value": "/infra/host-switch-profiles/0de8282e-7385-4e8e-a905-0c11960db728"
                        }
                    ],
                    "host_switch_type": "VDS",