NeuronEX Docs

English

简体中文

English

简体中文

Appearance

Contact Us
Try for Free

HTTP Pull ​

Stream Scan table

The NeuronEX data processing module can obtain data from the HTTP server through the HTTP Pull type of data source, which can be used as a data source for streams and scan tables.

Create stream ​

Log in to NeuronEX and click Data Processing -> Source. On the Stream tab, click Create Stream.

In the pop-up Source/Create page, enter the following configuration:

  • Stream Name: Enter the stream name

  • Whether the schema stream: Check to confirm whether it is a structured stream. If it is a structured stream, you need to add further stream fields. It can be unchecked by default.

  • Stream Type: Select httppull.

  • Data source (URL Endpoint): The path part of the specified URL is concatenated with the path attribute in the configuration key to form the final URL. For example, the path attribute in the configuration key is filled in as http://127.0.0.1:7000, and the data source (URL splicing path) is filled in as /api/data, then the complete HTTP request address is :http://127.0.0.1:7000/api/data.

  • Configuration key: You can use the default configuration key. If you want to customize the configuration key, you can click the Add Configuration key button and make the following settings in the pop-up dialog box.

    • Name: Enter the configuration key name.

    • Path: Specify the address of the requested server.

    • HTTP method: HTTP request method, which can be post, get, put or delete.

    • Interval: The time interval between two requests, in milliseconds.

    • Timeout: HTTP request timeout, in milliseconds.

    • Increment: If set to True, the result will be compared with the last time; if the response of two consecutive requests is the same, the new result will not be sent. The default value is False.

    • Text: The body of the request, for example {"data": "data", "method": 1}.

    • Text type: Text type, which can be none, text, json, html, xml, javascript or form.

    • Certificate Type: Optional parameter, fill in the certificate path, which can be an absolute path or a relative path. If a relative path is specified, the parent directory is the path where the neuronex command is executed. Example value: /var/xyz-certificate.pem

    • Private key path: Optional parameter, which can be an absolute path or a relative path. Example value: /var/xyz-private.pem.key

    • Root Certificate Path: Optional parameter to verify the server certificate. It can be an absolute path or a relative path. Example value: /var/xyz-rootca.pem

    • Skip certificate verification: Control whether to skip certificate verification. If set to True, certificate verification will be skipped; otherwise, certificate verification will be performed.

    • HTTP Headers: HTTP request headers that need to be sent with the HTTP request.

    • Response type: Response type, which can be code or body. If it is code, NeuronEX will check the HTTP response code to determine the response status. If body is used, NeuronEX checks the HTTP response body, requires it to be in JSON format, and checks the value of the code field. Defaults to code.

    • oAuth: Configure the OAuth verification process.

      • access

        • url: The URL to obtain the access code, always use the POST method to access.
        • body: The request body to obtain the access token. Typically, the authorization code is provided here.
        • expire: The expiration time of the token, the time unit is seconds, templates are allowed, so it must be a string.

      • refresh

        • url: URL of the refresh token, always requested using POST method.
        • headers: Request headers used for refresh tokens. The token is usually placed here for authorization.
        • body: The request body of the refresh token. When using a header file to pass refresh tokens, you may not need to configure this option.

  • Streaming Format: Select the default json format.

  • Shared: Check to confirm whether to share the source.

An example configuration is as follows:

yaml

default:
   #Request the URL of the server address
   url: http://localhost:7000
   # post, get, put, delete
   method: post
   # Interval between requests, time unit is ms
   interval: 10000
   # http request timeout, time unit is ms
   timeout: 5000
   # If it is set to true, it will be compared with the last result; if the responses of both requests are the same, sending the result will be skipped.
   # Possible settings may be: true/false
   incremental: false
   # Request body, for example '{"data": "data", "method": 1}'
   body: '{}'
   # Text type, none, text, json, html, xml, javascript, form
   bodyType: json
   # Request the required HTTP headers
   headers:
     Accept: application/json
   # How to check the response status, support through status code or body
   responseType: code
   # Get token
#oAuth:
# # Set how to obtain the access code
# access:
# # Get the URL of the access code, always use the POST method to send the request
# url: https://127.0.0.1/api/token
# # Request text
# body: '{"username": "admin","password": "123456"}'
# # The expiration time of the token, expressed as a string, the time unit is seconds, templates are allowed
# expire: '3600'
# # How to refresh token
#refresh:
# # Refresh token URL, always use POST method to send request
# url: https://127.0.0.1/api/refresh
# # HTTP request header, allowing the use of templates
# headers:
# identityId: '{{.data.identityId}}'
# token: '{{.data.token}}'
# # Request text
# body: ''

Create scan table ​

HTTP pull sources support lookup tables. Log in to NeuronEX and click Data Processing -> Source. On the Scan Table tab, click Create Scan Table.

  • Table Name: Enter the table name

  • Whether the schema stream: Check to confirm whether it is a structured table. If it is a structured table, you need to add further table fields.

    • name: field name
    • Type: supports bigint, float, string, datetime, boolean, array, struct, bytea

  • Table Type: Select httppull

  • Data source (URL Endpoint): The path part of the specified URL is concatenated with the path attribute in the configuration key to form the final URL. For example, the path attribute in the configuration key is filled in as http://127.0.0.1:7000, and data source (URL Endpoint) is filled in as /api/data, then the complete HTTP request address is :http://127.0.0.1:7000/api/data.

  • Configuration key: You can use the default configuration key. If you want to customize the configuration key, please refer to the [Create Stream](#Create Stream) section

  • Table format: supports json, binary, delimited, custom.

  • Retain Size: Specify the Retain size.