No irony at all, I am serious. Any effort is valuable for the project. Andrey Pokhilko
On 07/23/2017 06:19 PM, Philippe Mouawad wrote: > On Sun, Jul 23, 2017 at 5:09 PM, Andrey Pokhilko <[email protected]> wrote: > >> Hi Philippe, >> >> My question is not about dropping, it is about usage level we know and >> _possible deprecating_ based on that. Maintaining code that is barely >> used could be unnecessary burden for the project. >> > I see it as a burden when the underlying protocol changes and we need to > update it frequently while not sure it is useful. > In the case of the protocols mentioned, it looks to me that those protocols > are now very stable and only require little work. > > Besides they are potentially useful within Automation of a Test Plan: > > - LDAP => Create a CSV from a set of users having some LDAP attribute or > belonging to a group > - FTP => Getting or uploading some files > - MAIL / SMTP => Sent a mail based on test results or test state... > > Having those protocols within JMeter is interesting IMO. > > >> For example I have feeling that LDAP as protocol should be rarely used >> in JMeter just because protocol itself is declining (my assumption is >> based on things like >> https://trends.google.ru/trends/explore?date=all&q=ldap,oauth,openid or >> https://www.quora.com/Why-isnt-LDAP-dead-yet) >> >> From your comments I understood that you see interest on SO for all >> modules except LDAP. This matches my intuitive expectation. >> > I am not even sure of that. We had recently bug reports on Ldap. > I already used it within my work. > I was just mentioning the sources for "usage and popularity" > > >> Thanks for your analysis on usage of components, it's valuable >> information for all of us. >> > I don't pretend to have such a great analysis you are crediting me of > ironically or not :-) > > Clearly it would have been great to know usage based on reporting as > Emilian proposed. > It would have also been great if the plugins manager was part of JMeter > core and there was an Apache repository for Core plugins which would maybe > make it possible to distribute a small bundle. > But it's not the case. > > >> Andrey Pokhilko >> >> On 07/23/2017 05:34 PM, Philippe Mouawad wrote: >>> Hello Andrei, >>> I don't see why we should drop elements that are not deprecated and are >>> used based on bug reports, SO questions. >>> >>> MongoDB is not in that case as we can consider we are not maintaining it >>> and it is deprecated since many months. >>> >>> >>> Regards >>> >>> On Sun, Jul 23, 2017 at 4:27 PM, Andrey Pokhilko <[email protected]> wrote: >>> >>>> Based on these reasons, don't we see also worth deprecating: >>>> >>>> 1. Mail/SMTP components >>>> >>> AKAIK, they are not deprecated. And are useful, I saw several questions >> on >>> SO >>> >>>> 2. LDAP components >>>> >>> AKAIK, they are not deprecated. >>> >>>> 3. FTP >>>> >>> AKAIK, they are not deprecated. And are useful, I saw several questions >> on >>> SO >>> >>>> 4. Any of other distribution bundle modules (junit/tcp etc) >>>> >>> AKAIK, they are not deprecated, neither JUnit nor TCP which is used a lot >>> from SO questions.. >>> >>> >>> >>>> Possible benefits for users is cleaner UI menus, smaller distribution >>>> archive size, faster JMeter startup. Do we have estimations of >>>> importance of those parts of JMeter? >>>> >>>> Andrey Pokhilko >>>> >>>> On 07/20/2017 10:15 PM, Philippe Mouawad wrote: >>>>> Hello, >>>>> The decision to deprecate was motivated by many reasons: >>>>> >>>>> - Very low feedback both on SO, bugzilla and user mailing list >>>>> - No mention at all from MongoDB which seems to have its own tool >>>>> - The effort to upgrade (lot of deprecations) + the fact that an >> async >>>>> driver was released and that might be a better choice >>>>> - The fact that we need to make choices based on priorities :-) JDBC >>>>> sampler addresses many DB, MongoDB addresses 1 Product. I think it >>>> was a >>>>> mistake to add it (my mistake :-) ) >>>>> >>>>> Regards >>>>> >>>>> On Wed, Jul 19, 2017 at 6:19 PM, John Schulz <[email protected]> >>>> wrote: >>>>>> When the decision was made to deprecate no one was volunteering to >>>> update >>>>>> it. If we have volunteers then the volunteer(s) can update the driver. >>>>>> Mongo becomes undeprecated. >>>>>> >>>>>> Sent from my iPhone >>>>>> >>>>>>> On Jul 19, 2017, at 10:02 AM, Antonio Gomes Rodrigues < >>>> [email protected]> >>>>>> wrote: >>>>>>> Issues, question in stackoverflow... >>>>>>> >>>>>>> 2017-07-19 16:00 GMT+02:00 Emilian Bold <[email protected]>: >>>>>>> >>>>>>>> Out of curiosity, how do you measure usage? Based on issues opened? >>>>>>>> >>>>>>>> --emi >>>>>>>> >>>>>>>> >>>>>>>> On Wed, Jul 19, 2017 at 3:19 PM, Antonio Gomes Rodrigues >>>>>>>> <[email protected]> wrote: >>>>>>>>> Hi, >>>>>>>>> >>>>>>>>> If I remember it's because we have few time to update it and >> because >>>>>> it's >>>>>>>>> not very used >>>>>>>>> >>>>>>>>> Antonio >>>>>>>>> >>>>>>>>> 2017-07-19 14:15 GMT+02:00 Emilian Bold <[email protected]>: >>>>>>>>> >>>>>>>>>> I don't know why the MongoDB protocol got deprecated, but the next >>>>>>>>>> step would be removal of the classes not updating libraries. >>>>>>>>>> >>>>>>>>>> --emi >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Wed, Jul 19, 2017 at 12:55 PM, Maxime Chassagneux >>>>>>>>>> <[email protected]> wrote: >>>>>>>>>>> Hi, >>>>>>>>>>> >>>>>>>>>>> The JMeter bundle still include a mongoDB java driver ( version >>>>>>>> 2.11.3 ) >>>>>>>>>>> which is really old and doesn't work with all authentication >>>>>>>>>>> >>>>>>>>>>> By example : >>>>>>>>>>> >>>>>>>>>>> javax.script.ScriptException: java.lang. >> IllegalArgumentException: >>>>>>>>>>> Unsupported authMechanism: SCRAM-SHA-1 >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> As mongoDB is deprecated in JMeter, my question is : Should we >> keep >>>>>>>> this >>>>>>>>>>> librairie or update it to the lastest version ? >>>>>>>>>>> >>>>>>>>>>> Thanks for ur feedback. >> >
