[jira] [Updated] (IGNITE-2602) Queries: offset does not work with negative or MAX_VALUE limit

2017-08-22 Thread Vladimir Ozerov (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-2602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-2602:

Fix Version/s: (was: 2.2)

> Queries: offset does not work with negative or MAX_VALUE limit
> --
>
> Key: IGNITE-2602
> URL: https://issues.apache.org/jira/browse/IGNITE-2602
> Project: Ignite
>  Issue Type: Bug
>  Components: cache, sql
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>
> H2 allows specifying negative LIMIT with OFFSET: 
> http://www.h2database.com/html/grammar.html
> This does not work with Ignite (query returns empty result set).
> To work around this, I tried to specify Integer.MAX_VALUE, but this causes an 
> exception.
> Turns out, offset+limit should be <= Integer.MAX_VALUE, which is quite 
> inconvenient.
> I think we should support negative LIMIT for unlimited offset queries.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (IGNITE-2602) Queries: offset does not work with negative or MAX_VALUE limit

2017-05-10 Thread Vladimir Ozerov (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-2602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-2602:

Fix Version/s: (was: 2.1)
   2.2

> Queries: offset does not work with negative or MAX_VALUE limit
> --
>
> Key: IGNITE-2602
> URL: https://issues.apache.org/jira/browse/IGNITE-2602
> Project: Ignite
>  Issue Type: Bug
>  Components: cache, sql
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
> Fix For: 2.2
>
>
> H2 allows specifying negative LIMIT with OFFSET: 
> http://www.h2database.com/html/grammar.html
> This does not work with Ignite (query returns empty result set).
> To work around this, I tried to specify Integer.MAX_VALUE, but this causes an 
> exception.
> Turns out, offset+limit should be <= Integer.MAX_VALUE, which is quite 
> inconvenient.
> I think we should support negative LIMIT for unlimited offset queries.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (IGNITE-2602) Queries: offset does not work with negative or MAX_VALUE limit

2017-04-06 Thread Pavel Tupitsyn (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-2602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Tupitsyn updated IGNITE-2602:
---
Fix Version/s: (was: 2.0)
   2.1

> Queries: offset does not work with negative or MAX_VALUE limit
> --
>
> Key: IGNITE-2602
> URL: https://issues.apache.org/jira/browse/IGNITE-2602
> Project: Ignite
>  Issue Type: Bug
>  Components: cache, SQL
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
> Fix For: 2.1
>
>
> H2 allows specifying negative LIMIT with OFFSET: 
> http://www.h2database.com/html/grammar.html
> This does not work with Ignite (query returns empty result set).
> To work around this, I tried to specify Integer.MAX_VALUE, but this causes an 
> exception.
> Turns out, offset+limit should be <= Integer.MAX_VALUE, which is quite 
> inconvenient.
> I think we should support negative LIMIT for unlimited offset queries.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (IGNITE-2602) Queries: offset does not work with negative or MAX_VALUE limit

2016-11-06 Thread Vladimir Ozerov (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-2602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-2602:

Fix Version/s: (was: 1.8)
   2.0

> Queries: offset does not work with negative or MAX_VALUE limit
> --
>
> Key: IGNITE-2602
> URL: https://issues.apache.org/jira/browse/IGNITE-2602
> Project: Ignite
>  Issue Type: Bug
>  Components: cache, SQL
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
> Fix For: 2.0
>
>
> H2 allows specifying negative LIMIT with OFFSET: 
> http://www.h2database.com/html/grammar.html
> This does not work with Ignite (query returns empty result set).
> To work around this, I tried to specify Integer.MAX_VALUE, but this causes an 
> exception.
> Turns out, offset+limit should be <= Integer.MAX_VALUE, which is quite 
> inconvenient.
> I think we should support negative LIMIT for unlimited offset queries.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (IGNITE-2602) Queries: offset does not work with negative or MAX_VALUE limit

2016-11-06 Thread Vladimir Ozerov (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-2602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-2602:

Component/s: SQL

> Queries: offset does not work with negative or MAX_VALUE limit
> --
>
> Key: IGNITE-2602
> URL: https://issues.apache.org/jira/browse/IGNITE-2602
> Project: Ignite
>  Issue Type: Bug
>  Components: cache, SQL
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
> Fix For: 2.0
>
>
> H2 allows specifying negative LIMIT with OFFSET: 
> http://www.h2database.com/html/grammar.html
> This does not work with Ignite (query returns empty result set).
> To work around this, I tried to specify Integer.MAX_VALUE, but this causes an 
> exception.
> Turns out, offset+limit should be <= Integer.MAX_VALUE, which is quite 
> inconvenient.
> I think we should support negative LIMIT for unlimited offset queries.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (IGNITE-2602) Queries: offset does not work with negative or MAX_VALUE limit

2016-08-09 Thread Pavel Tupitsyn (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-2602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Tupitsyn updated IGNITE-2602:
---
Fix Version/s: (was: 1.7)
   1.8

> Queries: offset does not work with negative or MAX_VALUE limit
> --
>
> Key: IGNITE-2602
> URL: https://issues.apache.org/jira/browse/IGNITE-2602
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
> Fix For: 1.8
>
>
> H2 allows specifying negative LIMIT with OFFSET: 
> http://www.h2database.com/html/grammar.html
> This does not work with Ignite (query returns empty result set).
> To work around this, I tried to specify Integer.MAX_VALUE, but this causes an 
> exception.
> Turns out, offset+limit should be <= Integer.MAX_VALUE, which is quite 
> inconvenient.
> I think we should support negative LIMIT for unlimited offset queries.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (IGNITE-2602) Queries: offset does not work with negative or MAX_VALUE limit

2016-04-28 Thread Vladimir Ozerov (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-2602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-2602:

Fix Version/s: (was: 1.6)
   1.7

> Queries: offset does not work with negative or MAX_VALUE limit
> --
>
> Key: IGNITE-2602
> URL: https://issues.apache.org/jira/browse/IGNITE-2602
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
> Fix For: 1.7
>
>
> H2 allows specifying negative LIMIT with OFFSET: 
> http://www.h2database.com/html/grammar.html
> This does not work with Ignite (query returns empty result set).
> To work around this, I tried to specify Integer.MAX_VALUE, but this causes an 
> exception.
> Turns out, offset+limit should be <= Integer.MAX_VALUE, which is quite 
> inconvenient.
> I think we should support negative LIMIT for unlimited offset queries.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)