Dev 1.0.3 #1
Merged
Dev 1.0.3 #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…d, resuslt in can't find instace from eureka. for example,hostname:linkis-cg-linkis-cg-engineconnmanager-1, aplicationName:linkis-cg-engineconnmanager,the service registed in eureka "linkis-cg-linkis-cg-engineconnmanager-1:linkis-cg-linkis-cg-engineconnmanager:9102", instanceId.toLowerCase.indexOf(applicationName.toLowerCase) will return 0.
reason: in table linkis_cg_manager_service_instance and table linkis_cg_manager_service_instance_metrics, 'instance' is 128,but in linkis_ps_instance_label_relation(service_instance)、linkis_cg_manager_label_service_instance(service_instance)、linkis_cg_manager_engine_em(engine_instance、em_instance) is 64. if hostname use fqdn, then length will longer than 64,such as 'linkis-cg-engineconnmanager-0.linkis-svc.default.svc.cluster.local'
for example, hostname: linkis-cg-engineconnmanager-0.linkis-svc.default.svc.cluster.local serviceName:linkis-cg-engineconnmanager str:linkis-cg-engineconnmanager-linkis-cg-engineconnmanager-0.linkis-svc.default.svc.cluster.local:9104 after setStringValue: instance = -0.linkis-svc.default.svc.cluster.local:9104 correct value should be: linkis-cg-engineconnmanager-0.linkis-svc.default.svc.cluster.local:9104
2. Add special judgment for uri without user login.
Adjust some unnecessary parameters in the BML APIs
…verLoader bugFix: when hostname start with applicationName, will cause parse faile…
…CloumnWidth bugFix:unified the width of all instance related field to be 128.
bugFix:instance Label parase failed when hostname contains servicename.
add log for location issue #435
Add special judgment for uri without user login in Linkis-module.
Support engine operator
This reverts commit 7b7e183.
remove old license and add new apache license for dev-1.0.3
…ven-assembly-plugin 2.3 to 3.2.0
Resolve the code conflicts
Add the support of EngineConn common operators and OnceEngineConn common operators.
Dev 1.0.3
Unify the exception class of engineConnPlugin in one package
Resolve the code conflicts.
[ISSUS#1080] bugfix:build dist ignore empty directory of 'python' after upgrade maven-assembly-plugin 2.3 to 3.2.0
remove some limit of package and some junk file
weipengfei-sj
pushed a commit
that referenced
this pull request
Apr 19, 2022
Merge 1.1.0 latest code
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What is the purpose of the change
(For example: EngineConn-Core defines the the abstractions and interfaces of the EngineConn core functions.
The Engine Service in Linkis 0.x is refactored, EngineConn will handle the engine connection and session management.
Related issues: apache#590. )
Brief change log
(for example:)
Verifying this change
(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)
Does this pull request potentially affect one of the following parts:
Documentation