[ 
https://issues.apache.org/jira/browse/IGNITE-7712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16407702#comment-16407702
 ] 

ASF GitHub Bot commented on IGNITE-7712:
----------------------------------------

GitHub user alamar opened a pull request:

    https://github.com/apache/ignite/pull/3666

    IGNITE-7712 Add flag IGNITE_SQL_LAZY_RESULT_SET for setting default

    …value of SqlFieldsQuery.lazy

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gridgain/apache-ignite ignite-7712

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/3666.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #3666
    
----
commit 1c6af228b122ebc3f8bac51266aa808c2dacf23b
Author: Ilya Kasnacheev <ilya.kasnacheev@...>
Date:   2018-03-21T09:57:31Z

    IGNITE-7712 Add flag IGNITE_SQL_LAZY_RESULT_SET for setting default value 
of SqlFieldsQuery.lazy

----


> Add an ability to globally enable 'lazy' flag for SQL queries
> -------------------------------------------------------------
>
>                 Key: IGNITE-7712
>                 URL: https://issues.apache.org/jira/browse/IGNITE-7712
>             Project: Ignite
>          Issue Type: Improvement
>          Components: sql
>    Affects Versions: 2.3
>            Reporter: Valentin Kulichenko
>            Assignee: Ilya Kasnacheev
>            Priority: Major
>             Fix For: 2.5
>
>
> We have the {{lazy}} flag that can be set when a particular query is 
> executed, it's disabled by default.
> In some cases it can be useful to enable this flag globally, especially it 
> makes sense for the tools like Visor and Web Console.
> Let's do the following:
>  * Set it to {{true}} by default in Web Console.
>  * Add a system property that will allow to do the same on node level.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to