[jira] [Created] (IGNITE-4765) Different partition mapping for caches that use Fair Affinity Function
Alper Tekinalp created IGNITE-4765: -- Summary: Different partition mapping for caches that use Fair Affinity Function Key: IGNITE-4765 URL: https://issues.apache.org/jira/browse/IGNITE-4765 Project: Ignite Issue Type: Bug Reporter: Alper Tekinalp Caches created on different topology versions with fair affinity funtion may have different partition mapping. The cause of this problem is fair affinity function calculates partition mappings based on previous assignments. When rebalancing partitions previous assignments for a cache is known and new assignment calculated based on that. But when you create a new cache there is no previous assignments and the calculation is different. Reproduction steps: - Start node1 - Start cache1 - Start node2 - Partitions for cache1 will be rebalanced - Start cache2 - Check partition mapping for both cache1 and cache2 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (IGNITE-4637) Implement DDL operation completion protocol
[
https://issues.apache.org/jira/browse/IGNITE-4637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Paschenko reassigned IGNITE-4637:
---
Assignee: Alexander Paschenko
> Implement DDL operation completion protocol
> ---
>
> Key: IGNITE-4637
> URL: https://issues.apache.org/jira/browse/IGNITE-4637
> Project: Ignite
> Issue Type: Sub-task
> Components: SQL
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
> Fix For: 2.0
>
>
> *Normal flow*
> 1) When participating node completed operation, it sends
> {{PARTICIPANT_FINISHED}} message to coordinator.
> 2) When coordinator collected responses from all participants, it notifies
> originator with {{FINISHED}} request.
> 3) Originator responds coordinator with {{FINISHED_ACK}} message.
> 4) Coordinator responds to all peers with {{PARTICIPANT_FINISHED_ACK}}
> message.
> *Originator leave*
> 1) Coordinator marks originator as "notified", and sends
> {{PARTICIPANT_FINISHED_ACK}} message to participants after all
> {{PARTICIPANT_FINISHED}} are collected.
> *Participant leave*
> 1) Coordinator marks participant as "finished" and no longer waits for any
> responses from it.
> *Coordinator leave*
> 1) The oldest node among remaining participants is elected as new coordinator.
> 2) Coordinator *polls* explicitly operation state from participants with
> {{IS_PARTICIPANT_FINISHED}} message.
> 3) Participants re-send {{PARTICIPANT_FINISHED}} message to new coordinator.
> 4) If all participant nodes have left, originator feature is completed with
> error.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (IGNITE-4659) Migrate to webpack@2
[ https://issues.apache.org/jira/browse/IGNITE-4659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko reassigned IGNITE-4659: - Assignee: Vasiliy Sisko (was: Andrey Novikov) > Migrate to webpack@2 > > > Key: IGNITE-4659 > URL: https://issues.apache.org/jira/browse/IGNITE-4659 > Project: Ignite > Issue Type: Task > Components: wizards >Affects Versions: 1.9 >Reporter: Dmitriy Shabalin >Assignee: Vasiliy Sisko > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-4659) Migrate to webpack@2
[ https://issues.apache.org/jira/browse/IGNITE-4659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15891668#comment-15891668 ] Vasiliy Sisko commented on IGNITE-4659: --- # Show query link try to open some page but should open dialog. > Migrate to webpack@2 > > > Key: IGNITE-4659 > URL: https://issues.apache.org/jira/browse/IGNITE-4659 > Project: Ignite > Issue Type: Task > Components: wizards >Affects Versions: 1.9 >Reporter: Dmitriy Shabalin >Assignee: Andrey Novikov > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-4764) Web console: Correctly handle cache removing for cache checlpoint SPI
Vasiliy Sisko created IGNITE-4764: - Summary: Web console: Correctly handle cache removing for cache checlpoint SPI Key: IGNITE-4764 URL: https://issues.apache.org/jira/browse/IGNITE-4764 Project: Ignite Issue Type: Bug Components: UI, wizards Reporter: Vasiliy Sisko # Should be disabled when no caches configured in cluster. # Should remove selected cache when cache is removed from cluster. # Message when no caches configured for cluster is too long for field. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Issue Comment Deleted] (IGNITE-4659) Migrate to webpack@2
[ https://issues.apache.org/jira/browse/IGNITE-4659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko updated IGNITE-4659: -- Comment: was deleted (was: # Affix on configuration pages change position on minimal scroll of page.) > Migrate to webpack@2 > > > Key: IGNITE-4659 > URL: https://issues.apache.org/jira/browse/IGNITE-4659 > Project: Ignite > Issue Type: Task > Components: wizards >Affects Versions: 1.9 >Reporter: Dmitriy Shabalin >Assignee: Andrey Novikov > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-4659) Migrate to webpack@2
[ https://issues.apache.org/jira/browse/IGNITE-4659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15891550#comment-15891550 ] Vasiliy Sisko commented on IGNITE-4659: --- # Affix on configuration pages change position on minimal scroll of page. > Migrate to webpack@2 > > > Key: IGNITE-4659 > URL: https://issues.apache.org/jira/browse/IGNITE-4659 > Project: Ignite > Issue Type: Task > Components: wizards >Affects Versions: 1.9 >Reporter: Dmitriy Shabalin >Assignee: Andrey Novikov > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Issue Comment Deleted] (IGNITE-4659) Migrate to webpack@2
[ https://issues.apache.org/jira/browse/IGNITE-4659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko updated IGNITE-4659: -- Comment: was deleted (was: # Empty dropdowns is not disabled. F.e. Remove caches and create cluster. Caches dropdown should be disabled. # Does not show validation triangle for Java classes, number fields, ip-address.) > Migrate to webpack@2 > > > Key: IGNITE-4659 > URL: https://issues.apache.org/jira/browse/IGNITE-4659 > Project: Ignite > Issue Type: Task > Components: wizards >Affects Versions: 1.9 >Reporter: Dmitriy Shabalin >Assignee: Andrey Novikov > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-4659) Migrate to webpack@2
[ https://issues.apache.org/jira/browse/IGNITE-4659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15891508#comment-15891508 ] Vasiliy Sisko commented on IGNITE-4659: --- # Empty dropdowns is not disabled. F.e. Remove caches and create cluster. Caches dropdown should be disabled. # Does not show validation triangle for Java classes, number fields, ip-address. > Migrate to webpack@2 > > > Key: IGNITE-4659 > URL: https://issues.apache.org/jira/browse/IGNITE-4659 > Project: Ignite > Issue Type: Task > Components: wizards >Affects Versions: 1.9 >Reporter: Dmitriy Shabalin >Assignee: Andrey Novikov > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-4757) SQL Joins Metrics
[
https://issues.apache.org/jira/browse/IGNITE-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda updated IGNITE-4757:
Description:
SQL queries monitoring part has to be improved. Suggest adding the metrics
below.
Per-query metrics. Total history size is defined by
{{CacheConfiguration.getQueryDetailMetricsSize()}}:
* if a query was executed in the collocated or non-collocated mode. Three
results are valid: collocated, non-collocated, simple query (no joins).
* non-collocated query: size of the data exchanged between the nodes to
complete a specific join. If there are multiple joins in the query we need to
provide this metric for every of them.
* non-collocated query: did a query do broadcast or unicast to get data needed
to complete a join. If there are multiple joins in the query we need to provide
this metric for every of them.
* non-collocated and collocated query: a part of the time spent joining the
data. If there are multiple joins in the query we need to provide this metric
for every of them.
CacheMetrics:
* an average number of executed SQL queries (collocated, non-collocated, simple
query (no joins)).
Discussion from the dev list:
http://apache-ignite-developers.2346864.n4.nabble.com/Additional-SQL-metrics-td14945.html
was:
SQL queries monitoring part has to be improved. Suggest adding the metrics
below.
Per-query metrics. Total history size is defined by
{{CacheConfiguration.getQueryDetailMetricsSize()}}:
* if a query was executed in the collocated or non-collocated mode. Three
results are valid: collocated, non-collocated, simple query (no joins).
* non-collocated query: size of the data exchanged between the nodes to
complete a specific join. If there are multiple joins in the query we need to
provide this metric for every of them.
* non-collocated query: did a query do broadcast or unicast to get data needed
to complete a join. If there are multiple joins in the query we need to provide
this metric for every of them.
* non-collocated and collocated query: a part of the time spent joining the
data. If there are multiple joins in the query we need to provide this metric
for every of them.
CacheMetrics:
* an average number of executed SQL queries (collocated, non-collocated, simple
query (no joins)).
> SQL Joins Metrics
> -
>
> Key: IGNITE-4757
> URL: https://issues.apache.org/jira/browse/IGNITE-4757
> Project: Ignite
> Issue Type: Task
>Reporter: Denis Magda
>
> SQL queries monitoring part has to be improved. Suggest adding the metrics
> below.
> Per-query metrics. Total history size is defined by
> {{CacheConfiguration.getQueryDetailMetricsSize()}}:
> * if a query was executed in the collocated or non-collocated mode. Three
> results are valid: collocated, non-collocated, simple query (no joins).
> * non-collocated query: size of the data exchanged between the nodes to
> complete a specific join. If there are multiple joins in the query we need to
> provide this metric for every of them.
> * non-collocated query: did a query do broadcast or unicast to get data
> needed to complete a join. If there are multiple joins in the query we need
> to provide this metric for every of them.
> * non-collocated and collocated query: a part of the time spent joining the
> data. If there are multiple joins in the query we need to provide this metric
> for every of them.
> CacheMetrics:
> * an average number of executed SQL queries (collocated, non-collocated,
> simple query (no joins)).
> Discussion from the dev list:
> http://apache-ignite-developers.2346864.n4.nabble.com/Additional-SQL-metrics-td14945.html
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-4746) Add documentation for SQL query parallelism
[ https://issues.apache.org/jira/browse/IGNITE-4746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890978#comment-15890978 ] Denis Magda commented on IGNITE-4746: - [~vozerov], thanks. I've reviewed your changes. They look good to me. However, I had to remove 1.9 version introduced by you and move your changes to this [1] hidden page under 1.8. Presently we follow the rules described here [2] if a new documentation has to be added. This helps us to resolve issues we had in the past. [~pgarg], please review [1]. [1] https://apacheignite.readme.io/docs/performance-and-debugging-19#query-parallelism [2] https://cwiki.apache.org/confluence/display/IGNITE/Documentation > Add documentation for SQL query parallelism > --- > > Key: IGNITE-4746 > URL: https://issues.apache.org/jira/browse/IGNITE-4746 > Project: Ignite > Issue Type: Task > Components: documentation, SQL >Reporter: Vladimir Ozerov >Assignee: Denis Magda > Fix For: 1.9 > > > See IGNITE-4106. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (IGNITE-4746) Add documentation for SQL query parallelism
[ https://issues.apache.org/jira/browse/IGNITE-4746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda reassigned IGNITE-4746: --- Assignee: Prachi Garg (was: Denis Magda) > Add documentation for SQL query parallelism > --- > > Key: IGNITE-4746 > URL: https://issues.apache.org/jira/browse/IGNITE-4746 > Project: Ignite > Issue Type: Task > Components: documentation, SQL >Reporter: Vladimir Ozerov >Assignee: Prachi Garg > Fix For: 1.9 > > > See IGNITE-4106. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-4617) CPP: Implement Field-access methods for binary objects
[
https://issues.apache.org/jira/browse/IGNITE-4617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890955#comment-15890955
]
Igor Sapego commented on IGNITE-4617:
-
Seems like the only solution here is to refactor Java {{BinaryMetadata}} class
to store not only type IDs for the fields but also fiel IDs itself. I'm
currently working on this approach.
> CPP: Implement Field-access methods for binary objects
> --
>
> Key: IGNITE-4617
> URL: https://issues.apache.org/jira/browse/IGNITE-4617
> Project: Ignite
> Issue Type: Task
> Components: platforms
>Affects Versions: 1.8
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Labels: cpp
> Fix For: 2.0
>
>
> Currently we have very limited implementation of binary objects that does not
> provide access to fields of the binary object. At least such methods as
> {{HasField}} and {{GetField}} should be implemented.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-4761) ServiceProcessor hangs while stopping on unstable topology.
[ https://issues.apache.org/jira/browse/IGNITE-4761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov updated IGNITE-4761: - Priority: Critical (was: Major) > ServiceProcessor hangs while stopping on unstable topology. > --- > > Key: IGNITE-4761 > URL: https://issues.apache.org/jira/browse/IGNITE-4761 > Project: Ignite > Issue Type: Bug > Components: cache, managed services >Affects Versions: 1.7 >Reporter: Andrew Mashenkov >Priority: Critical > Fix For: 2.0 > > > GridServiceProcessor.onKernalStop can be blocked on taking busyLock when > the lock is being held by TopologyListener while infinite waiting for > readyAffinityFuture. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-4681) Apply new future adapter
[ https://issues.apache.org/jira/browse/IGNITE-4681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890626#comment-15890626 ] ASF GitHub Bot commented on IGNITE-4681: GitHub user gvvinblade opened a pull request: https://github.com/apache/ignite/pull/1584 IGNITE-4681 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4681 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/1584.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 #1584 > Apply new future adapter > > > Key: IGNITE-4681 > URL: https://issues.apache.org/jira/browse/IGNITE-4681 > Project: Ignite > Issue Type: Improvement >Reporter: Yakov Zhdanov >Assignee: Yakov Zhdanov > Fix For: 2.0 > > Attachments: GridFutAdapter over jdk8.java > > > Attached is reference future adapter implementation. It is proven to consume > less memory and it does not require explicit locking on listen(). We need to > apply it. > Known threats: > # if future is completed normally, but with Throwable as result, get() throws > exception. This can be fixed with internal wrapper class > # listener notification order changes - this is known to cause problems > org.apache.ignite.internal.processors.rest.ClientMemcachedProtocolSelfTest#testGetBulk > which is minor but still. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-4611) Write IgniteUuid with BinaryMarshaller
[
https://issues.apache.org/jira/browse/IGNITE-4611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890448#comment-15890448
]
ASF GitHub Bot commented on IGNITE-4611:
Github user daradurvs closed the pull request at:
https://github.com/apache/ignite/pull/1548
> Write IgniteUuid with BinaryMarshaller
> --
>
> Key: IGNITE-4611
> URL: https://issues.apache.org/jira/browse/IGNITE-4611
> Project: Ignite
> Issue Type: Improvement
> Components: binary
>Affects Versions: 1.8
>Reporter: Pavel Tupitsyn
>Assignee: Vyacheslav Daradur
> Fix For: 2.0
>
>
> Currently {{IgniteUuid}} is written with {{OptimizedMarshaller}}
> (it is not included in {{BinaryContext.BINARYLIZABLE_SYS_CLSS}}).
> This prevents it from being read on other platforms (.NET, C++).
> Use {{BinaryMarshaller}} instead.
> Dev list thread:
> http://apache-ignite-developers.2346864.n4.nabble.com/Write-IgniteUuid-with-BinaryMarshaller-td13971.html
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-4611) Write IgniteUuid with BinaryMarshaller
[
https://issues.apache.org/jira/browse/IGNITE-4611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890447#comment-15890447
]
ASF GitHub Bot commented on IGNITE-4611:
Github user daradurvs closed the pull request at:
https://github.com/apache/ignite/pull/1551
> Write IgniteUuid with BinaryMarshaller
> --
>
> Key: IGNITE-4611
> URL: https://issues.apache.org/jira/browse/IGNITE-4611
> Project: Ignite
> Issue Type: Improvement
> Components: binary
>Affects Versions: 1.8
>Reporter: Pavel Tupitsyn
>Assignee: Vyacheslav Daradur
> Fix For: 2.0
>
>
> Currently {{IgniteUuid}} is written with {{OptimizedMarshaller}}
> (it is not included in {{BinaryContext.BINARYLIZABLE_SYS_CLSS}}).
> This prevents it from being read on other platforms (.NET, C++).
> Use {{BinaryMarshaller}} instead.
> Dev list thread:
> http://apache-ignite-developers.2346864.n4.nabble.com/Write-IgniteUuid-with-BinaryMarshaller-td13971.html
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (IGNITE-4680) Properly split batch atomic cache operations between stripes (putAll, removeAll, etc)
[ https://issues.apache.org/jira/browse/IGNITE-4680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Dudkov reassigned IGNITE-4680: - Assignee: Konstantin Dudkov (was: Yakov Zhdanov) > Properly split batch atomic cache operations between stripes (putAll, > removeAll, etc) > - > > Key: IGNITE-4680 > URL: https://issues.apache.org/jira/browse/IGNITE-4680 > Project: Ignite > Issue Type: Improvement > Components: cache >Reporter: Yakov Zhdanov >Assignee: Konstantin Dudkov > Fix For: 2.0 > > > Need to revisit keys/requests mapping procedure and map the update directly > to stripe on remote node. > Here are some points: > # Abovementioned will require adding stripes count attribute to node's > attribute list > # Need to make sure we take all benefits of biased locking and stripes never > get mutually blocked > # locking all entries before processing request can be removed since it does > not make too much sense to atomic cache -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-4758) Introduce MemoryPolicy configuration and adapt PageMemory concept to multiple memory policies
[ https://issues.apache.org/jira/browse/IGNITE-4758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890379#comment-15890379 ] Sergey Chugunov commented on IGNITE-4758: - Fixed all compilation errors emerged after introducing MemoryPolicy and making related breaking changes. Tests look good, but validation logic especially around default MemoryPolicy needs clarification. > Introduce MemoryPolicy configuration and adapt PageMemory concept to multiple > memory policies > - > > Key: IGNITE-4758 > URL: https://issues.apache.org/jira/browse/IGNITE-4758 > Project: Ignite > Issue Type: Sub-task > Components: cache >Reporter: Sergey Chugunov >Assignee: Sergey Chugunov > Fix For: 2.0 > > Original Estimate: 336h > Time Spent: 16h > Remaining Estimate: 320h > > h2. Acceptance Criteria > # For each named *MemoryPolicy* described in configuration new named > *PageMemory* is created. > # Each cache on startup is assigned to corresponding *PageMemory* instance > which is stored in context of the cache. > # A default *PageMemory* is used to store content of caches with no > *MemoryPolicy* configured. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-2552) Eviction policy must consider either max size or max entries count
[ https://issues.apache.org/jira/browse/IGNITE-2552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890329#comment-15890329 ] Andrey Gura commented on IGNITE-2552: - I've reviewed your changes and have some comments (mostly cosmetic). Could you please fix this comment? See review in Upsource for details. > Eviction policy must consider either max size or max entries count > -- > > Key: IGNITE-2552 > URL: https://issues.apache.org/jira/browse/IGNITE-2552 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 1.5.0.final >Reporter: Denis Magda >Assignee: Alexey Kuznetsov >Priority: Minor > Fix For: 2.0 > > > Presently both max size and max entries number are considered by eviction > policy logic even if the only one is set by user explicitly. > This behavior must be reworked in a way that if one of the parameters is set > explicitly then only it will be used by eviction policy while the other one > will be ignored. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-4550) Move service deployment to certain test
[ https://issues.apache.org/jira/browse/IGNITE-4550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890279#comment-15890279 ] ASF GitHub Bot commented on IGNITE-4550: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1437 > Move service deployment to certain test > --- > > Key: IGNITE-4550 > URL: https://issues.apache.org/jira/browse/IGNITE-4550 > Project: Ignite > Issue Type: Improvement > Components: general >Affects Versions: 1.8 >Reporter: Andrew Mashenkov >Assignee: Andrew Mashenkov > Fix For: 1.9 > > > GridCacheAbstractFullApiSelfTest has service deployment in beforeTest() > method. > It look like there is no need to do this for all tests and service deployment > should be moved to testTransformResourceInjection(). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-4169) Data streamer mode for DML
[ https://issues.apache.org/jira/browse/IGNITE-4169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890280#comment-15890280 ] ASF GitHub Bot commented on IGNITE-4169: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1553 > Data streamer mode for DML > -- > > Key: IGNITE-4169 > URL: https://issues.apache.org/jira/browse/IGNITE-4169 > Project: Ignite > Issue Type: New Feature > Components: SQL >Affects Versions: 1.8 >Reporter: Alexander Paschenko >Assignee: Alexander Paschenko > Fix For: 1.9 > > > SQL INSERT and MERGE are supposed to support data streamer mode which should > be turned on by JDBC connection string param. > Note: particular details of usage means and implementation of this mode, as > well as urgency of this feature are yet to be discussed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-4458) Hadoop: striped shuffle mode must be enabled by default
[
https://issues.apache.org/jira/browse/IGNITE-4458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890284#comment-15890284
]
ASF GitHub Bot commented on IGNITE-4458:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/1390
> Hadoop: striped shuffle mode must be enabled by default
> ---
>
> Key: IGNITE-4458
> URL: https://issues.apache.org/jira/browse/IGNITE-4458
> Project: Ignite
> Issue Type: Task
> Components: hadoop
>Affects Versions: 1.8
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
> Fix For: 2.0
>
>
> Striped mode is enabled with
> {{HadoopJobProperty.SHUFFLE_MAPPER_STRIPED_OUTPUT}}. It shows consistently
> better results comparing to original shuffling mode.
> Possible solutions:
> 1) Make this property enabled by default;
> 2) Or totally remove previous mode (do not think it is a good idea)..
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-4742) Flaky IgniteCacheUpdateSqlQuerySelfTest.testTypeConversions
[ https://issues.apache.org/jira/browse/IGNITE-4742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890281#comment-15890281 ] ASF GitHub Bot commented on IGNITE-4742: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1569 > Flaky IgniteCacheUpdateSqlQuerySelfTest.testTypeConversions > --- > > Key: IGNITE-4742 > URL: https://issues.apache.org/jira/browse/IGNITE-4742 > Project: Ignite > Issue Type: Bug > Components: SQL >Affects Versions: 1.8 >Reporter: Alexander Paschenko >Assignee: Alexander Paschenko >Priority: Minor > Fix For: 1.9 > > > This test fails randomly on various query related suites and very seldom > locally. Seems to be test problem and not of what is tested. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-4741) JdbcStreamingSelfTest is not reliable
[
https://issues.apache.org/jira/browse/IGNITE-4741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890283#comment-15890283
]
ASF GitHub Bot commented on IGNITE-4741:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/1568
> JdbcStreamingSelfTest is not reliable
> -
>
> Key: IGNITE-4741
> URL: https://issues.apache.org/jira/browse/IGNITE-4741
> Project: Ignite
> Issue Type: Test
> Components: jdbc-driver
>Affects Versions: 1.8
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
>Priority: Minor
> Fix For: 1.9
>
>
> Test fails from time to time because it waits for some conditions based on
> {{Thread.sleep(1000L}}, which is not reliable enough.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-4409) UUID fields of the key class deserialized in a wrong way on INSERT.
[
https://issues.apache.org/jira/browse/IGNITE-4409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890282#comment-15890282
]
ASF GitHub Bot commented on IGNITE-4409:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/1554
> UUID fields of the key class deserialized in a wrong way on INSERT.
> ---
>
> Key: IGNITE-4409
> URL: https://issues.apache.org/jira/browse/IGNITE-4409
> Project: Ignite
> Issue Type: Bug
> Components: SQL
>Affects Versions: 1.8
>Reporter: Igor Sapego
>Assignee: Alexander Paschenko
> Fix For: 1.9
>
>
> Consider the following case. There is a class which is used as Key on C++
> side. It contains 3 fields: String, Timestamp and UUID. There is also a value
> of the type Integer. Record of the cache is being inserted with
> {{SqlFieldsQuery}}:
> {noformat}
> INSERT INTO Integer (str, ts, guid, _val) VALUES (?, ?, ?, ?)
> {noformat}
> String, Timestamp and Integer values serialized and desirialized just fine,
> but UUID value is passed further just like byte array of 17 bytes, first of
> which is 10 (UUID type header in Binary format), so later it gets converted
> here:
> {noformat}
> "main@1" prio=5 tid=0x1 nid=NA runnable
> java.lang.Thread.State: RUNNABLE
> at org.h2.value.ValueUuid.get(ValueUuid.java:68)
> at org.h2.value.Value.convertTo(Value.java:861)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.convert(DmlStatementsProcessor.java:637)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.rowToKeyValue(DmlStatementsProcessor.java:868)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.doInsert(DmlStatementsProcessor.java:745)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.executeUpdateStatement(DmlStatementsProcessor.java:286)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFields(DmlStatementsProcessor.java:159)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFieldsTwoStep(DmlStatementsProcessor.java:189)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryTwoStep(IgniteH2Indexing.java:1266)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:812)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:810)
> at
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:1777)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.queryTwoStep(GridQueryProcessor.java:810)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:749)
> at
> org.apache.ignite.internal.processors.platform.cache.PlatformCache.runFieldsQuery(PlatformCache.java:1205)
> at
> org.apache.ignite.internal.processors.platform.cache.PlatformCache.processInStreamOutObject(PlatformCache.java:837)
> at
> org.apache.ignite.internal.processors.platform.PlatformAbstractTarget.inStreamOutObject(PlatformAbstractTarget.java:90)
> {noformat}
> Obviously enough, it gets deserialized wrong because of the header byte and
> as a result, we get wrong key instance in the cache.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-1) Need to implement JCache specification
[ https://issues.apache.org/jira/browse/IGNITE-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890277#comment-15890277 ] ASF GitHub Bot commented on IGNITE-1: - Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1400 > Need to implement JCache specification > -- > > Key: IGNITE-1 > URL: https://issues.apache.org/jira/browse/IGNITE-1 > Project: Ignite > Issue Type: Task >Reporter: Dmitriy Setrakyan >Assignee: Alexey Goncharuk > Fix For: sprint-2 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-3939) Compact long zero values binary representation
[
https://issues.apache.org/jira/browse/IGNITE-3939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890257#comment-15890257
]
Taras Ledkov commented on IGNITE-3939:
--
In case the special {{ZERO}} offset is used for primitives or special objects
we have to make the metadata lookup on one filed unmarshaling.
It can be cause of the performance drop for SQL.
So, the special case will be implemented only for {{null}} references.
> Compact long zero values binary representation
> --
>
> Key: IGNITE-3939
> URL: https://issues.apache.org/jira/browse/IGNITE-3939
> Project: Ignite
> Issue Type: Improvement
> Components: binary
>Affects Versions: 1.7
>Reporter: Andrew Mashenkov
>Assignee: Taras Ledkov
> Fix For: 2.0
>
>
> We can use separate type for Long zero values and exclude 8-byte value from
> binary representation. This will reduce memory footprint and network load.
> Compatibility with previous versions MUST be preserved.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (IGNITE-4574) Introduce user value types to H2 w/custom conversion logic
[ https://issues.apache.org/jira/browse/IGNITE-4574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Kalashnikov reassigned IGNITE-4574: -- Assignee: Sergey Kalashnikov (was: Alexander Paschenko) > Introduce user value types to H2 w/custom conversion logic > -- > > Key: IGNITE-4574 > URL: https://issues.apache.org/jira/browse/IGNITE-4574 > Project: Ignite > Issue Type: Sub-task > Components: SQL >Reporter: Alexander Paschenko >Assignee: Sergey Kalashnikov > Fix For: 2.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-3487) _key and _val fields should be excluded from 'select * from' queries
[
https://issues.apache.org/jira/browse/IGNITE-3487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15889960#comment-15889960
]
Sergey Kalashnikov commented on IGNITE-3487:
[~vozerov], I have resolved the conflicts with ignite-2.0 branch per your
request.
> _key and _val fields should be excluded from 'select * from' queries
>
>
> Key: IGNITE-3487
> URL: https://issues.apache.org/jira/browse/IGNITE-3487
> Project: Ignite
> Issue Type: Improvement
> Components: SQL
>Affects Versions: 1.6
>Reporter: Valentin Kulichenko
>Assignee: Sergey Kalashnikov
> Labels: important
> Fix For: 2.0
>
>
> We have a pretty serious usability issue - predefined {{_key}} and {{_val}}
> fields are returned when query like {{select * from}} is executed. First of
> all, this is counterintuitive because user never defines or configures these
> fields. Second of all, they actually duplicate all other fields. And finally,
> they cause serialization exceptions because classes for key and value are not
> always available.
> We should exclude these fields from {{select * from}} queries, but this is a
> compatibility breaking change. It should be done in 2.0.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Comment Edited] (IGNITE-4694) Add tests to check there are no memory leaks in PageMemory
[ https://issues.apache.org/jira/browse/IGNITE-4694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15889943#comment-15889943 ] Igor Seliverstov edited comment on IGNITE-4694 at 3/1/17 10:38 AM: --- Changes are placed with IGNITE-4712 request together https://github.com/apache/ignite/pull/1559 was (Author: gvvinblade): Changes are placed with IGNITE-4712 request tohether https://github.com/apache/ignite/pull/1559 > Add tests to check there are no memory leaks in PageMemory > -- > > Key: IGNITE-4694 > URL: https://issues.apache.org/jira/browse/IGNITE-4694 > Project: Ignite > Issue Type: Sub-task > Components: cache >Reporter: Semen Boikov >Assignee: Semen Boikov > Fix For: 2.0 > > > Need add several tests running for 5-10 munites verifying there are no memory > leaks in new data structures based of PageMemory: > - test various page size > - test various objects size > - test put/get/remove operations > - test create cache/destroy cache operations > - test cases when indexes enabled/disabled > - test case when cache expiry policy is used > New tests should be added in new test suite. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-4694) Add tests to check there are no memory leaks in PageMemory
[ https://issues.apache.org/jira/browse/IGNITE-4694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15889943#comment-15889943 ] Igor Seliverstov commented on IGNITE-4694: -- Changes are placed with IGNITE-4712 request tohether https://github.com/apache/ignite/pull/1559 > Add tests to check there are no memory leaks in PageMemory > -- > > Key: IGNITE-4694 > URL: https://issues.apache.org/jira/browse/IGNITE-4694 > Project: Ignite > Issue Type: Sub-task > Components: cache >Reporter: Semen Boikov >Assignee: Semen Boikov > Fix For: 2.0 > > > Need add several tests running for 5-10 munites verifying there are no memory > leaks in new data structures based of PageMemory: > - test various page size > - test various objects size > - test put/get/remove operations > - test create cache/destroy cache operations > - test cases when indexes enabled/disabled > - test case when cache expiry policy is used > New tests should be added in new test suite. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-4620) CPP: Add documentation for DML
[ https://issues.apache.org/jira/browse/IGNITE-4620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15889929#comment-15889929 ] Igor Sapego commented on IGNITE-4620: - [~dmagda] Ok. > CPP: Add documentation for DML > -- > > Key: IGNITE-4620 > URL: https://issues.apache.org/jira/browse/IGNITE-4620 > Project: Ignite > Issue Type: Task > Components: documentation, platforms >Affects Versions: 1.8 >Reporter: Igor Sapego >Assignee: Igor Sapego > Labels: cpp > Fix For: 1.9 > > > We need to add documentation for DML support once its implemented in C++ > client. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-4694) Add tests to check there are no memory leaks in PageMemory
[ https://issues.apache.org/jira/browse/IGNITE-4694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15889927#comment-15889927 ] ASF GitHub Bot commented on IGNITE-4694: Github user gvvinblade closed the pull request at: https://github.com/apache/ignite/pull/1535 > Add tests to check there are no memory leaks in PageMemory > -- > > Key: IGNITE-4694 > URL: https://issues.apache.org/jira/browse/IGNITE-4694 > Project: Ignite > Issue Type: Sub-task > Components: cache >Reporter: Semen Boikov >Assignee: Semen Boikov > Fix For: 2.0 > > > Need add several tests running for 5-10 munites verifying there are no memory > leaks in new data structures based of PageMemory: > - test various page size > - test various objects size > - test put/get/remove operations > - test create cache/destroy cache operations > - test cases when indexes enabled/disabled > - test case when cache expiry policy is used > New tests should be added in new test suite. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-4659) Migrate to webpack@2
[ https://issues.apache.org/jira/browse/IGNITE-4659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15889917#comment-15889917 ] Andrey Novikov commented on IGNITE-4659: Reviewed. [~vsisko], please test popover, tooltip, alert, modal > Migrate to webpack@2 > > > Key: IGNITE-4659 > URL: https://issues.apache.org/jira/browse/IGNITE-4659 > Project: Ignite > Issue Type: Task > Components: wizards >Affects Versions: 1.9 >Reporter: Dmitriy Shabalin >Assignee: Andrey Novikov > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (IGNITE-4029) Local ContinuousQueries on PARTITIONED caches may await for previously rejected events
[
https://issues.apache.org/jira/browse/IGNITE-4029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolay Tikhonov reassigned IGNITE-4029:
Assignee: Nikolay Tikhonov
> Local ContinuousQueries on PARTITIONED caches may await for previously
> rejected events
> --
>
> Key: IGNITE-4029
> URL: https://issues.apache.org/jira/browse/IGNITE-4029
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.7, 1.8
>Reporter: David Bidorff
>Assignee: Nikolay Tikhonov
> Attachments: Ignite4029Test.java
>
>
> {{CacheContinuousQueryHandler.PartitionRecovery.collectEntries()}} stores and
> updates the identifier of the next expected event. However, some events may
> be rejected before even reaching the query handler, preventing this counter
> to be incremented and leading the next events to be queued until
> {{MAX_BUFF_SIZE}} is reached.
> This happens after data was rebalanced: some events may be handled as
> happening on a backup node, leading the test {{primary || skipPrimaryCheck}}
> (on line 410 of {{CacheContinuousQueryHandler.onEntryUpdate()}}) to be false
> and preventing the previously mentioned counter to be increased.
> I'm not sure if the main problem is about those events being considered has
> happening on a backup node or if it is about the counter not being
> incremented, but either way, this can be problematic on caches with very few
> 'update events' where the {{MAX_BUFF_SIZE}} is not reached quickly.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Issue Comment Deleted] (IGNITE-4473) Client should re-try connection attempt in case of concurrent network failure
[ https://issues.apache.org/jira/browse/IGNITE-4473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Karachentsev updated IGNITE-4473: Comment: was deleted (was: Looks like the same issue) > Client should re-try connection attempt in case of concurrent network failure > - > > Key: IGNITE-4473 > URL: https://issues.apache.org/jira/browse/IGNITE-4473 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 1.8 >Reporter: Vladimir Ozerov >Assignee: Dmitry Karachentsev > Fix For: 2.0 > > > *Problem* > Consider the following scenario: > 1) Client started, but there are no servers, so it hangs somewhere inside > start routine. > 2) Server appears, and discovery finishes successfully. > 3) Nodes start talking to each other through communication SPI to finish > start process (e.g. to complete exchange). > 4) But network glitch occurs and server becomes unreachable. > *Expected behavior* > Client disconnects and hangs waiting for reconnect. > *Actual behavior* > Client throws an exception and never tries to reconnect. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-4473) Client should re-try connection attempt in case of concurrent network failure
[ https://issues.apache.org/jira/browse/IGNITE-4473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15889875#comment-15889875 ] Dmitry Karachentsev commented on IGNITE-4473: - Looks like the same issue > Client should re-try connection attempt in case of concurrent network failure > - > > Key: IGNITE-4473 > URL: https://issues.apache.org/jira/browse/IGNITE-4473 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 1.8 >Reporter: Vladimir Ozerov >Assignee: Dmitry Karachentsev > Fix For: 2.0 > > > *Problem* > Consider the following scenario: > 1) Client started, but there are no servers, so it hangs somewhere inside > start routine. > 2) Server appears, and discovery finishes successfully. > 3) Nodes start talking to each other through communication SPI to finish > start process (e.g. to complete exchange). > 4) But network glitch occurs and server becomes unreachable. > *Expected behavior* > Client disconnects and hangs waiting for reconnect. > *Actual behavior* > Client throws an exception and never tries to reconnect. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-4029) Local ContinuousQueries on PARTITIONED caches may await for previously rejected events
[
https://issues.apache.org/jira/browse/IGNITE-4029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Bidorff updated IGNITE-4029:
--
Attachment: Ignite4029Test.java
So, the more I look into my tests, the weirder it gets. I updated my tests (and
provided it as an attachment to this ticket) and it seems that the order of the
nodes startup is important :
* If node A is started before node B, then test succeeds every time.
* If node B is started before node A, then test fails every time.
> Local ContinuousQueries on PARTITIONED caches may await for previously
> rejected events
> --
>
> Key: IGNITE-4029
> URL: https://issues.apache.org/jira/browse/IGNITE-4029
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.7, 1.8
>Reporter: David Bidorff
> Attachments: Ignite4029Test.java
>
>
> {{CacheContinuousQueryHandler.PartitionRecovery.collectEntries()}} stores and
> updates the identifier of the next expected event. However, some events may
> be rejected before even reaching the query handler, preventing this counter
> to be incremented and leading the next events to be queued until
> {{MAX_BUFF_SIZE}} is reached.
> This happens after data was rebalanced: some events may be handled as
> happening on a backup node, leading the test {{primary || skipPrimaryCheck}}
> (on line 410 of {{CacheContinuousQueryHandler.onEntryUpdate()}}) to be false
> and preventing the previously mentioned counter to be increased.
> I'm not sure if the main problem is about those events being considered has
> happening on a backup node or if it is about the counter not being
> incremented, but either way, this can be problematic on caches with very few
> 'update events' where the {{MAX_BUFF_SIZE}} is not reached quickly.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Closed] (IGNITE-4702) Optimize BinaryMarshaller field reading in case all object fields are of fixed size
[
https://issues.apache.org/jira/browse/IGNITE-4702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov closed IGNITE-4702.
---
> Optimize BinaryMarshaller field reading in case all object fields are of
> fixed size
> ---
>
> Key: IGNITE-4702
> URL: https://issues.apache.org/jira/browse/IGNITE-4702
> Project: Ignite
> Issue Type: Task
> Components: general
>Reporter: Vladimir Ozerov
> Labels: performance
> Fix For: 2.0
>
>
> In order to get field position within {{BinaryObject}} we do the following:
> 1) Lookup schema
> 2) Get field order
> 3) Find field position in order
> 4) Jump to the field
> If all object fields have fixed length, then it's body will always be of the
> same size, and relative field positions will be constant. This also
> applicable to objects having only some fields of known size, if these fields
> are on the head positions.
> We can add this information to schema and modify lookup routine as follows:
> 1) Lookup schema
> 2) Get field position by field ID immediately
> 4) Jump to the field
> This will save us from footer lookups thus decreasing overall field lookup
> time. It could be especially important for queries.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-4029) Local ContinuousQueries on PARTITIONED caches may await for previously rejected events
[
https://issues.apache.org/jira/browse/IGNITE-4029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Bidorff updated IGNITE-4029:
--
Attachment: (was: TestIgnite4029.java)
> Local ContinuousQueries on PARTITIONED caches may await for previously
> rejected events
> --
>
> Key: IGNITE-4029
> URL: https://issues.apache.org/jira/browse/IGNITE-4029
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.7, 1.8
>Reporter: David Bidorff
> Attachments: Ignite4029Test.java
>
>
> {{CacheContinuousQueryHandler.PartitionRecovery.collectEntries()}} stores and
> updates the identifier of the next expected event. However, some events may
> be rejected before even reaching the query handler, preventing this counter
> to be incremented and leading the next events to be queued until
> {{MAX_BUFF_SIZE}} is reached.
> This happens after data was rebalanced: some events may be handled as
> happening on a backup node, leading the test {{primary || skipPrimaryCheck}}
> (on line 410 of {{CacheContinuousQueryHandler.onEntryUpdate()}}) to be false
> and preventing the previously mentioned counter to be increased.
> I'm not sure if the main problem is about those events being considered has
> happening on a backup node or if it is about the counter not being
> incremented, but either way, this can be problematic on caches with very few
> 'update events' where the {{MAX_BUFF_SIZE}} is not reached quickly.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (IGNITE-4702) Optimize BinaryMarshaller field reading in case all object fields are of fixed size
[
https://issues.apache.org/jira/browse/IGNITE-4702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov resolved IGNITE-4702.
-
Resolution: Won't Fix
Conflicts with IGNITE-3939, which is of greater priority. Closing.
> Optimize BinaryMarshaller field reading in case all object fields are of
> fixed size
> ---
>
> Key: IGNITE-4702
> URL: https://issues.apache.org/jira/browse/IGNITE-4702
> Project: Ignite
> Issue Type: Task
> Components: general
>Reporter: Vladimir Ozerov
> Labels: performance
> Fix For: 2.0
>
>
> In order to get field position within {{BinaryObject}} we do the following:
> 1) Lookup schema
> 2) Get field order
> 3) Find field position in order
> 4) Jump to the field
> If all object fields have fixed length, then it's body will always be of the
> same size, and relative field positions will be constant. This also
> applicable to objects having only some fields of known size, if these fields
> are on the head positions.
> We can add this information to schema and modify lookup routine as follows:
> 1) Lookup schema
> 2) Get field position by field ID immediately
> 4) Jump to the field
> This will save us from footer lookups thus decreasing overall field lookup
> time. It could be especially important for queries.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Closed] (IGNITE-4481) Creating the scripts
[ https://issues.apache.org/jira/browse/IGNITE-4481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Suntsov closed IGNITE-4481. Fix confirmed > Creating the scripts > > > Key: IGNITE-4481 > URL: https://issues.apache.org/jira/browse/IGNITE-4481 > Project: Ignite > Issue Type: Sub-task >Reporter: Oleg Ostanin >Assignee: Oleg Ostanin > Fix For: 1.9 > > > The goal of this subtask is to resolve this part of original task: > 1. Every deliverable must contain an executable (bat or sh file) with a clear > instruction on how to start a specific benchmark from the console. > 2. For local runs (drivers and servers point out on localhost) ssh connection > must not be used -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-3969) Hadoop: Add installation instructions for MapR to readme.io.
[ https://issues.apache.org/jira/browse/IGNITE-3969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-3969: Fix Version/s: (was: 1.8) 1.9 > Hadoop: Add installation instructions for MapR to readme.io. > > > Key: IGNITE-3969 > URL: https://issues.apache.org/jira/browse/IGNITE-3969 > Project: Ignite > Issue Type: Task > Components: documentation, hadoop >Affects Versions: 1.7 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov > Fix For: 1.9 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-4746) Add documentation for SQL query parallelism
[
https://issues.apache.org/jira/browse/IGNITE-4746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15889797#comment-15889797
]
Vladimir Ozerov commented on IGNITE-4746:
-
Edit is under version {{1.9}}.
> Add documentation for SQL query parallelism
> ---
>
> Key: IGNITE-4746
> URL: https://issues.apache.org/jira/browse/IGNITE-4746
> Project: Ignite
> Issue Type: Task
> Components: documentation, SQL
>Reporter: Vladimir Ozerov
>Assignee: Denis Magda
> Fix For: 1.9
>
>
> See IGNITE-4106.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (IGNITE-4746) Add documentation for SQL query parallelism
[
https://issues.apache.org/jira/browse/IGNITE-4746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov reassigned IGNITE-4746:
---
Assignee: Denis Magda (was: Vladimir Ozerov)
[~dmagda],
See {{SQL Grid}} -> {{Performance and Debugging}} -> {{Query parallelism}}
section.
At the very least please make sure that layout is correct because I have some
problems with {{readme.io}} and cannot setup paragraph properly.
> Add documentation for SQL query parallelism
> ---
>
> Key: IGNITE-4746
> URL: https://issues.apache.org/jira/browse/IGNITE-4746
> Project: Ignite
> Issue Type: Task
> Components: documentation, SQL
>Reporter: Vladimir Ozerov
>Assignee: Denis Magda
> Fix For: 1.9
>
>
> See IGNITE-4106.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-3487) _key and _val fields should be excluded from 'select * from' queries
[
https://issues.apache.org/jira/browse/IGNITE-3487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15889725#comment-15889725
]
Vladimir Ozerov commented on IGNITE-3487:
-
[~skalashnikov],
Could you please re-merge PR with the branch {{ignite-2.0}}, I see some
conflicts there.
> _key and _val fields should be excluded from 'select * from' queries
>
>
> Key: IGNITE-3487
> URL: https://issues.apache.org/jira/browse/IGNITE-3487
> Project: Ignite
> Issue Type: Improvement
> Components: SQL
>Affects Versions: 1.6
>Reporter: Valentin Kulichenko
>Assignee: Sergey Kalashnikov
> Labels: important
> Fix For: 2.0
>
>
> We have a pretty serious usability issue - predefined {{_key}} and {{_val}}
> fields are returned when query like {{select * from}} is executed. First of
> all, this is counterintuitive because user never defines or configures these
> fields. Second of all, they actually duplicate all other fields. And finally,
> they cause serialization exceptions because classes for key and value are not
> always available.
> We should exclude these fields from {{select * from}} queries, but this is a
> compatibility breaking change. It should be done in 2.0.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
