[openstack-dev] [mistral] [murano] [yaql] An online YAQL evaluator [was RE: [mistral] [murano] An online YAQL evaluator]

Stan Lagun slagun at mirantis.com
Sun Jan 17 00:25:12 UTC 2016


Very cool, indeed! Even myself (developer of yaql) often use yaqluator
instead of yaql CLI :)

Finally took a time to see source codes.
Few tips that you may find useful:
* The most expensive operation in yaql is YaqlFactory.create(). This
method builds a parser and it takes significant time (orders of
magnitude more then expression parsing). I see that you create
factory/parser
  on each evaluation. However parser was designed to be immutable and
thread safe so it may be reasonable to create it only once (+1 for
legacy mode) and reuse it across queries. This will make a big
difference
  if the site become popular
* You don't use engine options. There are number of useful settings
that allow to limit iterator length or memory usage. For example looks
like I killed the site by executing [1, 2].cycle() which returns
indefinite collection.
   Sorry for that. Another useful option is the one that converts sets
to lists on output. Without it set function cannot be used in
yaqluator. Also see [1]

[1]: https://review.openstack.org/#/c/268673/
Sincerely yours,
Stan Lagun
Principal Software Engineer @ Mirantis



On Wed, Jan 13, 2016 at 9:17 AM, Renat Akhmerov <rakhmerov at mirantis.com> wrote:
> Very cool! It now even supports code assistance :)
>
> Moshe, can’t stop saying good words :) Amazing!
>
> Renat Akhmerov
> @ Mirantis Inc.
>
>
>
> On 22 Dec 2015, at 23:06, ELISHA, Moshe (Moshe)
> <moshe.elisha at alcatel-lucent.com> wrote:
>
> Hi all,
>
> Thank you for the kind words.
> Just wanted to let you know that yaqluator[1] was updated and now supports
> YAQL 1.0.2.
> There is also a checkbox there to work in “Legacy Mode”.
>
> Hope you will find it useful.
>
> [1] http://yaqluator.com/
>
>
> From: Renat Akhmerov [mailto:rakhmerov at mirantis.com]
> Sent: Friday, August 14, 2015 11:51 AM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [mistral] [murano] An online YAQL evaluator
>
> I just read this thread so decided to add my 2 cents into the collection of
> opinions.
>
> Guys, I tried it out a couple of weeks ago (was told about it by one of my
> colleagues). This is really incredible! Especially given that you completed
> it in 24 hours :) I think as YAQL attracts more and more users it will be
> very handy tool. I am actually for improving it further.
>
> Thanks a lot! Looking forward to switch to yaql 1.0!
>
> Renat Akhmerov
> @ Mirantis Inc.
>
>
>
>
> On 05 Aug 2015, at 04:09, Stan Lagun <slagun at mirantis.com> wrote:
>
> Dmitry,
>
> yaql 1.0 has both str() and len() and much much more so there is no need to
> support them explicitly since Mistral is going to switch to yaql 1.0 and
> yaqluator.com is going to do the same
>
> Sincerely yours,
> Stan Lagun
> Principal Software Engineer @ Mirantis
>
>
>
> On Tue, Aug 4, 2015 at 8:55 PM, Dmitri Zimine <dzimine at stackstorm.com>
> wrote:
> Awesome! Really.
>
> Thank you folks for doing this.
>
> I am so much looking forward to moving it to 1.0 with more built-in
> functions and more power to extend it...
>
> Note that Mistral has a few extensions, like `str`, `len`, which are not in
> the scope of evaluator.
>
> DZ>
>
>
> On Aug 2, 2015, at 12:44 PM, Stan Lagun <slagun at mirantis.com> wrote:
>
>
> Guys, this is awesome!!!
>
> Happy to see yaql gets attention. One more initiative that you may find
> interesting is https://review.openstack.org/#/c/159905/
> This is an attempt to port yaql 1.0 from Python to JS so that the same can
> be done in browser
>
> Sincerely yours,
> Stan Lagun
> Principal Software Engineer @ Mirantis
>
>
>
> On Sun, Aug 2, 2015 at 5:30 PM, Nikolay Makhotkin <nmakhotkin at mirantis.com>
> wrote:
> Hi guys!
>
> That's awesome! It is very useful for all us!
>
> --
> Best Regards,
> Nikolay
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



More information about the OpenStack-dev mailing list