You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »

State

[progress record]:

Proposed time: 2022/08/30

Discussion time: 2022/08/30

Accept/reject time: 2022/08/30

Complete time:

[issues]：

[email]: After creating the LKIP and writing the preliminary content, start a discussion on the LKIP proposal. Currently, the discussion must be initiated in the WeChat group [Apache Linkis Community Development Group], and the minutes can be sent to the official dev mailbox of linkis. The email address for the minutes can be placed here

[release]: The (planned) release version of Linkis

[proposer]：

Motivation & Background

When the current linkis entrance is executed, the user needs to associate the userCreator and tenant to the ECM, and the tenant label is automatically matched. The purpose is to no longer associate the user with the userCreator and tenant. linkis automatically matches the identifier to the user's execution task by configuring

Basic concept

Expect to achieve goals

  • linkis does not require users to add tags by themselves, but is added to the execution tasks by linkis, users only need to configure

Implementation plan

  • By intercepting, get the jobRequest, get the user's information, match the label information configured by the user, and then add the label information to the execution task.
  • flow chart:

Function realization

a) Data cache

  • Cache tenant tag table information (the principle is the same as that of sensitive table interception and cache data)
  • When the configuration table is updated, the cache is updated (increased)

b) Data configuration

  • Add a new page for data configuration demo: hadoop-IDE can be associated with tenant1
  • The configuration relationship can only be one label per user. demo:hadoop-IDE is associated based on user-creatorLabel
  • Tenant can be configured
  • When adding or modifying, determine the ECM resource corresponding to the tenant. If there is no corresponding tenant, an error message will be displayed, "Add/modify failed, contact the administrator to add the ECM corresponding to the label"
  • Automatically insert configuration for new users to do label judgment
  • monitor configuration detection alarm

Changes


Modification Detail
1
Modification of maven module


2Modification of HTTP interface
Interface name Function Remarks
createTenantAdd tenant label (new tenant label mapping relationship)creator is in front, _ underscore link, department abbreviation or all, _ underline link, 01, 02 serial number increments (corresponding machine)
updateTenantModify the tenant label
deleteTenantdeletes the tenant label
queryTenantListquery tag list
3Modification of the client interface
4Modification of database table structure

Added tenant label correspondence table

Field Type Name Remarks
id numberserial 
user varchar user
creator  varcharcreator
tentant_value varchar Tenant
create_time datetime create time
update_time datetime update time
desc varchar  sources ofbusiness
bussiness_user varchar docking person
user_creator key index
5Modification of configuration item
6Modification Error code 
7Modifications for Third Party Dependencies

Compatibility, Deprecation, and Migration Plan

  • What impact (if any) will there be on existing users?
  • If we are changing behavior, how will we phase out the older behavior?
  • If we require special migration tools, describe them here.
  • When will we remove the existing behavior?


  • No labels