Details
-
Type:
Epic
-
Status: Invalid
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: Qserv
-
Labels:None
-
Epic Name:F16 Replace mysql-proxy - czar xml-rpc protocol with REST
-
WBS:02C.06.02.03
-
Team:Data Access and Database
Description
xml-rpc for communication between mysql proxy and czar is pretty sketchy and we always treated it as a temporary solution. Once RESTful API to qserv matures, we should replace the xml-rpc with REST. This was discussed at https://confluence.lsstcorp.org/display/DM/Qserv+Hangout+2015-02-04
Attachments
Issue Links
Activity
Summary | Replace mysql-proxy - czar xml-rpc protocol with REST | FY16 Replace mysql-proxy - czar xml-rpc protocol with REST |
Link | This issue relates to DLP-31 [ DLP-31 ] |
Cycle | Summer 2016 [ 10803 ] |
Summary | FY16 Replace mysql-proxy - czar xml-rpc protocol with REST | S16 Replace mysql-proxy - czar xml-rpc protocol with REST |
Rank | Ranked higher |
Epic Name | FY16 Replace mysql-proxy - czar xml-rpc protocol with REST | S16 Replace mysql-proxy - czar xml-rpc protocol with REST |
Rank | Ranked lower |
Rank | Ranked higher |
Story Points | 50 |
Story Points | 50 | 45 |
Resolution | Done [ 10000 ] | |
Status | To Do [ 10001 ] | Invalid [ 11005 ] |
Story Points | 45 |
Cycle | Summer 2016 [ 10803 ] |
Rank | Ranked higher |
Epic Status | To Do [ 10101 ] | Done [ 10103 ] |
Summary | S16 Replace mysql-proxy - czar xml-rpc protocol with REST | F16 Replace mysql-proxy - czar xml-rpc protocol with REST |
Epic Name | S16 Replace mysql-proxy - czar xml-rpc protocol with REST | F16 Replace mysql-proxy - czar xml-rpc protocol with REST |
Reporter | Jacek Becla [X] [ jbecla ] | Fritz Mueller [ fritzm ] |