Hi Jintao,

Glad to hear that. 


My concern is that whether the formats of rest apis in spring mvc will be kept? 
As we know, many users work with their Kylins through rest apis.



Best regards,

 

Ni Chunen / George



On 08/6/2019 14:36,zjt<[email protected]> wrote:
Hi Team:


Next, I will do these things to upgrade kylin from springmvc architecture to 
springbok architecture.
1. Modify the project's pom.xml to import the spring boot dependency.
2. Upgrade kylin-server from spring mvc to springbok 1.5.5, modify kylin-server 
code to support spring boot.
3. Modify the build&package script, package kylin into to a war package and run 
it as external tomcat mode. It's the same as current deployment.


I have implemented this part or the features and conducted a simple test. I 
expect to submit my code to the "KYLIN-4125" branch this week.












-------- Forwarding messages --------
From: "zhao jintao (JIRA)" <[email protected]>
Date: 2019-08-06 11:53:00
To:  [email protected]
Subject: [jira] [Created] (KYLIN-4125) Kylin upgraded from springmvc 
architecture to spring boot architecture
zhao jintao created KYLIN-4125:
----------------------------------

Summary: Kylin upgraded from springmvc architecture to spring boot architecture
Key: KYLIN-4125
URL: https://issues.apache.org/jira/browse/KYLIN-4125
Project: Kylin
Issue Type: Improvement
Components: REST Service
Reporter: zhao jintao
Assignee: zhao jintao


Hi Team:

Kylin is based on the spring mvc architecture, but the spring mvc configuration 
is more complicated. It is cumbersome when integrateing new components.

Now, The mainstream of the industry has been based on the spring boot 
architecture. Spring boot can be automatically configured to reduce the 
complexity of project integration; promote the expansion and implementation of 
microservice architecture. More and more project architectures have been 
upgraded from springmvc to spring boot.

Kylin can also be upgraded from the springmvc architecture to the spring boot 
architecture.


Do you have any suggestions?



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Reply via email to