Hi, IMO its better if we share the real user story behind the creating labels in gateway level. (Is it only for grouping purpose? ) Also whats the difference between current tags vs labels?
Regards, *Dakshika Jayathilaka* PMC Member & Committer of Apache Stratos Associate Technical Lead WSO2, Inc. lean.enterprise.middleware 0771100911 On Tue, May 8, 2018 at 11:05 AM Chamin Dias <cham...@wso2.com> wrote: > Hi all, > > Thanks for the responses. > > This is to communicate a concern/conclusion regarding the flow (attaching > labels). > > *Using the UI (API Publisher)* > > 1. We have decided to fetch the existing labels and provide the option to > select the labels. This improved the user experience because there is no > need to remember the labels in advance. > > 2. In this case, (since the attached labels are already there in the > system) we do not need to validate the labels at API creation time. > > > *Using the REST API* > > 1. As discussed, we hope to introduce new section in the payload. > Eg : > "labels":[ > "wso2", > "development" > ] > > 2. In this approach, the user needs to know the existing labels in > advance. However, if he types a non existing label (by mistake or > intentionally), we need to validate the labels at API creation (saving) > time. We will attach only the existing/valid labels and create the API > (because adding new labels is an admin task - in admin dashboard). We can > print a message in the console saying that the invalid labels have been > skipped. > > 3. Accordingly (when using the REST API) we need to do the validation > call, at API creation time. > > Please provide your feedback if you have any optimization for this. > > Thanks. > > On Mon, May 7, 2018 at 10:33 AM, Sanjeewa Malalgoda <sanje...@wso2.com> > wrote: > >> +1. Lets go with rxt option for the moment as other search options are >> also based on same design. >> >> Thanks, >> sanjeewa. >> >> On Sun, May 6, 2018 at 12:48 AM, Prasanna Dangalla <prasa...@wso2.com> >> wrote: >> >>> Hi, >>> >>> On Fri, May 4, 2018 at 5:58 PM Nuwan Dias <nuw...@wso2.com> wrote: >>> >>>> I think it should be in the rxt as a field. Storing it as a property >>>> seems like a hack to me. And yes, storing on a separate DB will cause >>>> complications with queries since the rest of the data is in the rxt. >>>> >>> >>> If we Include as a feild in API rxt, then the search issue that Malintha >>> pointed out will also be solved. >>> +1 to go with a feild in the rxt. >>> >>> Thanks >>> Prasanna >>> >>>> >>>> On Fri, May 4, 2018 at 5:45 PM, Malintha Amarasinghe < >>>> malint...@wso2.com> wrote: >>>> >>>>> Hi, >>>>> >>>>> On Fri, May 4, 2018 at 11:15 AM, Prasanna Dangalla <prasa...@wso2.com> >>>>> wrote: >>>>> >>>>>> >>>>>> HI, >>>>>> >>>>>> >>>>>> >>>>>> On Fri, May 4, 2018 at 11:07 AM Chamin Dias <cham...@wso2.com> wrote: >>>>>> >>>>>>> On Fri, May 4, 2018 at 9:19 AM, Dinusha Dissanayake < >>>>>>> dinus...@wso2.com> wrote: >>>>>>> >>>>>>>> >>>>>>>>> >>>>>>>>> AFAIU we are going to use labels when downloading a subset of APIs >>>>>>>>> via Microgateway. If it is not mandatory to have the labels, how are >>>>>>>>> we >>>>>>>>> going to handle the APIs without labels in Microgateway? Are we not >>>>>>>>> going >>>>>>>>> to download the APIs without labels? >>>>>>>>> >>>>>>>>> As Sachini has mentioned above if a subset of APIs to be deployed >>>>>>>> in the micro gateway, it needs to have a label. Say if APIs have a >>>>>>>> default >>>>>>>> label called "def_label". Then if we call "setup def_label", all the >>>>>>>> APIs >>>>>>>> will be deployed in the micro gateway. Hence I do not think having a >>>>>>>> default label would add a significant value. Only the APIs needed to be >>>>>>>> deployed in the micro gateways will have labels AFAIR. (please correct >>>>>>>> me >>>>>>>> if I am wrong) >>>>>>>> >>>>>>> >>>>>>> Agree with Dinusha. As per the previous discussions >>>>>>> <http://mail.wso2.org/mailarchive/architecture/2018-May/030704.html> >>>>>>> also this fact has been confirmed. Hence the business value of adding a >>>>>>> default label would be minor IMHO. >>>>>>> >>>>>> Yes IMO too it not mandaory to add a default value to the label. >>>>>> >>>>>> We need to decide, how we are storing the label vales that are >>>>>> attched to a specific label. There are three options as for the >>>>>> discussion >>>>>> had. >>>>>> >>>>>> - Store it as an API RXT filed value. >>>>>> - Add the label as a property to the API reource >>>>>> - Add the label to AM_DB >>>>>> >>>>>> All curent search queries we are running in registry(solr). If we use >>>>> a seperate mapping in AM_DB, we might not be able to use multiple searches >>>>> at the same time, eg: search APIs which have has label "Internal" status: >>>>> "PUBLISHED" or "PROTOTYPED" since we do not keep status in the DB. >>>>> >>>>> So I think we need to go for option 1 or 2. WDYT? >>>>> >>>>> Can we store multivalued attributes in registry properties? >>>>> >>>>> Thanks! >>>>> Malintha >>>>> >>>>> >>>>>> Your thoughts on the above factor is hoghly appreciated. >>>>>> >>>>>> @Chamin: Can you share a digram of the floor that we discussed. >>>>>> >>>>>> Thanks >>>>>> Prasanna >>>>>> >>>>>> >>>>>>> >>>>>>>> >>>>>>>> Thanks, >>>>>>>> DinushaD. >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Architecture mailing list >>>>>>>> Architecture@wso2.org >>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Chamin Dias >>>>>>> Mobile : 0716097455 >>>>>>> Email : cham...@wso2.com >>>>>>> LinkedIn : https://www.linkedin.com/in/chamindias >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Architecture mailing list >>>>>>> Architecture@wso2.org >>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Architecture mailing list >>>>>> Architecture@wso2.org >>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Malintha Amarasinghe >>>>> *WSO2, Inc. - lean | enterprise | middleware* >>>>> http://wso2.com/ >>>>> >>>>> Mobile : +94 712383306 >>>>> >>>>> _______________________________________________ >>>>> Architecture mailing list >>>>> Architecture@wso2.org >>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>> >>>>> >>>> >>>> >>>> -- >>>> Nuwan Dias >>>> >>>> Software Architect - WSO2, Inc. http://wso2.com >>>> email : nuw...@wso2.com >>>> Phone : +94 777 775 729 >>>> _______________________________________________ >>>> Architecture mailing list >>>> Architecture@wso2.org >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>> -- >>> *Prasanna Dangalla* >>> Senior Software Engineer, WSO2, Inc.; http://wso2.com/ >>> lean.enterprise.middleware >>> >>> >>> *cell: +94 718 11 27 51* >>> *twitter: @prasa77* >>> >>> _______________________________________________ >>> Architecture mailing list >>> Architecture@wso2.org >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> *Sanjeewa Malalgoda* >> WSO2 Inc. >> Mobile : +94 712933253 >> >> <http://sanjeewamalalgoda.blogspot.com/>blog >> :http://sanjeewamalalgoda.blogspot.com/ >> <http://sanjeewamalalgoda.blogspot.com/> >> >> >> >> _______________________________________________ >> Architecture mailing list >> Architecture@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > Chamin Dias > Mobile : 0716097455 > Email : cham...@wso2.com > LinkedIn : https://www.linkedin.com/in/chamindias > > _______________________________________________ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
