Bug 933 AMP - Eliminate the usage of SQL queries from GUI/APIs payload

Review Request #316 — Created July 8, 2024 and submitted

pmurugaiyan
AMP
amp_bug_fixes_base_3_6_0
933
apoorva.sn, prajesh, shuinvy

AMP - Eliminate the usage of SQL queries from GUI/APIs payload

The changes tested locally with Postman and for UI whereever possible with the limited data. All API changes are tested with Postman.

Description From Last Updated

should we expose the function name we are calling ? or can we rename the 'key' name so that it …

apoorva.snapoorva.sn

Can we rename this field to query_params or something similar ?

apoorva.snapoorva.sn

UI still need to know what function it should call in the backend. Can we decouple this?

prajeshprajesh
shuinvy
  1. Ship It!
  2. 
      
apoorva.sn
  1. 
      
  2. Can we rename this field to query_params or something similar ?

    1. Query params means graps values from dynamic parts of URL. So that will give us a different meaning. Since this filed is being used for querying the data I have named with 'query' (Similar to Kibana 'queries'). If 'queries' works we can use that. Parameter/Params might not be a suitable key at the JSON context.

  3. 
      
apoorva.sn
  1. 
      
  2. should we expose the function name we are calling ?
    or can we rename the 'key' name so that it is not explicit that we are calling a function with this name

  3. 
      
prajesh
  1. 
      
  2. UI still need to know what function it should call in the backend. Can we decouple this?

    1. Yes Praveen, we have that dependency. Since we are using a single http entry point (/composer_query) we have to define the target from UI to process the request (now we are calling it as action - the python function name).

  3. 
      
pmurugaiyan
prajesh
  1. Ship It!
  2. 
      
apoorva.sn
  1. Ship It!
  2. 
      
pmurugaiyan
Review request changed

Status: Closed (submitted)

Loading...