Check out Code Sample

Analysis chart (Chart) is mainly used to arrange data statistics analysis query logic, supports the use of JavaScript scripts to process the results of each query node, can directly view the analysis chart in the data management background, and can also be used as a process (process), The reference method is charts.<analytical chart name>. Analysis chart (Chart) supports data analysis engines based on ElasticSearch and MySQL for various business scenarios.

Data kanban and data big screen pages can also be written in the same way.

Data kanban, analysis charts, data screen related processes.

The analysis chart description file is a JSON text file named with lowercase English letters + .chart.json extension, <name>.chart.json; The result processing script file is a JavaScript script file named <name>.<script>.js with the extension of Analysis chart name + . + script name + .js.

The extension of the data kanban is .kan.json, and the extension of the big data screen is .scr.json

The analysis chart layout document consists of basic information, query nodes, output data, and analysis page rendering parameters.

{
  "lang": "gou",
  "label": "Latest Information",
  "version": "1.0.0",
  "description": "Latest Information",
  "nodes": [],
  "output": {},
  "apis": {},
  "filters": {},
  "page": {}
}

Write a data kanban description file pet.kan.json and place it in the application's kanban directory.

Description file content:

Application Directory Structure:

├── apis # Used to store interface description files
│ └── pet.http.json
├── models # Used to store data model description files
│ └── pet.mod.json
├── tables # Used to store data table description files
│ └── pet.tab.json
├── kanban # Used to store data kanban description files
│ └── pet.kan.json
├── db
└── ui
└── app.json

Access Kanban interface:

Page route: /xiang/kanban/<Kanban Name>

1. Enter https://127.0.0.1:5099/xiang/kanban/pet in the address bar

2. It is recommended to add the /xiang/kanban/pet route as a menu item.

{
  "nodes": [
    {
      "name": "Industry Distribution",
      "query": {
        "model": "service",
        "select": ["city", ":COUNT(id) as cnt", "@industries.$ as industry"],
        "wheres": [
          { "column": "created_at", "value": "{{$query.from}}", "op": "ge" },
          { "column": "created_at", "value": "{{$query.to}}", "op": "le" }
        ],
        "order": ["cnt.desc"],
        "limit": 100,
        "group": ["@industries.$", "city"]
      }
    },
    {
      "name": "Billing method",
      "query": {
        "model": "service",
        "select": ["city", ":COUNT(id) as cnt", "@price_options.$ as option"],
        "wheres": [
          { "column": "created_at", "value": "{{$query.from}}", "op": "ge" },
          { "column": "created_at", "value": "{{$query.to}}", "op": "le" }
        ],
        "order": ["cnt.desc"],
        "limit": 100,
        "group": ["@price_options.$", "city"]
      }
    },
    {
      "name": "Merge result",
      "process": "xiang.chart.MergeData",
      "args": [
        ["city", "industry", "billing"],
        {
          "Industry": {
            "key": "city",
            "values": "{{$res.Industry distribution[*].industry}}"
          },
          "Billing": {
            "key": "city",
            "values": "{{$res.Billing method[*].option}}"
          }
        }
      ]
    }
  ]
}

An analysis chart query orchestration (Chart) can have multiple query nodes, each query node also writes and sets the query query parameters corresponding to the data engine, or calls a process (process), which can specify the result Processing scripts and return values ​​can be used to reference contextual information in query nodes. The context data reference and result processing script are specifically consistent with the business logic orchestration (Flow).

Object Node data structure

The data and configuration query interface is enabled by default in the analysis chart. You can disable the interface, set the authentication method and default value options by setting the same key settings.

{
  "apis": {
    "data": {
      "disable": true,
      "guard": "bearer-jwt",
      "default": {}
    },
    "setting": {
      "guard": "-",
      "default": {}
    }
  }
}