Closed BigDataKatha closed 5 years ago
https://everymundo.github.io/emDataStandards/documentation/build/#farenet3.0-farenet-3.0
Issue: Currently, the variable routeType can be populated with NONSTOP, CONNECTING, CODESHARE. https://github.com/EveryMundo/emDataStandards/blob/543463c46f5dd65a197f2e15f2d121526941395d/types/flight.schema.json#L309-L313 However, if we populate the variable with CODESHARE, the flight can still be NONSTOP or CONNECTING.
Solution:
Populate routeType only with NONSTOP OR CONNECTING, so that:
"routeType": { "description": "NONSTOP, CONNECTING", "type": "string", "example": "NONSTOP" }
and leverage the existing boolean variable "isCodeshare" to indicate if the flight is a codeshare or not. https://github.com/EveryMundo/emDataStandards/blob/543463c46f5dd65a197f2e15f2d121526941395d/types/fareNet3.0.schema.json#L717-L721
@danielsan @neilgoldman @darielnoel @yartiles @EveryMundo/em-microservices-admin @howardem @anahiem @unoriginalbanter
@anaiscorinne and I agreed to move forward with this. I will be laying out the documents that need to be updated.
I updated: flight_base.schema.json
https://everymundo.github.io/emDataStandards/documentation/build/#farenet3.0-farenet-3.0
Issue: Currently, the variable routeType can be populated with NONSTOP, CONNECTING, CODESHARE. https://github.com/EveryMundo/emDataStandards/blob/543463c46f5dd65a197f2e15f2d121526941395d/types/flight.schema.json#L309-L313 However, if we populate the variable with CODESHARE, the flight can still be NONSTOP or CONNECTING.
Solution:
Populate routeType only with NONSTOP OR CONNECTING, so that:
and leverage the existing boolean variable "isCodeshare" to indicate if the flight is a codeshare or not. https://github.com/EveryMundo/emDataStandards/blob/543463c46f5dd65a197f2e15f2d121526941395d/types/fareNet3.0.schema.json#L717-L721
@danielsan @neilgoldman @darielnoel @yartiles @EveryMundo/em-microservices-admin @howardem @anahiem @unoriginalbanter