[jira] [Created] (IGNITE-3590) Create test and first simple implementation of secondary file system.
Dmitry Karachentsev created IGNITE-3590: --- Summary: Create test and first simple implementation of secondary file system. Key: IGNITE-3590 URL: https://issues.apache.org/jira/browse/IGNITE-3590 Project: Ignite Issue Type: Sub-task Components: IGFS Affects Versions: 1.6 Reporter: Dmitry Karachentsev Assignee: Dmitry Karachentsev Fix For: 1.7 Create new simple (copy paste from IgniteHadoopIgfsSecondaryFileSystem) inplementation and tests for it as start point. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3406) Interceptor and continuous query can get incorrect old value during rebalancing
[
https://issues.apache.org/jira/browse/IGNITE-3406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15395170#comment-15395170
]
Dmitry Karachentsev commented on IGNITE-3406:
-
Able to reproduce only first case, only for interceptor, and only for
TRANSACTIONAL cache. Fix requires deeper investigation of how tx cache works.
> Interceptor and continuous query can get incorrect old value during
> rebalancing
> ---
>
> Key: IGNITE-3406
> URL: https://issues.apache.org/jira/browse/IGNITE-3406
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.6
>Reporter: Valentin Kulichenko
>Assignee: Dmitry Karachentsev
> Fix For: 1.7
>
>
> During the rebalancing the old value passed to interceptor or continuous
> query can't be wrong due to scenarios described below.
> Scenario 1.
> # New node joins.
> # Update request arrives to the new node before the entry for the same key is
> rebalanced to this node.
> # Listeners are notified with {{null}} old value.
> In this case we should use {{GridDhtForceKeysRequest}} to get the old value.
> Scenario 2.
> # Entry is updated on primary node.
> # New backup node joins and the entry with already updated value is
> rebalanced from the primary node.
> # Update request arrives to this new backup node.
> # Listeners are notified with the old value which is the same as new value.
> In this case we should send the old value with the update request in case
> there is ongoing rebalancing and cache has interceptor configured or
> continuous queries registered.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-1926) Implement IgfsSecondaryFileSystem using java.io.File API
[ https://issues.apache.org/jira/browse/IGNITE-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Karachentsev reassigned IGNITE-1926: --- Assignee: Dmitry Karachentsev > Implement IgfsSecondaryFileSystem using java.io.File API > > > Key: IGNITE-1926 > URL: https://issues.apache.org/jira/browse/IGNITE-1926 > Project: Ignite > Issue Type: Improvement > Components: IGFS >Affects Versions: 1.6 >Reporter: Valentin Kulichenko >Assignee: Dmitry Karachentsev > Labels: roadmap > Fix For: 1.7 > > > This will allow to persist IGFS data on the local disk. Currently we have > only Hadoop-based implementation. > Corresponding user thread: > http://apache-ignite-users.70518.x6.nabble.com/IGFS-backed-by-persistence-on-physical-filesystem-td1882.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-3323) Get rid of copypasted JB annotations, use dependency instead.
[
https://issues.apache.org/jira/browse/IGNITE-3323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov resolved IGNITE-3323.
--
> Get rid of copypasted JB annotations, use dependency instead.
> -
>
> Key: IGNITE-3323
> URL: https://issues.apache.org/jira/browse/IGNITE-3323
> Project: Ignite
> Issue Type: Task
>Affects Versions: 1.5.0.final
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>Priority: Minor
> Labels: newbie
> Fix For: 1.7
>
>
> From user request:
> {quote}
> I've come across an issue where there are a couple of classes duplicated from
> org.jetbrains.annotations within the ignite-core module which conflict with
> other part of our code base.
> As these files are duplicated rather than being referenced as a maven
> dependency I am unable to exclude them or reference a specific version of the
> org.jetbrains.annotations artifact.
> Specifically, the included version cannot be used to annotate types
> ignite-core-1.6.0.jar:org.jetbrains.annotations.Nullable ...
> @Target({ElementType.METHOD, ElementType.FIELD, ElementType.PARAMETER,
> ElementType.LOCAL_VARIABLE})
> annotations-15.0.jar:org.jetbrains.annotations.Nullable ...
> @Target({ElementType.METHOD, ElementType.FIELD, ElementType.PARAMETER,
> ElementType.LOCAL_VARIABLE, ElementType.TYPE_USE})
> As far as I know there isn't an easy way of excluding these files from within
> the ignite-core module. Is there are reason why these "external" files have
> been duplicated within the ignite code base rather than being referenced as a
> maven dependency? Or alternatively, has anyone come across a way of avoiding
> these conflicts?
> {quote}
> Seems we have to remove these classes from Ignite code and use maven
> dependency.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-3323) Get rid of copypasted JB annotations, use dependency instead.
[
https://issues.apache.org/jira/browse/IGNITE-3323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15395204#comment-15395204
]
Anton Vinogradov commented on IGNITE-3323:
--
Fixed, thanks for tip.
> Get rid of copypasted JB annotations, use dependency instead.
> -
>
> Key: IGNITE-3323
> URL: https://issues.apache.org/jira/browse/IGNITE-3323
> Project: Ignite
> Issue Type: Task
>Affects Versions: 1.5.0.final
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>Priority: Minor
> Labels: newbie
> Fix For: 1.7
>
>
> From user request:
> {quote}
> I've come across an issue where there are a couple of classes duplicated from
> org.jetbrains.annotations within the ignite-core module which conflict with
> other part of our code base.
> As these files are duplicated rather than being referenced as a maven
> dependency I am unable to exclude them or reference a specific version of the
> org.jetbrains.annotations artifact.
> Specifically, the included version cannot be used to annotate types
> ignite-core-1.6.0.jar:org.jetbrains.annotations.Nullable ...
> @Target({ElementType.METHOD, ElementType.FIELD, ElementType.PARAMETER,
> ElementType.LOCAL_VARIABLE})
> annotations-15.0.jar:org.jetbrains.annotations.Nullable ...
> @Target({ElementType.METHOD, ElementType.FIELD, ElementType.PARAMETER,
> ElementType.LOCAL_VARIABLE, ElementType.TYPE_USE})
> As far as I know there isn't an easy way of excluding these files from within
> the ignite-core module. Is there are reason why these "external" files have
> been duplicated within the ignite code base rather than being referenced as a
> maven dependency? Or alternatively, has anyone come across a way of avoiding
> these conflicts?
> {quote}
> Seems we have to remove these classes from Ignite code and use maven
> dependency.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (IGNITE-3323) Get rid of copypasted JB annotations, use dependency instead.
[
https://issues.apache.org/jira/browse/IGNITE-3323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov closed IGNITE-3323.
Assignee: Jens Hoffmann (was: Anton Vinogradov)
> Get rid of copypasted JB annotations, use dependency instead.
> -
>
> Key: IGNITE-3323
> URL: https://issues.apache.org/jira/browse/IGNITE-3323
> Project: Ignite
> Issue Type: Task
>Affects Versions: 1.5.0.final
>Reporter: Anton Vinogradov
>Assignee: Jens Hoffmann
>Priority: Minor
> Labels: newbie
> Fix For: 1.7
>
>
> From user request:
> {quote}
> I've come across an issue where there are a couple of classes duplicated from
> org.jetbrains.annotations within the ignite-core module which conflict with
> other part of our code base.
> As these files are duplicated rather than being referenced as a maven
> dependency I am unable to exclude them or reference a specific version of the
> org.jetbrains.annotations artifact.
> Specifically, the included version cannot be used to annotate types
> ignite-core-1.6.0.jar:org.jetbrains.annotations.Nullable ...
> @Target({ElementType.METHOD, ElementType.FIELD, ElementType.PARAMETER,
> ElementType.LOCAL_VARIABLE})
> annotations-15.0.jar:org.jetbrains.annotations.Nullable ...
> @Target({ElementType.METHOD, ElementType.FIELD, ElementType.PARAMETER,
> ElementType.LOCAL_VARIABLE, ElementType.TYPE_USE})
> As far as I know there isn't an easy way of excluding these files from within
> the ignite-core module. Is there are reason why these "external" files have
> been duplicated within the ignite code base rather than being referenced as a
> maven dependency? Or alternatively, has anyone come across a way of avoiding
> these conflicts?
> {quote}
> Seems we have to remove these classes from Ignite code and use maven
> dependency.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-3591) .NET: Self-joins do not work in LINQ
Pavel Tupitsyn created IGNITE-3591: -- Summary: .NET: Self-joins do not work in LINQ Key: IGNITE-3591 URL: https://issues.apache.org/jira/browse/IGNITE-3591 Project: Ignite Issue Type: Bug Components: platforms Affects Versions: 1.6 Reporter: Pavel Tupitsyn Assignee: Pavel Tupitsyn Fix For: 1.7 When joining the table on itself, the same table alias is used, leading to ambiguous column name error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3561) .NET: DistributedJoins property in SqlQuery & SqlFieldsQuery
[ https://issues.apache.org/jira/browse/IGNITE-3561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15395241#comment-15395241 ] ASF GitHub Bot commented on IGNITE-3561: GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/900 IGNITE-3561 .NET: DistributedJoins property in SqlQuery & SqlFieldsQuery - improve API and tests You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-3561-1 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/900.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 #900 > .NET: DistributedJoins property in SqlQuery & SqlFieldsQuery > > > Key: IGNITE-3561 > URL: https://issues.apache.org/jira/browse/IGNITE-3561 > Project: Ignite > Issue Type: Improvement > Components: platforms >Affects Versions: 1.7 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Labels: .net > Fix For: 1.7 > > > IGNITE-1232 added new properties to SqlQuery and SqlFieldsQuery classes. > Propagate them to .NET. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3323) Get rid of copypasted JB annotations, use dependency instead.
[
https://issues.apache.org/jira/browse/IGNITE-3323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15395245#comment-15395245
]
ASF GitHub Bot commented on IGNITE-3323:
Github user jayho closed the pull request at:
https://github.com/apache/ignite/pull/895
> Get rid of copypasted JB annotations, use dependency instead.
> -
>
> Key: IGNITE-3323
> URL: https://issues.apache.org/jira/browse/IGNITE-3323
> Project: Ignite
> Issue Type: Task
>Affects Versions: 1.5.0.final
>Reporter: Anton Vinogradov
>Assignee: Jens Hoffmann
>Priority: Minor
> Labels: newbie
> Fix For: 1.7
>
>
> From user request:
> {quote}
> I've come across an issue where there are a couple of classes duplicated from
> org.jetbrains.annotations within the ignite-core module which conflict with
> other part of our code base.
> As these files are duplicated rather than being referenced as a maven
> dependency I am unable to exclude them or reference a specific version of the
> org.jetbrains.annotations artifact.
> Specifically, the included version cannot be used to annotate types
> ignite-core-1.6.0.jar:org.jetbrains.annotations.Nullable ...
> @Target({ElementType.METHOD, ElementType.FIELD, ElementType.PARAMETER,
> ElementType.LOCAL_VARIABLE})
> annotations-15.0.jar:org.jetbrains.annotations.Nullable ...
> @Target({ElementType.METHOD, ElementType.FIELD, ElementType.PARAMETER,
> ElementType.LOCAL_VARIABLE, ElementType.TYPE_USE})
> As far as I know there isn't an easy way of excluding these files from within
> the ignite-core module. Is there are reason why these "external" files have
> been duplicated within the ignite code base rather than being referenced as a
> maven dependency? Or alternatively, has anyone come across a way of avoiding
> these conflicts?
> {quote}
> Seems we have to remove these classes from Ignite code and use maven
> dependency.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (IGNITE-2611) add ability to remove notebook from SQL menu directly
[ https://issues.apache.org/jira/browse/IGNITE-2611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov closed IGNITE-2611. -- Assignee: (was: Pavel Konstantinov) Successfully tested on staging > add ability to remove notebook from SQL menu directly > - > > Key: IGNITE-2611 > URL: https://issues.apache.org/jira/browse/IGNITE-2611 > Project: Ignite > Issue Type: Sub-task >Reporter: Pavel Konstantinov > Fix For: 1.7 > > > Currently user should open notebook and only then he has ability to remove > this notebook. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3513) Cleanup worker is placed in the Thread's waiting queue using Thread.sleep method
[
https://issues.apache.org/jira/browse/IGNITE-3513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15395278#comment-15395278
]
Eduard Shangareev commented on IGNITE-3513:
---
Night benchmark run.
Result for *1* ExpriryPolicy:
|Thread|Sleep|Wait|Park|
|2|161.508 ± 1.308|170.009 ± 2.791|163.672 ± 2.856|
|4|263.062 ± 3.680|274.452 ± 3.191|263.886 ± 5.375|
|8|328.178 ± 4.100|378.947 ± 24.256|327.398 ± 8.166|
|16|331.939 ± 3.376|367.014 ± 6.759|324.264 ± 30.517|
|32|340.865 ± 3.612|370.433 ± 2.863|341.507 ± 4.826|
Result for *2* ExpriryPolicy:
|Thread|Sleep|Wait|Park|
|2|167.343 ± 2.423|148.122 ± 2.108|141.759 ± 4.842|
|4|260.494 ± 2.344|251.488 ± 5.418|221.650 ± 1.996|
|8|333.675 ± 3.024|325.235 ± 3.193|330.027 ± 3.249|
|16|336.898 ± 4.852|344.233 ± 4.319|335.587 ± 3.450|
|32|346.102 ± 3.045|351.342 ± 3.727|339.795 ± 4.816|
Result for *3* ExpriryPolicy:
|Thread|Sleep|Wait|Park|
|2|163.042 ± 3.640|155.299 ± 1.977|150.011 ± 3.164|
|4|257.366 ± 3.600|256.394 ± 2.352|227.143 ± 2.704|
|8|330.468 ± 4.112|329.907 ± 24.981|318.291 ± 4.997|
|16|326.528 ± 3.263|345.385 ± 2.834|326.629 ± 3.275|
|32|336.828 ± 4.916|352.499 ± 3.689|331.759 ± 6.301|
Result for *4* ExpriryPolicy:
|Thread|Sleep|Wait|Park|
|2|165.767 ± 3.107|152.139 ± 1.882|142.256 ± 2.534|
|4|263.421 ± 3.162|249.717 ± 4.320|220.386 ± 3.418|
|8|332.505 ± 2.498|330.995 ± 4.075|319.970 ± 3.628|
|16|331.850 ± 3.934|342.258 ± 2.591|328.169 ± 3.960|
|32|342.669 ± 3.990|351.790 ± 3.482|335.425 ± 2.636|
Result for *5* ExpriryPolicy:
|Thread|Sleep|Wait|Park|
|2|161.109 ± 3.544|144.023 ± 1.787|140.389 ± 3.822|
|4|262.874 ± 4.848|252.311 ± 5.104|216.460 ± 3.625|
|8|335.351 ± 4.769|325.620 ± 3.335|326.554 ± 3.145|
|16|337.047 ± 3.524|342.082 ± 2.526|327.885 ± 13.494|
|32|337.168 ± 3.587|354.922 ± 4.035|336.269 ± 3.266|
> Cleanup worker is placed in the Thread's waiting queue using Thread.sleep
> method
>
>
> Key: IGNITE-3513
> URL: https://issues.apache.org/jira/browse/IGNITE-3513
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.6
>Reporter: Denis Magda
>Assignee: Eduard Shangareev
> Fix For: 1.7
>
>
> There is a bug in current implementation of
> {{GridCacheTtlManager#CleanupWorker}}.
> Refer to the implementation's code snippet and the details below.
> {code}
> EntryWrapper first = pendingEntries.firstx();
> if (first != null) {
>long waitTime = first.expireTime - U.currentTimeMillis();
>if (waitTime > 0)
> U.sleep(waitTime);
> }
> {code}
> 1. Put first item with TTL = 1 hour. CleanupWorker will go to sleep for 1
> hour.
> 2. Put second item with TTL = 1 minute. Since
> CleanupWorker's thread sleeps now, second item will not be expired at the
> time.
> NOTE: This scenario is easily to reproducible if first and second items are
> put into cache asynchronously. If try to put them in same thread one-by-one
> expiration may work fine.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-3513) Cleanup worker is placed in the Thread's waiting queue using Thread.sleep method
[
https://issues.apache.org/jira/browse/IGNITE-3513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15395278#comment-15395278
]
Eduard Shangareev edited comment on IGNITE-3513 at 7/27/16 9:05 AM:
Night benchmark run (sleep duration - 10ms).
Result for *1* ExpriryPolicy:
|Thread|Sleep|Wait|Park|
|2|161.508 ± 1.308|170.009 ± 2.791|163.672 ± 2.856|
|4|263.062 ± 3.680|274.452 ± 3.191|263.886 ± 5.375|
|8|328.178 ± 4.100|378.947 ± 24.256|327.398 ± 8.166|
|16|331.939 ± 3.376|367.014 ± 6.759|324.264 ± 30.517|
|32|340.865 ± 3.612|370.433 ± 2.863|341.507 ± 4.826|
Result for *2* ExpriryPolicy:
|Thread|Sleep|Wait|Park|
|2|167.343 ± 2.423|148.122 ± 2.108|141.759 ± 4.842|
|4|260.494 ± 2.344|251.488 ± 5.418|221.650 ± 1.996|
|8|333.675 ± 3.024|325.235 ± 3.193|330.027 ± 3.249|
|16|336.898 ± 4.852|344.233 ± 4.319|335.587 ± 3.450|
|32|346.102 ± 3.045|351.342 ± 3.727|339.795 ± 4.816|
Result for *3* ExpriryPolicy:
|Thread|Sleep|Wait|Park|
|2|163.042 ± 3.640|155.299 ± 1.977|150.011 ± 3.164|
|4|257.366 ± 3.600|256.394 ± 2.352|227.143 ± 2.704|
|8|330.468 ± 4.112|329.907 ± 24.981|318.291 ± 4.997|
|16|326.528 ± 3.263|345.385 ± 2.834|326.629 ± 3.275|
|32|336.828 ± 4.916|352.499 ± 3.689|331.759 ± 6.301|
Result for *4* ExpriryPolicy:
|Thread|Sleep|Wait|Park|
|2|165.767 ± 3.107|152.139 ± 1.882|142.256 ± 2.534|
|4|263.421 ± 3.162|249.717 ± 4.320|220.386 ± 3.418|
|8|332.505 ± 2.498|330.995 ± 4.075|319.970 ± 3.628|
|16|331.850 ± 3.934|342.258 ± 2.591|328.169 ± 3.960|
|32|342.669 ± 3.990|351.790 ± 3.482|335.425 ± 2.636|
Result for *5* ExpriryPolicy:
|Thread|Sleep|Wait|Park|
|2|161.109 ± 3.544|144.023 ± 1.787|140.389 ± 3.822|
|4|262.874 ± 4.848|252.311 ± 5.104|216.460 ± 3.625|
|8|335.351 ± 4.769|325.620 ± 3.335|326.554 ± 3.145|
|16|337.047 ± 3.524|342.082 ± 2.526|327.885 ± 13.494|
|32|337.168 ± 3.587|354.922 ± 4.035|336.269 ± 3.266|
was (Author: edshanggg):
Night benchmark run.
Result for *1* ExpriryPolicy:
|Thread|Sleep|Wait|Park|
|2|161.508 ± 1.308|170.009 ± 2.791|163.672 ± 2.856|
|4|263.062 ± 3.680|274.452 ± 3.191|263.886 ± 5.375|
|8|328.178 ± 4.100|378.947 ± 24.256|327.398 ± 8.166|
|16|331.939 ± 3.376|367.014 ± 6.759|324.264 ± 30.517|
|32|340.865 ± 3.612|370.433 ± 2.863|341.507 ± 4.826|
Result for *2* ExpriryPolicy:
|Thread|Sleep|Wait|Park|
|2|167.343 ± 2.423|148.122 ± 2.108|141.759 ± 4.842|
|4|260.494 ± 2.344|251.488 ± 5.418|221.650 ± 1.996|
|8|333.675 ± 3.024|325.235 ± 3.193|330.027 ± 3.249|
|16|336.898 ± 4.852|344.233 ± 4.319|335.587 ± 3.450|
|32|346.102 ± 3.045|351.342 ± 3.727|339.795 ± 4.816|
Result for *3* ExpriryPolicy:
|Thread|Sleep|Wait|Park|
|2|163.042 ± 3.640|155.299 ± 1.977|150.011 ± 3.164|
|4|257.366 ± 3.600|256.394 ± 2.352|227.143 ± 2.704|
|8|330.468 ± 4.112|329.907 ± 24.981|318.291 ± 4.997|
|16|326.528 ± 3.263|345.385 ± 2.834|326.629 ± 3.275|
|32|336.828 ± 4.916|352.499 ± 3.689|331.759 ± 6.301|
Result for *4* ExpriryPolicy:
|Thread|Sleep|Wait|Park|
|2|165.767 ± 3.107|152.139 ± 1.882|142.256 ± 2.534|
|4|263.421 ± 3.162|249.717 ± 4.320|220.386 ± 3.418|
|8|332.505 ± 2.498|330.995 ± 4.075|319.970 ± 3.628|
|16|331.850 ± 3.934|342.258 ± 2.591|328.169 ± 3.960|
|32|342.669 ± 3.990|351.790 ± 3.482|335.425 ± 2.636|
Result for *5* ExpriryPolicy:
|Thread|Sleep|Wait|Park|
|2|161.109 ± 3.544|144.023 ± 1.787|140.389 ± 3.822|
|4|262.874 ± 4.848|252.311 ± 5.104|216.460 ± 3.625|
|8|335.351 ± 4.769|325.620 ± 3.335|326.554 ± 3.145|
|16|337.047 ± 3.524|342.082 ± 2.526|327.885 ± 13.494|
|32|337.168 ± 3.587|354.922 ± 4.035|336.269 ± 3.266|
> Cleanup worker is placed in the Thread's waiting queue using Thread.sleep
> method
>
>
> Key: IGNITE-3513
> URL: https://issues.apache.org/jira/browse/IGNITE-3513
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.6
>Reporter: Denis Magda
>Assignee: Eduard Shangareev
> Fix For: 1.7
>
>
> There is a bug in current implementation of
> {{GridCacheTtlManager#CleanupWorker}}.
> Refer to the implementation's code snippet and the details below.
> {code}
> EntryWrapper first = pendingEntries.firstx();
> if (first != null) {
>long waitTime = first.expireTime - U.currentTimeMillis();
>if (waitTime > 0)
> U.sleep(waitTime);
> }
> {code}
> 1. Put first item with TTL = 1 hour. CleanupWorker will go to sleep for 1
> hour.
> 2. Put second item with TTL = 1 minute. Since
> CleanupWorker's thread sleeps now, second item will not be expired at the
> time.
> NOTE: This scenario is easily to reproducible if first and second items are
> put into cache asynchronously. If try to put them in same thread one-by-one
> expiration may work fine.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-3513) Cleanup worker is placed in the Thread's waiting queue using Thread.sleep method
[
https://issues.apache.org/jira/browse/IGNITE-3513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15395278#comment-15395278
]
Eduard Shangareev edited comment on IGNITE-3513 at 7/27/16 9:05 AM:
Night benchmark run (sleep duration - 10ms, numbers - ops/ms).
Result for *1* ExpriryPolicy:
|Thread|Sleep|Wait|Park|
|2|161.508 ± 1.308|170.009 ± 2.791|163.672 ± 2.856|
|4|263.062 ± 3.680|274.452 ± 3.191|263.886 ± 5.375|
|8|328.178 ± 4.100|378.947 ± 24.256|327.398 ± 8.166|
|16|331.939 ± 3.376|367.014 ± 6.759|324.264 ± 30.517|
|32|340.865 ± 3.612|370.433 ± 2.863|341.507 ± 4.826|
Result for *2* ExpriryPolicy:
|Thread|Sleep|Wait|Park|
|2|167.343 ± 2.423|148.122 ± 2.108|141.759 ± 4.842|
|4|260.494 ± 2.344|251.488 ± 5.418|221.650 ± 1.996|
|8|333.675 ± 3.024|325.235 ± 3.193|330.027 ± 3.249|
|16|336.898 ± 4.852|344.233 ± 4.319|335.587 ± 3.450|
|32|346.102 ± 3.045|351.342 ± 3.727|339.795 ± 4.816|
Result for *3* ExpriryPolicy:
|Thread|Sleep|Wait|Park|
|2|163.042 ± 3.640|155.299 ± 1.977|150.011 ± 3.164|
|4|257.366 ± 3.600|256.394 ± 2.352|227.143 ± 2.704|
|8|330.468 ± 4.112|329.907 ± 24.981|318.291 ± 4.997|
|16|326.528 ± 3.263|345.385 ± 2.834|326.629 ± 3.275|
|32|336.828 ± 4.916|352.499 ± 3.689|331.759 ± 6.301|
Result for *4* ExpriryPolicy:
|Thread|Sleep|Wait|Park|
|2|165.767 ± 3.107|152.139 ± 1.882|142.256 ± 2.534|
|4|263.421 ± 3.162|249.717 ± 4.320|220.386 ± 3.418|
|8|332.505 ± 2.498|330.995 ± 4.075|319.970 ± 3.628|
|16|331.850 ± 3.934|342.258 ± 2.591|328.169 ± 3.960|
|32|342.669 ± 3.990|351.790 ± 3.482|335.425 ± 2.636|
Result for *5* ExpriryPolicy:
|Thread|Sleep|Wait|Park|
|2|161.109 ± 3.544|144.023 ± 1.787|140.389 ± 3.822|
|4|262.874 ± 4.848|252.311 ± 5.104|216.460 ± 3.625|
|8|335.351 ± 4.769|325.620 ± 3.335|326.554 ± 3.145|
|16|337.047 ± 3.524|342.082 ± 2.526|327.885 ± 13.494|
|32|337.168 ± 3.587|354.922 ± 4.035|336.269 ± 3.266|
was (Author: edshanggg):
Night benchmark run (sleep duration - 10ms).
Result for *1* ExpriryPolicy:
|Thread|Sleep|Wait|Park|
|2|161.508 ± 1.308|170.009 ± 2.791|163.672 ± 2.856|
|4|263.062 ± 3.680|274.452 ± 3.191|263.886 ± 5.375|
|8|328.178 ± 4.100|378.947 ± 24.256|327.398 ± 8.166|
|16|331.939 ± 3.376|367.014 ± 6.759|324.264 ± 30.517|
|32|340.865 ± 3.612|370.433 ± 2.863|341.507 ± 4.826|
Result for *2* ExpriryPolicy:
|Thread|Sleep|Wait|Park|
|2|167.343 ± 2.423|148.122 ± 2.108|141.759 ± 4.842|
|4|260.494 ± 2.344|251.488 ± 5.418|221.650 ± 1.996|
|8|333.675 ± 3.024|325.235 ± 3.193|330.027 ± 3.249|
|16|336.898 ± 4.852|344.233 ± 4.319|335.587 ± 3.450|
|32|346.102 ± 3.045|351.342 ± 3.727|339.795 ± 4.816|
Result for *3* ExpriryPolicy:
|Thread|Sleep|Wait|Park|
|2|163.042 ± 3.640|155.299 ± 1.977|150.011 ± 3.164|
|4|257.366 ± 3.600|256.394 ± 2.352|227.143 ± 2.704|
|8|330.468 ± 4.112|329.907 ± 24.981|318.291 ± 4.997|
|16|326.528 ± 3.263|345.385 ± 2.834|326.629 ± 3.275|
|32|336.828 ± 4.916|352.499 ± 3.689|331.759 ± 6.301|
Result for *4* ExpriryPolicy:
|Thread|Sleep|Wait|Park|
|2|165.767 ± 3.107|152.139 ± 1.882|142.256 ± 2.534|
|4|263.421 ± 3.162|249.717 ± 4.320|220.386 ± 3.418|
|8|332.505 ± 2.498|330.995 ± 4.075|319.970 ± 3.628|
|16|331.850 ± 3.934|342.258 ± 2.591|328.169 ± 3.960|
|32|342.669 ± 3.990|351.790 ± 3.482|335.425 ± 2.636|
Result for *5* ExpriryPolicy:
|Thread|Sleep|Wait|Park|
|2|161.109 ± 3.544|144.023 ± 1.787|140.389 ± 3.822|
|4|262.874 ± 4.848|252.311 ± 5.104|216.460 ± 3.625|
|8|335.351 ± 4.769|325.620 ± 3.335|326.554 ± 3.145|
|16|337.047 ± 3.524|342.082 ± 2.526|327.885 ± 13.494|
|32|337.168 ± 3.587|354.922 ± 4.035|336.269 ± 3.266|
> Cleanup worker is placed in the Thread's waiting queue using Thread.sleep
> method
>
>
> Key: IGNITE-3513
> URL: https://issues.apache.org/jira/browse/IGNITE-3513
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.6
>Reporter: Denis Magda
>Assignee: Eduard Shangareev
> Fix For: 1.7
>
>
> There is a bug in current implementation of
> {{GridCacheTtlManager#CleanupWorker}}.
> Refer to the implementation's code snippet and the details below.
> {code}
> EntryWrapper first = pendingEntries.firstx();
> if (first != null) {
>long waitTime = first.expireTime - U.currentTimeMillis();
>if (waitTime > 0)
> U.sleep(waitTime);
> }
> {code}
> 1. Put first item with TTL = 1 hour. CleanupWorker will go to sleep for 1
> hour.
> 2. Put second item with TTL = 1 minute. Since
> CleanupWorker's thread sleeps now, second item will not be expired at the
> time.
> NOTE: This scenario is easily to reproducible if first and second items are
> put into cache asynchronously. If try to put them in same thread one-by-one
> expiration may work fine.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-3578) CPP: Add support of distributed joins in SqlQuery & SqlFieldsQuery
[
https://issues.apache.org/jira/browse/IGNITE-3578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15395395#comment-15395395
]
Igor Sapego commented on IGNITE-3578:
-
Vladimir,
I'll try to add such tests, but the problem is that with current C++ API I can
not be sure if the records are not collocated or if they (accidentally) are.
But I guess adding a lot of records should do the trick.
> CPP: Add support of distributed joins in SqlQuery & SqlFieldsQuery
> --
>
> Key: IGNITE-3578
> URL: https://issues.apache.org/jira/browse/IGNITE-3578
> Project: Ignite
> Issue Type: Task
> Components: platforms
>Affects Versions: 1.6
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Labels: cpp
> Fix For: 1.7
>
>
> IGNITE-1232 added new properties to {{SqlQuery}} and {{SqlFieldsQuery}}
> classes. Propagate them to C++.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (IGNITE-3561) .NET: DistributedJoins property in SqlQuery & SqlFieldsQuery
[ https://issues.apache.org/jira/browse/IGNITE-3561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov closed IGNITE-3561. --- > .NET: DistributedJoins property in SqlQuery & SqlFieldsQuery > > > Key: IGNITE-3561 > URL: https://issues.apache.org/jira/browse/IGNITE-3561 > Project: Ignite > Issue Type: Improvement > Components: platforms >Affects Versions: 1.7 >Reporter: Pavel Tupitsyn >Assignee: Vladimir Ozerov > Labels: .net > Fix For: 1.7 > > > IGNITE-1232 added new properties to SqlQuery and SqlFieldsQuery classes. > Propagate them to .NET. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3560) Unify type descriptor removal and destruction in IgniteH2Indexing
[ https://issues.apache.org/jira/browse/IGNITE-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15395433#comment-15395433 ] Krome Plasma commented on IGNITE-3560: -- Yes that is true, thanks. > Unify type descriptor removal and destruction in IgniteH2Indexing > - > > Key: IGNITE-3560 > URL: https://issues.apache.org/jira/browse/IGNITE-3560 > Project: Ignite > Issue Type: Bug >Reporter: Sergi Vladykin >Priority: Blocker > Fix For: 1.7 > > > Currently I see at least 3 places where we have to deal with table > destruction: > 1. unregisterCache() -> Schema.onDrop() > 2. unregisterType() -> removeTable() > 3. stop() > We need to refactor them to call the same logic which has to always do the > following steps: > 1. dataTables.remove() > 2. GridH2Table.destroy() > 3. U.closeQuiet(TableDescriptor.luceneIdx) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3561) .NET: DistributedJoins property in SqlQuery & SqlFieldsQuery
[ https://issues.apache.org/jira/browse/IGNITE-3561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15395442#comment-15395442 ] ASF GitHub Bot commented on IGNITE-3561: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/900 > .NET: DistributedJoins property in SqlQuery & SqlFieldsQuery > > > Key: IGNITE-3561 > URL: https://issues.apache.org/jira/browse/IGNITE-3561 > Project: Ignite > Issue Type: Improvement > Components: platforms >Affects Versions: 1.7 >Reporter: Pavel Tupitsyn >Assignee: Vladimir Ozerov > Labels: .net > Fix For: 1.7 > > > IGNITE-1232 added new properties to SqlQuery and SqlFieldsQuery classes. > Propagate them to .NET. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1084) [Test] HibernateL2CacheSelfTest#testNaturalIdCache() is broken
[ https://issues.apache.org/jira/browse/IGNITE-1084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15395459#comment-15395459 ] ASF GitHub Bot commented on IGNITE-1084: GitHub user mwadhwa opened a pull request: https://github.com/apache/ignite/pull/901 IGNITE-1084 fixed issue broken HibernateL2CacheSelfTest#testNaturalI… …dCache() You can merge this pull request into a Git repository by running: $ git pull https://github.com/mwadhwa/ignite master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/901.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 #901 commit 2a1be7d6925390081d8aa674b516381e4c5a0b42 Author: milap.wadhwa Date: 2016-07-27T11:11:55Z IGNITE-1084 fixed issue broken HibernateL2CacheSelfTest#testNaturalIdCache() > [Test] HibernateL2CacheSelfTest#testNaturalIdCache() is broken > -- > > Key: IGNITE-1084 > URL: https://issues.apache.org/jira/browse/IGNITE-1084 > Project: Ignite > Issue Type: Test > Components: cache >Reporter: Sergey Evdokimov >Assignee: Milap Wadhwa >Priority: Minor > Labels: Muted_test > > Test HibernateL2CacheSelfTest#testNaturalIdCache() should be unmuted and > fixed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-271) Fix GridMultithreadedJobStealingSelfTest.testTwoJobsMultithreaded test periodically fails
[ https://issues.apache.org/jira/browse/IGNITE-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Milap Wadhwa reassigned IGNITE-271: --- Assignee: Milap Wadhwa > Fix GridMultithreadedJobStealingSelfTest.testTwoJobsMultithreaded test > periodically fails > - > > Key: IGNITE-271 > URL: https://issues.apache.org/jira/browse/IGNITE-271 > Project: Ignite > Issue Type: Bug > Components: compute >Reporter: Nikolay Tikhonov >Assignee: Milap Wadhwa >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-3592) Provide some kind of pluggable compression SPI support
Alexey Kuznetsov created IGNITE-3592: Summary: Provide some kind of pluggable compression SPI support Key: IGNITE-3592 URL: https://issues.apache.org/jira/browse/IGNITE-3592 Project: Ignite Issue Type: Task Components: cache Reporter: Alexey Kuznetsov Fix For: 2.0 It may be useful in some cases to compress data stored in cache. And in order to give access to compressed data from SQL engine this support should be implemented in ignite-core level. See discussion on dev-list: http://apache-ignite-developers.2346864.n4.nabble.com/Data-compression-in-Ignite-2-0-td10099.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-3591) .NET: Self-joins do not work in LINQ
[ https://issues.apache.org/jira/browse/IGNITE-3591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn closed IGNITE-3591. -- > .NET: Self-joins do not work in LINQ > > > Key: IGNITE-3591 > URL: https://issues.apache.org/jira/browse/IGNITE-3591 > Project: Ignite > Issue Type: Bug > Components: platforms >Affects Versions: 1.6 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Labels: .net > Fix For: 1.7 > > > When joining the table on itself, the same table alias is used, leading to > ambiguous column name error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-3591) .NET: Self-joins do not work in LINQ
[ https://issues.apache.org/jira/browse/IGNITE-3591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn resolved IGNITE-3591. Resolution: Fixed > .NET: Self-joins do not work in LINQ > > > Key: IGNITE-3591 > URL: https://issues.apache.org/jira/browse/IGNITE-3591 > Project: Ignite > Issue Type: Bug > Components: platforms >Affects Versions: 1.6 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Labels: .net > Fix For: 1.7 > > > When joining the table on itself, the same table alias is used, leading to > ambiguous column name error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2112) Provide a way to serialize/deserialize an IgniteConfiguration object using JSON
[ https://issues.apache.org/jira/browse/IGNITE-2112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Milap Wadhwa updated IGNITE-2112: - Assignee: (was: Milap Wadhwa) > Provide a way to serialize/deserialize an IgniteConfiguration object using > JSON > --- > > Key: IGNITE-2112 > URL: https://issues.apache.org/jira/browse/IGNITE-2112 > Project: Ignite > Issue Type: Improvement > Components: general >Affects Versions: ignite-1.4 >Reporter: Juan Velez >Priority: Minor > > Currently as of Release 1.4, Ignite does not provide a way to > serialize/deserialize an IgniteConfiguration object using JSON. Attempts to > create a working serializer/deserializer are met with very difficult setup > and configuration because the IgniteConfiguration (and subcomponents) rely on > Factories, SPIs, etc for properties. as well as not being completely > compliant with the JavaBeans standard. > It would be great if the serialization/deserialization using JSON could be > provided as either a new method in an existing/new Util class or part of the > IgniteConfiguration class itself. > I understand that in the case of deserialization most likely there would be > constraints on how to correctly specify the JSON string but that would be > left for implementors of the feature to correctly decide/design/document. > See user@ thread > http://apache-ignite-users.70518.x6.nabble.com/How-to-serialize-deserialize-IgniteConfiguration-to-from-JSON-td2164.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-3593) .NET: IgniteConfiguration.WorkDirectory has no effect
Pavel Tupitsyn created IGNITE-3593: -- Summary: .NET: IgniteConfiguration.WorkDirectory has no effect Key: IGNITE-3593 URL: https://issues.apache.org/jira/browse/IGNITE-3593 Project: Ignite Issue Type: Bug Components: platforms Affects Versions: 1.6 Reporter: Pavel Tupitsyn Assignee: Pavel Tupitsyn Fix For: 1.7 Temporary marshaller is created during startup, it sets the work dir, and it can't be changed after that (static state). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3593) .NET: IgniteConfiguration.WorkDirectory has no effect
[ https://issues.apache.org/jira/browse/IGNITE-3593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15395886#comment-15395886 ] ASF GitHub Bot commented on IGNITE-3593: GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/903 IGNITE-3593 .NET: Fix IgniteConfiguration.WorkDirectory having no effect You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-3593 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/903.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 #903 > .NET: IgniteConfiguration.WorkDirectory has no effect > - > > Key: IGNITE-3593 > URL: https://issues.apache.org/jira/browse/IGNITE-3593 > Project: Ignite > Issue Type: Bug > Components: platforms >Affects Versions: 1.6 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Fix For: 1.7 > > > Temporary marshaller is created during startup, it sets the work dir, and it > can't be changed after that (static state). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3321) Address possible data corruption in Persistent Store implementations
[ https://issues.apache.org/jira/browse/IGNITE-3321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15396374#comment-15396374 ] Igor Rudyak commented on IGNITE-3321: - How about transactions involving multiple caches? Here is an example: 1) We have an Ignite transaction modifying two different caches 2) When committing the transaction our CacheStore.sessionEnd(...) implementation will be called twice. Once for the first cache and than for the second cache. 3) Lets assume that at the first call to CacheStore.sessionEnd(...) we successfully saved all the changes made by the transaction to the first cache into persistent store. 4) Also lets assume that at the second call to CacheStore.sessionEnd(...) we failed to save into persistent store all the changes made to the second cache - for example there is a network failure between Ignite cluster and persistent store. 5) In the such situation we will have partially committed Ignite transaction data in persistent store. > Address possible data corruption in Persistent Store implementations > > > Key: IGNITE-3321 > URL: https://issues.apache.org/jira/browse/IGNITE-3321 > Project: Ignite > Issue Type: Improvement > Components: cache >Affects Versions: 1.6 > Environment: any >Reporter: Alexandre Boudnik >Assignee: Alexandre Boudnik >Priority: Critical > Original Estimate: 504h > Remaining Estimate: 504h > > When records from partitions on different nodes are committed, each node uses > its own SQL connection. It is possible that one of DML statements will fail > on one of the connections, while others have committed successfully. > And we need to make a very hard decision: > - If we ignore fail then we will lose some changes. > - If we throw an exception we will make inconsistent changes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-3594) ODBC: Add connection properties to support distributed joins.
Vladimir Ozerov created IGNITE-3594: --- Summary: ODBC: Add connection properties to support distributed joins. Key: IGNITE-3594 URL: https://issues.apache.org/jira/browse/IGNITE-3594 Project: Ignite Issue Type: Task Components: odbc Affects Versions: 1.6 Reporter: Vladimir Ozerov Assignee: Igor Sapego Priority: Critical Fix For: 1.7 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-3578) CPP: Add support of distributed joins in SqlQuery & SqlFieldsQuery
[
https://issues.apache.org/jira/browse/IGNITE-3578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov closed IGNITE-3578.
---
> CPP: Add support of distributed joins in SqlQuery & SqlFieldsQuery
> --
>
> Key: IGNITE-3578
> URL: https://issues.apache.org/jira/browse/IGNITE-3578
> Project: Ignite
> Issue Type: Task
> Components: platforms
>Affects Versions: 1.6
>Reporter: Igor Sapego
>Assignee: Vladimir Ozerov
> Labels: cpp
> Fix For: 1.7
>
>
> IGNITE-1232 added new properties to {{SqlQuery}} and {{SqlFieldsQuery}}
> classes. Propagate them to C++.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-3490) Web console: Refactoring server side code to services, append tests
[ https://issues.apache.org/jira/browse/IGNITE-3490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15397003#comment-15397003 ] Vasiliy Sisko commented on IGNITE-3490: --- Tested. Problems not found. > Web console: Refactoring server side code to services, append tests > --- > > Key: IGNITE-3490 > URL: https://issues.apache.org/jira/browse/IGNITE-3490 > Project: Ignite > Issue Type: Bug >Reporter: Andrey Novikov >Assignee: Vasiliy Sisko > > Move code from routes to services. > serve/routes/clusters.js -> serve/services/cluster.js > serve/routes/igfs.js -> serve/services/igfs.js > ... > For example use serve/routes/cache.js -> serve/services/cache.js > For test use as example test/backend/unit/CacheService.test.js -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (IGNITE-3490) Web console: Refactoring server side code to services, append tests
[ https://issues.apache.org/jira/browse/IGNITE-3490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko reopened IGNITE-3490: --- Assignee: Andrey Novikov (was: Vasiliy Sisko) > Web console: Refactoring server side code to services, append tests > --- > > Key: IGNITE-3490 > URL: https://issues.apache.org/jira/browse/IGNITE-3490 > Project: Ignite > Issue Type: Bug >Reporter: Andrey Novikov >Assignee: Andrey Novikov > > Move code from routes to services. > serve/routes/clusters.js -> serve/services/cluster.js > serve/routes/igfs.js -> serve/services/igfs.js > ... > For example use serve/routes/cache.js -> serve/services/cache.js > For test use as example test/backend/unit/CacheService.test.js -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-3595) Improve Enum fields handling in SQL.
Sergi Vladykin created IGNITE-3595: -- Summary: Improve Enum fields handling in SQL. Key: IGNITE-3595 URL: https://issues.apache.org/jira/browse/IGNITE-3595 Project: Ignite Issue Type: Improvement Affects Versions: 1.7 Reporter: Sergi Vladykin Fix For: 2.0 Currently queries like this do not work in Ignite if we use enum field on the left side and enum constant name or ordinal on the right side: select * from A where my_enum = 'ENUM_CONST'; select * from A where my_enum = 3; This is a huge usability issue. We can try to solve it by contributing `User defined Value types` in H2 and implementing the special value type for Enums to handle comparison with String (convert to enum by name) and with int (convert to enum by ordinal). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
