[jira] [Assigned] (IGNITE-2093) Add support for scan near cache to VisorQueryTask
[ https://issues.apache.org/jira/browse/IGNITE-2093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov reassigned IGNITE-2093: -- Assignee: Alexey Kuznetsov (was: Pavel Konstantinov) > Add support for scan near cache to VisorQueryTask > - > > Key: IGNITE-2093 > URL: https://issues.apache.org/jira/browse/IGNITE-2093 > Project: Ignite > Issue Type: Task > Components: cache >Affects Versions: 1.5.0.final >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov >Priority: Major > > VisorQueryTask can execute EXPLAIN, SQL and SCAN queries, but it is not so > hard add support for SCAN NEAR CACHE "pseudo query" that will work on some > node locally and will return > ccache.localEntries(CachePeekMode.NEAR).iterator(). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-2093) Add support for scan near cache to VisorQueryTask
[ https://issues.apache.org/jira/browse/IGNITE-2093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16358039#comment-16358039 ] Pavel Konstantinov commented on IGNITE-2093: Tested on barnch > Add support for scan near cache to VisorQueryTask > - > > Key: IGNITE-2093 > URL: https://issues.apache.org/jira/browse/IGNITE-2093 > Project: Ignite > Issue Type: Task > Components: cache >Affects Versions: 1.5.0.final >Reporter: Alexey Kuznetsov >Assignee: Pavel Konstantinov >Priority: Major > > VisorQueryTask can execute EXPLAIN, SQL and SCAN queries, but it is not so > hard add support for SCAN NEAR CACHE "pseudo query" that will work on some > node locally and will return > ccache.localEntries(CachePeekMode.NEAR).iterator(). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7658) visorcmd: add ability to get configuration of certain cache
[ https://issues.apache.org/jira/browse/IGNITE-7658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov updated IGNITE-7658: --- Fix Version/s: 2.5 > visorcmd: add ability to get configuration of certain cache > --- > > Key: IGNITE-7658 > URL: https://issues.apache.org/jira/browse/IGNITE-7658 > Project: Ignite > Issue Type: Improvement >Reporter: Pavel Konstantinov >Priority: Major > Fix For: 2.5 > > > Currently 'config' command returns only full configuration from a node. > config -id8=@n0 > It is inconvenient in case if a user wants to get the configuration for one > certain cache. > I suggesting to add a new option to 'config' command to set cache, like: > config -id8=@n0 -c=@c0 - get configuration of cache @c0 from node @n0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-7658) visorcmd: add ability to get configuration of certain cache
Pavel Konstantinov created IGNITE-7658: -- Summary: visorcmd: add ability to get configuration of certain cache Key: IGNITE-7658 URL: https://issues.apache.org/jira/browse/IGNITE-7658 Project: Ignite Issue Type: Improvement Reporter: Pavel Konstantinov Currently 'config' command returns only full configuration from a node. config -id8=@n0 It is inconvenient in case if a user wants to get the configuration for one certain cache. I suggesting to add a new option to 'config' command to set cache, like: config -id8=@n0 -c=@c0 - get configuration of cache @c0 from node @n0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7337) Spark Data Frames: support saving a data frame in Ignite
[
https://issues.apache.org/jira/browse/IGNITE-7337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357893#comment-16357893
]
ASF GitHub Bot commented on IGNITE-7337:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3438
> Spark Data Frames: support saving a data frame in Ignite
>
>
> Key: IGNITE-7337
> URL: https://issues.apache.org/jira/browse/IGNITE-7337
> Project: Ignite
> Issue Type: New Feature
> Components: spark
>Affects Versions: 2.3
>Reporter: Valentin Kulichenko
>Assignee: Nikolay Izhikov
>Priority: Major
> Fix For: 2.4
>
>
> Once Ignite data source for Spark is implemented, we need to add an ability
> to store a data frame in Ignite. Most likely if should be enough to provide
> implementation for the following traits:
> * {{InsertableRelation}}
> * {{CreatableRelationProvider}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-7650) Web Console: Rework signin page.
[ https://issues.apache.org/jira/browse/IGNITE-7650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Novikov updated IGNITE-7650: --- Description: * Extract signin/signup form to separated page. * Implement landing page, signin/signup page as components. was: * Add landing screen on signin page * Refactor signin controller to component. > Web Console: Rework signin page. > > > Key: IGNITE-7650 > URL: https://issues.apache.org/jira/browse/IGNITE-7650 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Alexander Kalinin >Assignee: Alexander Kalinin >Priority: Major > Fix For: 2.5 > > > * Extract signin/signup form to separated page. > * Implement landing page, signin/signup page as components. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-7578) Web console: Actualize configuration of ClientConnectorConfiguration
[ https://issues.apache.org/jira/browse/IGNITE-7578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko reassigned IGNITE-7578: - Assignee: Pavel Konstantinov (was: Vasiliy Sisko) > Web console: Actualize configuration of ClientConnectorConfiguration > > > Key: IGNITE-7578 > URL: https://issues.apache.org/jira/browse/IGNITE-7578 > Project: Ignite > Issue Type: Bug >Reporter: Vasiliy Sisko >Assignee: Pavel Konstantinov >Priority: Major > Fix For: 2.5 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7578) Web console: Actualize configuration of ClientConnectorConfiguration
[ https://issues.apache.org/jira/browse/IGNITE-7578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357859#comment-16357859 ] Vasiliy Sisko commented on IGNITE-7578: --- Fixed. Now 'SSL factory' is mandatory when 'Use Ignite SSL' is OFF. > Web console: Actualize configuration of ClientConnectorConfiguration > > > Key: IGNITE-7578 > URL: https://issues.apache.org/jira/browse/IGNITE-7578 > Project: Ignite > Issue Type: Bug >Reporter: Vasiliy Sisko >Assignee: Vasiliy Sisko >Priority: Major > Fix For: 2.5 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7061) Rework Features menu and page
[ https://issues.apache.org/jira/browse/IGNITE-7061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357740#comment-16357740 ] Denis Magda commented on IGNITE-7061: - Don't forget to update the features page [1] and groom the use cases. [1] https://ignite.apache.org/features.html > Rework Features menu and page > - > > Key: IGNITE-7061 > URL: https://issues.apache.org/jira/browse/IGNITE-7061 > Project: Ignite > Issue Type: Task > Components: site >Reporter: Denis Magda >Assignee: Denis Magda >Priority: Major > Fix For: 2.4 > > > The features menu and the page [1] is overloaded and confusing. As a > technical guy, I feel lost trying to grasp what’s important and what’s > secondary. That deters me from digging into the project. > Rework the menu and page in accordance with this discussion: > http://apache-ignite-developers.2346864.n4.nabble.com/Reworking-Ignite-site-s-quot-Features-quot-menu-td24569.html > All the changes are incorporated in this SVN branch: > https://svn.apache.org/repos/asf/ignite/site/branches/ignite-7061 > [1] https://ignite.apache.org/features.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-7060) Prepare Architecture section for the site
[ https://issues.apache.org/jira/browse/IGNITE-7060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda closed IGNITE-7060. --- > Prepare Architecture section for the site > - > > Key: IGNITE-7060 > URL: https://issues.apache.org/jira/browse/IGNITE-7060 > Project: Ignite > Issue Type: Sub-task > Components: site >Reporter: Denis Magda >Assignee: Denis Magda >Priority: Major > Fix For: 2.4 > > > In addition to the features, it's useful to introduce Ignite architecture > right in the Features menu covering the following: > * Overview > * Clustering and Deployment > * Distributed Database > * Durable Memory -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-7060) Prepare Architecture section for the site
[ https://issues.apache.org/jira/browse/IGNITE-7060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda resolved IGNITE-7060. - Resolution: Fixed > Prepare Architecture section for the site > - > > Key: IGNITE-7060 > URL: https://issues.apache.org/jira/browse/IGNITE-7060 > Project: Ignite > Issue Type: Sub-task > Components: site >Reporter: Denis Magda >Assignee: Denis Magda >Priority: Major > Fix For: 2.4 > > > In addition to the features, it's useful to introduce Ignite architecture > right in the Features menu covering the following: > * Overview > * Clustering and Deployment > * Distributed Database > * Durable Memory -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7060) Prepare Architecture section for the site
[ https://issues.apache.org/jira/browse/IGNITE-7060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357739#comment-16357739 ] Denis Magda commented on IGNITE-7060: - Introduced the architecture section by adding the following page: * Clustering and Deployment * Memory-Centric Storage * Durable Memory * Persistence This should be enough for now. More pages can be added in the future. > Prepare Architecture section for the site > - > > Key: IGNITE-7060 > URL: https://issues.apache.org/jira/browse/IGNITE-7060 > Project: Ignite > Issue Type: Sub-task > Components: site >Reporter: Denis Magda >Assignee: Denis Magda >Priority: Major > Fix For: 2.4 > > > In addition to the features, it's useful to introduce Ignite architecture > right in the Features menu covering the following: > * Overview > * Clustering and Deployment > * Distributed Database > * Durable Memory -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-7060) Prepare Architecture section for the site
[ https://issues.apache.org/jira/browse/IGNITE-7060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda reassigned IGNITE-7060: --- Assignee: Denis Magda > Prepare Architecture section for the site > - > > Key: IGNITE-7060 > URL: https://issues.apache.org/jira/browse/IGNITE-7060 > Project: Ignite > Issue Type: Sub-task > Components: site >Reporter: Denis Magda >Assignee: Denis Magda >Priority: Major > Fix For: 2.4 > > > In addition to the features, it's useful to introduce Ignite architecture > right in the Features menu covering the following: > * Overview > * Clustering and Deployment > * Distributed Database > * Durable Memory -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7657) SQL COPY: minor style fixes
[ https://issues.apache.org/jira/browse/IGNITE-7657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357703#comment-16357703 ] ASF GitHub Bot commented on IGNITE-7657: GitHub user gg-shq opened a pull request: https://github.com/apache/ignite/pull/3496 IGNITE-7657: Minor style fixes: imports, forgotten javadocs, annotations …ons. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7657 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/3496.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 #3496 commit a8252aa0590913fcbb812c0e0d66213e1a56a743 Author: shq Date: 2018-02-08T23:18:47Z IGNITE-7657: Minor style fixes: imports, forgotten javadocs, annotations. > SQL COPY: minor style fixes > --- > > Key: IGNITE-7657 > URL: https://issues.apache.org/jira/browse/IGNITE-7657 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.4 >Reporter: Kirill Shirokov >Assignee: Kirill Shirokov >Priority: Minor > > This issue is for fixing minor style issues in a separate branch in order to > avoid spoiling other COPY-related pull requests with minor refactorings. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7193) IgniteReflectionFactory does not handle primitive data types.
[
https://issues.apache.org/jira/browse/IGNITE-7193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-7193:
Component/s: general
> IgniteReflectionFactory does not handle primitive data types.
> -
>
> Key: IGNITE-7193
> URL: https://issues.apache.org/jira/browse/IGNITE-7193
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.1
>Reporter: Vyacheslav Koptilin
>Assignee: Vyacheslav Koptilin
>Priority: Minor
> Fix For: 2.5
>
>
> {code:java}
> public class TestClass {
> public static final int INITIAL_VALUE = 12;
> public static final int UPDATED_VALUE = 42;
> private int field = INITIAL_VALUE;
> public void setField(int value) {
> this.field = value;
> }
> public int getField() {
> return this.field;
> }
> public static void main(String[] args) {
> Map props = new HashMap<>();
> props.put("field", UPDATED_VALUE);
> IgniteReflectionFactory factory = new
> IgniteReflectionFactory<>(ExampleNodeStartup.TestClass.class);
> factory.setProperties(props);
> assertEquals(UPDATED_VALUE, factory.create().getField());
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-7193) IgniteReflectionFactory does not handle primitive data types.
[
https://issues.apache.org/jira/browse/IGNITE-7193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-7193:
Fix Version/s: 2.5
> IgniteReflectionFactory does not handle primitive data types.
> -
>
> Key: IGNITE-7193
> URL: https://issues.apache.org/jira/browse/IGNITE-7193
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.1
>Reporter: Vyacheslav Koptilin
>Assignee: Vyacheslav Koptilin
>Priority: Minor
> Fix For: 2.5
>
>
> {code:java}
> public class TestClass {
> public static final int INITIAL_VALUE = 12;
> public static final int UPDATED_VALUE = 42;
> private int field = INITIAL_VALUE;
> public void setField(int value) {
> this.field = value;
> }
> public int getField() {
> return this.field;
> }
> public static void main(String[] args) {
> Map props = new HashMap<>();
> props.put("field", UPDATED_VALUE);
> IgniteReflectionFactory factory = new
> IgniteReflectionFactory<>(ExampleNodeStartup.TestClass.class);
> factory.setProperties(props);
> assertEquals(UPDATED_VALUE, factory.create().getField());
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7656) Can't query a created cache
[
https://issues.apache.org/jira/browse/IGNITE-7656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357673#comment-16357673
]
Valentin Kulichenko commented on IGNITE-7656:
-
Cache name becomes schema name, type name becomes table name. I would recommend
you to go through docs and examples to see how it works in Ignite, and then go
to user forum is anything is not working as expected. Community members would
be happy to help.
> Can't query a created cache
> ---
>
> Key: IGNITE-7656
> URL: https://issues.apache.org/jira/browse/IGNITE-7656
> Project: Ignite
> Issue Type: Bug
>Reporter: Mike Williams
>Priority: Major
>
> I have here a dead simple example that should work - here's a definition of a
> data object ( a Cat):
> {{{color:#cc7832}import
> {color}org.apache.ignite.cache.query.annotations.*{color:#cc7832};
> {color}{color:#cc7832}import {color}java.io.*{color:#cc7832};
> {color}{color:#cc7832}public class {color}Cat {color:#cc7832}implements
> {color}Serializable {}}
> {{ {color:#bbb529}@QuerySqlField
> {color} {color:#cc7832}int {color}{color:#9876aa}legs{color}{color:#cc7832};
> {color} {color:#bbb529}@QuerySqlField
> {color} String {color:#9876aa}name{color}{color:#cc7832};
> {color}{color:#cc7832}
> {color} {color:#ffc66d}Cat{color}({color:#cc7832}int {color}l{color:#cc7832},
> {color}String n)}}
> {{ {}}
> {{ {color:#9876aa}legs {color}= l{color:#cc7832};
> {color} {color:#9876aa}name {color}= n{color:#cc7832};
> {color} }}}
> {{}}}
>
> And when I run the following, I want to get a list of cats:
> {color:#cc7832}import {color}org.apache.ignite.Ignition{color:#cc7832};
> {color}{color:#cc7832}import {color}org.apache.ignite.Ignite{color:#cc7832};
> {color}{color:#cc7832}import
> {color}org.apache.ignite.IgniteCache{color:#cc7832};
> {color}{color:#cc7832}import
> {color}org.apache.ignite.configuration.CacheConfiguration{color:#cc7832};
> {color}{color:#cc7832}import
> {color}org.apache.ignite.cache.query.SqlFieldsQuery{color:#cc7832};
> {color}{color:#cc7832}import
> {color}org.apache.ignite.cache.query.QueryCursor{color:#cc7832};
> {color}{color:#cc7832}import {color}java.util.List{color:#cc7832};
> {color}{color:#cc7832}public class {color}Test {
> {color:#cc7832}public static void {color}{color:#ffc66d}main{color}(String[]
> args)
> {
> {color:#808080}//Ignition.setClientMode(true);
> {color} Ignite ignite = Ignition.start(){color:#cc7832};
> {color} CacheConfiguration cfg=
> {color:#cc7832}new
> {color}CacheConfiguration({color:#6a8759}"catCache"{color}){color:#cc7832};
> {color}
> cfg.setIndexedTypes(Integer.{color:#cc7832}class,{color}Integer.{color:#cc7832}class{color}){color:#cc7832};
> {color}{color:#cc7832} try{color}(IgniteCache {color}Cat> cache = ignite.getOrCreateCache(cfg))
> {
> {color:#cc7832}for {color}({color:#cc7832}int {color}i =
> {color:#6897bb}0{color}{color:#cc7832}; {color}i <
> {color:#6897bb}10{color}{color:#cc7832}; {color}++i) {
> cache.put(i{color:#cc7832}, new {color}Cat(i +
> {color:#6897bb}1{color}{color:#cc7832},{color}{color:#6a8759}"Fluffy"{color})){color:#cc7832};
> {color} }
> SqlFieldsQuery sql = {color:#cc7832}new
> {color}SqlFieldsQuery({color:#6a8759}"select * from
> catCache"{color}){color:#cc7832};
> {color}{color:#cc7832} try {color}(QueryCursor> cursor =
> cache.query(sql)) {
> {color:#cc7832}for {color}(List row : cursor)
> System.{color:#9876aa}out{color}.println({color:#6a8759}"cat=" {color}+
> row.get({color:#6897bb}0{color})){color:#cc7832};
> {color} }
> }{color:#cc7832}
> {color}}}
>
> However, I get only an error. Something seems strange in the way the cache is
> set up in H2 - the schema is catCatche, and the name is INTEGER. The names of
> the data fields don't look right either - here's the whole DDL:
> CREATE MEMORY TABLE "catCache".INTEGER(
> _KEY INT NOT NULL,
> _VAL INT,
> _VER OTHER INVISIBLE
> )
> ENGINE "org.apache.ignite.internal.processors.query.h2.H2TableEngine"
> What am I doing wrong?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-7657) SQL COPY: minor style fixes
[ https://issues.apache.org/jira/browse/IGNITE-7657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Shirokov updated IGNITE-7657: Description: This issue is for fixing minor style issues in a separate branch in order to avoid spoiling other COPY-related pull requests with minor refactorings. > SQL COPY: minor style fixes > --- > > Key: IGNITE-7657 > URL: https://issues.apache.org/jira/browse/IGNITE-7657 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.4 >Reporter: Kirill Shirokov >Assignee: Kirill Shirokov >Priority: Minor > > This issue is for fixing minor style issues in a separate branch in order to > avoid spoiling other COPY-related pull requests with minor refactorings. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-7657) SQL COPY: minor style fixes
Kirill Shirokov created IGNITE-7657: --- Summary: SQL COPY: minor style fixes Key: IGNITE-7657 URL: https://issues.apache.org/jira/browse/IGNITE-7657 Project: Ignite Issue Type: Bug Components: sql Affects Versions: 2.4 Reporter: Kirill Shirokov Assignee: Kirill Shirokov -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7656) Can't query a created cache
[
https://issues.apache.org/jira/browse/IGNITE-7656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357663#comment-16357663
]
Mike Williams commented on IGNITE-7656:
---
Better but name is still funky:
CREATE MEMORY TABLE "catCache".CAT(
_KEY INT INVISIBLE NOT NULL,
_VAL OTHER INVISIBLE ,
_VER OTHER INVISIBLE ,
LEGS INT,
NAME VARCHAR
)
ENGINE "org.apache.ignite.internal.processors.query.h2.H2TableEngine"
How do I make the name just catCache?
> Can't query a created cache
> ---
>
> Key: IGNITE-7656
> URL: https://issues.apache.org/jira/browse/IGNITE-7656
> Project: Ignite
> Issue Type: Bug
>Reporter: Mike Williams
>Priority: Major
>
> I have here a dead simple example that should work - here's a definition of a
> data object ( a Cat):
> {{{color:#cc7832}import
> {color}org.apache.ignite.cache.query.annotations.*{color:#cc7832};
> {color}{color:#cc7832}import {color}java.io.*{color:#cc7832};
> {color}{color:#cc7832}public class {color}Cat {color:#cc7832}implements
> {color}Serializable {}}
> {{ {color:#bbb529}@QuerySqlField
> {color} {color:#cc7832}int {color}{color:#9876aa}legs{color}{color:#cc7832};
> {color} {color:#bbb529}@QuerySqlField
> {color} String {color:#9876aa}name{color}{color:#cc7832};
> {color}{color:#cc7832}
> {color} {color:#ffc66d}Cat{color}({color:#cc7832}int {color}l{color:#cc7832},
> {color}String n)}}
> {{ {}}
> {{ {color:#9876aa}legs {color}= l{color:#cc7832};
> {color} {color:#9876aa}name {color}= n{color:#cc7832};
> {color} }}}
> {{}}}
>
> And when I run the following, I want to get a list of cats:
> {color:#cc7832}import {color}org.apache.ignite.Ignition{color:#cc7832};
> {color}{color:#cc7832}import {color}org.apache.ignite.Ignite{color:#cc7832};
> {color}{color:#cc7832}import
> {color}org.apache.ignite.IgniteCache{color:#cc7832};
> {color}{color:#cc7832}import
> {color}org.apache.ignite.configuration.CacheConfiguration{color:#cc7832};
> {color}{color:#cc7832}import
> {color}org.apache.ignite.cache.query.SqlFieldsQuery{color:#cc7832};
> {color}{color:#cc7832}import
> {color}org.apache.ignite.cache.query.QueryCursor{color:#cc7832};
> {color}{color:#cc7832}import {color}java.util.List{color:#cc7832};
> {color}{color:#cc7832}public class {color}Test {
> {color:#cc7832}public static void {color}{color:#ffc66d}main{color}(String[]
> args)
> {
> {color:#808080}//Ignition.setClientMode(true);
> {color} Ignite ignite = Ignition.start(){color:#cc7832};
> {color} CacheConfiguration cfg=
> {color:#cc7832}new
> {color}CacheConfiguration({color:#6a8759}"catCache"{color}){color:#cc7832};
> {color}
> cfg.setIndexedTypes(Integer.{color:#cc7832}class,{color}Integer.{color:#cc7832}class{color}){color:#cc7832};
> {color}{color:#cc7832} try{color}(IgniteCache {color}Cat> cache = ignite.getOrCreateCache(cfg))
> {
> {color:#cc7832}for {color}({color:#cc7832}int {color}i =
> {color:#6897bb}0{color}{color:#cc7832}; {color}i <
> {color:#6897bb}10{color}{color:#cc7832}; {color}++i) {
> cache.put(i{color:#cc7832}, new {color}Cat(i +
> {color:#6897bb}1{color}{color:#cc7832},{color}{color:#6a8759}"Fluffy"{color})){color:#cc7832};
> {color} }
> SqlFieldsQuery sql = {color:#cc7832}new
> {color}SqlFieldsQuery({color:#6a8759}"select * from
> catCache"{color}){color:#cc7832};
> {color}{color:#cc7832} try {color}(QueryCursor> cursor =
> cache.query(sql)) {
> {color:#cc7832}for {color}(List row : cursor)
> System.{color:#9876aa}out{color}.println({color:#6a8759}"cat=" {color}+
> row.get({color:#6897bb}0{color})){color:#cc7832};
> {color} }
> }{color:#cc7832}
> {color}}}
>
> However, I get only an error. Something seems strange in the way the cache is
> set up in H2 - the schema is catCatche, and the name is INTEGER. The names of
> the data fields don't look right either - here's the whole DDL:
> CREATE MEMORY TABLE "catCache".INTEGER(
> _KEY INT NOT NULL,
> _VAL INT,
> _VER OTHER INVISIBLE
> )
> ENGINE "org.apache.ignite.internal.processors.query.h2.H2TableEngine"
> What am I doing wrong?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (IGNITE-7464) Add property to configure time between node connection attempts
[ https://issues.apache.org/jira/browse/IGNITE-7464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko closed IGNITE-7464. --- > Add property to configure time between node connection attempts > --- > > Key: IGNITE-7464 > URL: https://issues.apache.org/jira/browse/IGNITE-7464 > Project: Ignite > Issue Type: Bug >Reporter: Stanislav Lukyanov >Assignee: Stanislav Lukyanov >Priority: Major > Fix For: 2.4 > > > Currently when a node attempts to join the cluster, the connection algorithm > will be repeated until successful or timed out. The time between the attempts > is hardcoded - 2 seconds. > It might be useful to adjust that time via a property (say, in SPI config) > based on the network quality, application constraints, etc. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7464) Add property to configure time between node connection attempts
[ https://issues.apache.org/jira/browse/IGNITE-7464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-7464: Fix Version/s: 2.4 > Add property to configure time between node connection attempts > --- > > Key: IGNITE-7464 > URL: https://issues.apache.org/jira/browse/IGNITE-7464 > Project: Ignite > Issue Type: Bug >Reporter: Stanislav Lukyanov >Assignee: Stanislav Lukyanov >Priority: Major > Fix For: 2.4 > > > Currently when a node attempts to join the cluster, the connection algorithm > will be repeated until successful or timed out. The time between the attempts > is hardcoded - 2 seconds. > It might be useful to adjust that time via a property (say, in SPI config) > based on the network quality, application constraints, etc. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-7656) Can't query a created cache
[
https://issues.apache.org/jira/browse/IGNITE-7656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko closed IGNITE-7656.
---
> Can't query a created cache
> ---
>
> Key: IGNITE-7656
> URL: https://issues.apache.org/jira/browse/IGNITE-7656
> Project: Ignite
> Issue Type: Bug
>Reporter: Mike Williams
>Priority: Major
>
> I have here a dead simple example that should work - here's a definition of a
> data object ( a Cat):
> {{{color:#cc7832}import
> {color}org.apache.ignite.cache.query.annotations.*{color:#cc7832};
> {color}{color:#cc7832}import {color}java.io.*{color:#cc7832};
> {color}{color:#cc7832}public class {color}Cat {color:#cc7832}implements
> {color}Serializable {}}
> {{ {color:#bbb529}@QuerySqlField
> {color} {color:#cc7832}int {color}{color:#9876aa}legs{color}{color:#cc7832};
> {color} {color:#bbb529}@QuerySqlField
> {color} String {color:#9876aa}name{color}{color:#cc7832};
> {color}{color:#cc7832}
> {color} {color:#ffc66d}Cat{color}({color:#cc7832}int {color}l{color:#cc7832},
> {color}String n)}}
> {{ {}}
> {{ {color:#9876aa}legs {color}= l{color:#cc7832};
> {color} {color:#9876aa}name {color}= n{color:#cc7832};
> {color} }}}
> {{}}}
>
> And when I run the following, I want to get a list of cats:
> {color:#cc7832}import {color}org.apache.ignite.Ignition{color:#cc7832};
> {color}{color:#cc7832}import {color}org.apache.ignite.Ignite{color:#cc7832};
> {color}{color:#cc7832}import
> {color}org.apache.ignite.IgniteCache{color:#cc7832};
> {color}{color:#cc7832}import
> {color}org.apache.ignite.configuration.CacheConfiguration{color:#cc7832};
> {color}{color:#cc7832}import
> {color}org.apache.ignite.cache.query.SqlFieldsQuery{color:#cc7832};
> {color}{color:#cc7832}import
> {color}org.apache.ignite.cache.query.QueryCursor{color:#cc7832};
> {color}{color:#cc7832}import {color}java.util.List{color:#cc7832};
> {color}{color:#cc7832}public class {color}Test {
> {color:#cc7832}public static void {color}{color:#ffc66d}main{color}(String[]
> args)
> {
> {color:#808080}//Ignition.setClientMode(true);
> {color} Ignite ignite = Ignition.start(){color:#cc7832};
> {color} CacheConfiguration cfg=
> {color:#cc7832}new
> {color}CacheConfiguration({color:#6a8759}"catCache"{color}){color:#cc7832};
> {color}
> cfg.setIndexedTypes(Integer.{color:#cc7832}class,{color}Integer.{color:#cc7832}class{color}){color:#cc7832};
> {color}{color:#cc7832} try{color}(IgniteCache {color}Cat> cache = ignite.getOrCreateCache(cfg))
> {
> {color:#cc7832}for {color}({color:#cc7832}int {color}i =
> {color:#6897bb}0{color}{color:#cc7832}; {color}i <
> {color:#6897bb}10{color}{color:#cc7832}; {color}++i) {
> cache.put(i{color:#cc7832}, new {color}Cat(i +
> {color:#6897bb}1{color}{color:#cc7832},{color}{color:#6a8759}"Fluffy"{color})){color:#cc7832};
> {color} }
> SqlFieldsQuery sql = {color:#cc7832}new
> {color}SqlFieldsQuery({color:#6a8759}"select * from
> catCache"{color}){color:#cc7832};
> {color}{color:#cc7832} try {color}(QueryCursor> cursor =
> cache.query(sql)) {
> {color:#cc7832}for {color}(List row : cursor)
> System.{color:#9876aa}out{color}.println({color:#6a8759}"cat=" {color}+
> row.get({color:#6897bb}0{color})){color:#cc7832};
> {color} }
> }{color:#cc7832}
> {color}}}
>
> However, I get only an error. Something seems strange in the way the cache is
> set up in H2 - the schema is catCatche, and the name is INTEGER. The names of
> the data fields don't look right either - here's the whole DDL:
> CREATE MEMORY TABLE "catCache".INTEGER(
> _KEY INT NOT NULL,
> _VAL INT,
> _VER OTHER INVISIBLE
> )
> ENGINE "org.apache.ignite.internal.processors.query.h2.H2TableEngine"
> What am I doing wrong?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IGNITE-7656) Can't query a created cache
[
https://issues.apache.org/jira/browse/IGNITE-7656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko resolved IGNITE-7656.
-
Resolution: Not A Problem
> Can't query a created cache
> ---
>
> Key: IGNITE-7656
> URL: https://issues.apache.org/jira/browse/IGNITE-7656
> Project: Ignite
> Issue Type: Bug
>Reporter: Mike Williams
>Priority: Major
>
> I have here a dead simple example that should work - here's a definition of a
> data object ( a Cat):
> {{{color:#cc7832}import
> {color}org.apache.ignite.cache.query.annotations.*{color:#cc7832};
> {color}{color:#cc7832}import {color}java.io.*{color:#cc7832};
> {color}{color:#cc7832}public class {color}Cat {color:#cc7832}implements
> {color}Serializable {}}
> {{ {color:#bbb529}@QuerySqlField
> {color} {color:#cc7832}int {color}{color:#9876aa}legs{color}{color:#cc7832};
> {color} {color:#bbb529}@QuerySqlField
> {color} String {color:#9876aa}name{color}{color:#cc7832};
> {color}{color:#cc7832}
> {color} {color:#ffc66d}Cat{color}({color:#cc7832}int {color}l{color:#cc7832},
> {color}String n)}}
> {{ {}}
> {{ {color:#9876aa}legs {color}= l{color:#cc7832};
> {color} {color:#9876aa}name {color}= n{color:#cc7832};
> {color} }}}
> {{}}}
>
> And when I run the following, I want to get a list of cats:
> {color:#cc7832}import {color}org.apache.ignite.Ignition{color:#cc7832};
> {color}{color:#cc7832}import {color}org.apache.ignite.Ignite{color:#cc7832};
> {color}{color:#cc7832}import
> {color}org.apache.ignite.IgniteCache{color:#cc7832};
> {color}{color:#cc7832}import
> {color}org.apache.ignite.configuration.CacheConfiguration{color:#cc7832};
> {color}{color:#cc7832}import
> {color}org.apache.ignite.cache.query.SqlFieldsQuery{color:#cc7832};
> {color}{color:#cc7832}import
> {color}org.apache.ignite.cache.query.QueryCursor{color:#cc7832};
> {color}{color:#cc7832}import {color}java.util.List{color:#cc7832};
> {color}{color:#cc7832}public class {color}Test {
> {color:#cc7832}public static void {color}{color:#ffc66d}main{color}(String[]
> args)
> {
> {color:#808080}//Ignition.setClientMode(true);
> {color} Ignite ignite = Ignition.start(){color:#cc7832};
> {color} CacheConfiguration cfg=
> {color:#cc7832}new
> {color}CacheConfiguration({color:#6a8759}"catCache"{color}){color:#cc7832};
> {color}
> cfg.setIndexedTypes(Integer.{color:#cc7832}class,{color}Integer.{color:#cc7832}class{color}){color:#cc7832};
> {color}{color:#cc7832} try{color}(IgniteCache {color}Cat> cache = ignite.getOrCreateCache(cfg))
> {
> {color:#cc7832}for {color}({color:#cc7832}int {color}i =
> {color:#6897bb}0{color}{color:#cc7832}; {color}i <
> {color:#6897bb}10{color}{color:#cc7832}; {color}++i) {
> cache.put(i{color:#cc7832}, new {color}Cat(i +
> {color:#6897bb}1{color}{color:#cc7832},{color}{color:#6a8759}"Fluffy"{color})){color:#cc7832};
> {color} }
> SqlFieldsQuery sql = {color:#cc7832}new
> {color}SqlFieldsQuery({color:#6a8759}"select * from
> catCache"{color}){color:#cc7832};
> {color}{color:#cc7832} try {color}(QueryCursor> cursor =
> cache.query(sql)) {
> {color:#cc7832}for {color}(List row : cursor)
> System.{color:#9876aa}out{color}.println({color:#6a8759}"cat=" {color}+
> row.get({color:#6897bb}0{color})){color:#cc7832};
> {color} }
> }{color:#cc7832}
> {color}}}
>
> However, I get only an error. Something seems strange in the way the cache is
> set up in H2 - the schema is catCatche, and the name is INTEGER. The names of
> the data fields don't look right either - here's the whole DDL:
> CREATE MEMORY TABLE "catCache".INTEGER(
> _KEY INT NOT NULL,
> _VAL INT,
> _VER OTHER INVISIBLE
> )
> ENGINE "org.apache.ignite.internal.processors.query.h2.H2TableEngine"
> What am I doing wrong?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7656) Can't query a created cache
[
https://issues.apache.org/jira/browse/IGNITE-7656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357648#comment-16357648
]
Valentin Kulichenko commented on IGNITE-7656:
-
[~MDW], table is created this way because you specified {{Integer}} as value
class for indexing: {{cfg.setIndexedTypes(Integer.class,Integer.class);}}.
Change it to {{Cat}} and it should work.
Also please report such problems on user forum instead:
[https://ignite.apache.org/community/resources.html#mail-lists.] Use Jira only
for actual bugs, improvements or features.
> Can't query a created cache
> ---
>
> Key: IGNITE-7656
> URL: https://issues.apache.org/jira/browse/IGNITE-7656
> Project: Ignite
> Issue Type: Bug
>Reporter: Mike Williams
>Priority: Major
>
> I have here a dead simple example that should work - here's a definition of a
> data object ( a Cat):
> {{{color:#cc7832}import
> {color}org.apache.ignite.cache.query.annotations.*{color:#cc7832};
> {color}{color:#cc7832}import {color}java.io.*{color:#cc7832};
> {color}{color:#cc7832}public class {color}Cat {color:#cc7832}implements
> {color}Serializable {}}
> {{ {color:#bbb529}@QuerySqlField
> {color} {color:#cc7832}int {color}{color:#9876aa}legs{color}{color:#cc7832};
> {color} {color:#bbb529}@QuerySqlField
> {color} String {color:#9876aa}name{color}{color:#cc7832};
> {color}{color:#cc7832}
> {color} {color:#ffc66d}Cat{color}({color:#cc7832}int {color}l{color:#cc7832},
> {color}String n)}}
> {{ {}}
> {{ {color:#9876aa}legs {color}= l{color:#cc7832};
> {color} {color:#9876aa}name {color}= n{color:#cc7832};
> {color} }}}
> {{}}}
>
> And when I run the following, I want to get a list of cats:
> {color:#cc7832}import {color}org.apache.ignite.Ignition{color:#cc7832};
> {color}{color:#cc7832}import {color}org.apache.ignite.Ignite{color:#cc7832};
> {color}{color:#cc7832}import
> {color}org.apache.ignite.IgniteCache{color:#cc7832};
> {color}{color:#cc7832}import
> {color}org.apache.ignite.configuration.CacheConfiguration{color:#cc7832};
> {color}{color:#cc7832}import
> {color}org.apache.ignite.cache.query.SqlFieldsQuery{color:#cc7832};
> {color}{color:#cc7832}import
> {color}org.apache.ignite.cache.query.QueryCursor{color:#cc7832};
> {color}{color:#cc7832}import {color}java.util.List{color:#cc7832};
> {color}{color:#cc7832}public class {color}Test {
> {color:#cc7832}public static void {color}{color:#ffc66d}main{color}(String[]
> args)
> {
> {color:#808080}//Ignition.setClientMode(true);
> {color} Ignite ignite = Ignition.start(){color:#cc7832};
> {color} CacheConfiguration cfg=
> {color:#cc7832}new
> {color}CacheConfiguration({color:#6a8759}"catCache"{color}){color:#cc7832};
> {color}
> cfg.setIndexedTypes(Integer.{color:#cc7832}class,{color}Integer.{color:#cc7832}class{color}){color:#cc7832};
> {color}{color:#cc7832} try{color}(IgniteCache {color}Cat> cache = ignite.getOrCreateCache(cfg))
> {
> {color:#cc7832}for {color}({color:#cc7832}int {color}i =
> {color:#6897bb}0{color}{color:#cc7832}; {color}i <
> {color:#6897bb}10{color}{color:#cc7832}; {color}++i) {
> cache.put(i{color:#cc7832}, new {color}Cat(i +
> {color:#6897bb}1{color}{color:#cc7832},{color}{color:#6a8759}"Fluffy"{color})){color:#cc7832};
> {color} }
> SqlFieldsQuery sql = {color:#cc7832}new
> {color}SqlFieldsQuery({color:#6a8759}"select * from
> catCache"{color}){color:#cc7832};
> {color}{color:#cc7832} try {color}(QueryCursor> cursor =
> cache.query(sql)) {
> {color:#cc7832}for {color}(List row : cursor)
> System.{color:#9876aa}out{color}.println({color:#6a8759}"cat=" {color}+
> row.get({color:#6897bb}0{color})){color:#cc7832};
> {color} }
> }{color:#cc7832}
> {color}}}
>
> However, I get only an error. Something seems strange in the way the cache is
> set up in H2 - the schema is catCatche, and the name is INTEGER. The names of
> the data fields don't look right either - here's the whole DDL:
> CREATE MEMORY TABLE "catCache".INTEGER(
> _KEY INT NOT NULL,
> _VAL INT,
> _VER OTHER INVISIBLE
> )
> ENGINE "org.apache.ignite.internal.processors.query.h2.H2TableEngine"
> What am I doing wrong?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-7656) Can't query a created cache
[
https://issues.apache.org/jira/browse/IGNITE-7656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Williams updated IGNITE-7656:
--
Description:
I have here a dead simple example that should work - here's a definition of a
data object ( a Cat):
{{{color:#cc7832}import
{color}org.apache.ignite.cache.query.annotations.*{color:#cc7832};
{color}{color:#cc7832}import {color}java.io.*{color:#cc7832};
{color}{color:#cc7832}public class {color}Cat {color:#cc7832}implements
{color}Serializable {}}
{{ {color:#bbb529}@QuerySqlField
{color} {color:#cc7832}int {color}{color:#9876aa}legs{color}{color:#cc7832};
{color} {color:#bbb529}@QuerySqlField
{color} String {color:#9876aa}name{color}{color:#cc7832};
{color}{color:#cc7832}
{color} {color:#ffc66d}Cat{color}({color:#cc7832}int {color}l{color:#cc7832},
{color}String n)}}
{{ {}}
{{ {color:#9876aa}legs {color}= l{color:#cc7832};
{color} {color:#9876aa}name {color}= n{color:#cc7832};
{color} }}}
{{}}}
And when I run the following, I want to get a list of cats:
{color:#cc7832}import {color}org.apache.ignite.Ignition{color:#cc7832};
{color}{color:#cc7832}import {color}org.apache.ignite.Ignite{color:#cc7832};
{color}{color:#cc7832}import
{color}org.apache.ignite.IgniteCache{color:#cc7832};
{color}{color:#cc7832}import
{color}org.apache.ignite.configuration.CacheConfiguration{color:#cc7832};
{color}{color:#cc7832}import
{color}org.apache.ignite.cache.query.SqlFieldsQuery{color:#cc7832};
{color}{color:#cc7832}import
{color}org.apache.ignite.cache.query.QueryCursor{color:#cc7832};
{color}{color:#cc7832}import {color}java.util.List{color:#cc7832};
{color}{color:#cc7832}public class {color}Test {
{color:#cc7832}public static void {color}{color:#ffc66d}main{color}(String[]
args)
{
{color:#808080}//Ignition.setClientMode(true);
{color} Ignite ignite = Ignition.start(){color:#cc7832};
{color} CacheConfiguration cfg=
{color:#cc7832}new
{color}CacheConfiguration({color:#6a8759}"catCache"{color}){color:#cc7832};
{color}
cfg.setIndexedTypes(Integer.{color:#cc7832}class,{color}Integer.{color:#cc7832}class{color}){color:#cc7832};
{color}{color:#cc7832} try{color}(IgniteCache cache = ignite.getOrCreateCache(cfg))
{
{color:#cc7832}for {color}({color:#cc7832}int {color}i =
{color:#6897bb}0{color}{color:#cc7832}; {color}i <
{color:#6897bb}10{color}{color:#cc7832}; {color}++i) {
cache.put(i{color:#cc7832}, new {color}Cat(i +
{color:#6897bb}1{color}{color:#cc7832},{color}{color:#6a8759}"Fluffy"{color})){color:#cc7832};
{color} }
SqlFieldsQuery sql = {color:#cc7832}new
{color}SqlFieldsQuery({color:#6a8759}"select * from
catCache"{color}){color:#cc7832};
{color}{color:#cc7832} try {color}(QueryCursor> cursor =
cache.query(sql)) {
{color:#cc7832}for {color}(List row : cursor)
System.{color:#9876aa}out{color}.println({color:#6a8759}"cat=" {color}+
row.get({color:#6897bb}0{color})){color:#cc7832};
{color} }
}{color:#cc7832}
{color}}}
However, I get only an error. Something seems strange in the way the cache is
set up in H2 - the schema is catCatche, and the name is INTEGER. The names of
the data fields don't look right either - here's the whole DDL:
CREATE MEMORY TABLE "catCache".INTEGER(
_KEY INT NOT NULL,
_VAL INT,
_VER OTHER INVISIBLE
)
ENGINE "org.apache.ignite.internal.processors.query.h2.H2TableEngine"
What am I doing wrong?
> Can't query a created cache
> ---
>
> Key: IGNITE-7656
> URL: https://issues.apache.org/jira/browse/IGNITE-7656
> Project: Ignite
> Issue Type: Bug
>Reporter: Mike Williams
>Priority: Major
>
> I have here a dead simple example that should work - here's a definition of a
> data object ( a Cat):
> {{{color:#cc7832}import
> {color}org.apache.ignite.cache.query.annotations.*{color:#cc7832};
> {color}{color:#cc7832}import {color}java.io.*{color:#cc7832};
> {color}{color:#cc7832}public class {color}Cat {color:#cc7832}implements
> {color}Serializable {}}
> {{ {color:#bbb529}@QuerySqlField
> {color} {color:#cc7832}int {color}{color:#9876aa}legs{color}{color:#cc7832};
> {color} {color:#bbb529}@QuerySqlField
> {color} String {color:#9876aa}name{color}{color:#cc7832};
> {color}{color:#cc7832}
> {color} {color:#ffc66d}Cat{color}({color:#cc7832}int {color}l{color:#cc7832},
> {color}String n)}}
> {{ {}}
> {{ {color:#9876aa}legs {color}= l{color:#cc7832};
> {color} {color:#9876aa}name {color}= n{color:#cc7832};
> {color} }}}
> {{}}}
>
> And when I run the following, I want to get a list of cats:
> {color:#cc7832}import {color}org.apache.ignite.Ignition{color:#cc7832};
> {color}{color:#cc7832}import {color}org.apache.ignite.Ignite{color:#cc7832};
> {color}{color:#cc7832}import
> {color}org.apache.ignite.IgniteCache{color:#cc7832};
> {color}{color:#cc7832}import
> {color}org.apache.ignite.configuration.CacheConfiguration{color:#cc7832};
> {color}{co
[jira] [Created] (IGNITE-7656) Can't query a created cache
Mike Williams created IGNITE-7656: - Summary: Can't query a created cache Key: IGNITE-7656 URL: https://issues.apache.org/jira/browse/IGNITE-7656 Project: Ignite Issue Type: Bug Reporter: Mike Williams -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7059) Improve Collocated Processing page on the site
[ https://issues.apache.org/jira/browse/IGNITE-7059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357627#comment-16357627 ] Denis Magda commented on IGNITE-7059: - The page is reworked. Now it includes separate sections for the topics mentioned in the description: http://localhost:8080/collocatedprocessing.html > Improve Collocated Processing page on the site > -- > > Key: IGNITE-7059 > URL: https://issues.apache.org/jira/browse/IGNITE-7059 > Project: Ignite > Issue Type: Sub-task > Components: site >Reporter: Denis Magda >Assignee: Denis Magda >Priority: Major > Fix For: 2.4 > > > Presently the collocated processing [1] covers general aspects of this > paradigm. Elaborate more on the following: > * How it's related to SQL > * How it's related to compute grid and ML > * As for compute grid, mention that it allows broadcast or run computations > on concrete nodes as well. > [1] https://ignite.apache.org/collocatedprocessing.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-7059) Improve Collocated Processing page on the site
[ https://issues.apache.org/jira/browse/IGNITE-7059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda resolved IGNITE-7059. - Resolution: Fixed > Improve Collocated Processing page on the site > -- > > Key: IGNITE-7059 > URL: https://issues.apache.org/jira/browse/IGNITE-7059 > Project: Ignite > Issue Type: Sub-task > Components: site >Reporter: Denis Magda >Assignee: Denis Magda >Priority: Major > Fix For: 2.4 > > > Presently the collocated processing [1] covers general aspects of this > paradigm. Elaborate more on the following: > * How it's related to SQL > * How it's related to compute grid and ML > * As for compute grid, mention that it allows broadcast or run computations > on concrete nodes as well. > [1] https://ignite.apache.org/collocatedprocessing.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-7059) Improve Collocated Processing page on the site
[ https://issues.apache.org/jira/browse/IGNITE-7059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda closed IGNITE-7059. --- > Improve Collocated Processing page on the site > -- > > Key: IGNITE-7059 > URL: https://issues.apache.org/jira/browse/IGNITE-7059 > Project: Ignite > Issue Type: Sub-task > Components: site >Reporter: Denis Magda >Assignee: Denis Magda >Priority: Major > Fix For: 2.4 > > > Presently the collocated processing [1] covers general aspects of this > paradigm. Elaborate more on the following: > * How it's related to SQL > * How it's related to compute grid and ML > * As for compute grid, mention that it allows broadcast or run computations > on concrete nodes as well. > [1] https://ignite.apache.org/collocatedprocessing.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7351) Create a page for continuous queries
[ https://issues.apache.org/jira/browse/IGNITE-7351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-7351: Issue Type: Task (was: Sub-task) Parent: (was: IGNITE-7061) > Create a page for continuous queries > > > Key: IGNITE-7351 > URL: https://issues.apache.org/jira/browse/IGNITE-7351 > Project: Ignite > Issue Type: Task > Components: site >Reporter: Denis Magda >Priority: Major > Fix For: 2.5 > > > Create a page for continuous queries putting it under Features menu on the > site. This capability is a strong distinguisher from relational databases > that do not support continuous notifications and processing built around them. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7351) Create a page for continuous queries
[ https://issues.apache.org/jira/browse/IGNITE-7351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-7351: Fix Version/s: (was: 2.4) 2.5 > Create a page for continuous queries > > > Key: IGNITE-7351 > URL: https://issues.apache.org/jira/browse/IGNITE-7351 > Project: Ignite > Issue Type: Sub-task > Components: site >Reporter: Denis Magda >Priority: Major > Fix For: 2.5 > > > Create a page for continuous queries putting it under Features menu on the > site. This capability is a strong distinguisher from relational databases > that do not support continuous notifications and processing built around them. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-7655) Spark Data Frames: saving data frames into Ignite needs to be documented
Nikolay Izhikov created IGNITE-7655: --- Summary: Spark Data Frames: saving data frames into Ignite needs to be documented Key: IGNITE-7655 URL: https://issues.apache.org/jira/browse/IGNITE-7655 Project: Ignite Issue Type: Bug Components: spark Reporter: Nikolay Izhikov Assignee: Nikolay Izhikov Fix For: 2.4 Once IGNITE-7337 is ready for merge. This new feature of Ignite needs to be documented. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7654) Geospatial queries does not work for JDBC/ODBC
[
https://issues.apache.org/jira/browse/IGNITE-7654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Cherkasov updated IGNITE-7654:
--
Description:
Geospatial queries do not work for JDBC/ODBC.
I can create a table with GEOMETRY from sqlline, like this:
{code:java}
CREATE TABLE GEO_TABLE(GID INTEGER PRIMARY KEY, THE_GEOM GEOMETRY);{code}
I can add rows:
{code:java}
INSERT INTO GEO_TABLE(GID, THE_GEOM) VALUES (2, 'POINT(500 505)');{code}
but there's no way to select GEOMETRY objects:
{code:java}
SELECT THE_GEOM FROM GEO_TABLE;{code}
sqlline throws the following excpetion:
{noformat}
Error: class org.apache.ignite.binary.BinaryObjectException: Custom objects are
not supported (state=5,code=0)
java.sql.SQLException: class org.apache.ignite.binary.BinaryObjectException:
Custom objects are not supported
at
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:671)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:130)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:299)
at sqlline.Commands.execute(Commands.java:823)
at sqlline.Commands.sql(Commands.java:733)
at sqlline.SqlLine.dispatch(SqlLine.java:795)
at sqlline.SqlLine.begin(SqlLine.java:668)
at sqlline.SqlLine.start(SqlLine.java:373)
at sqlline.SqlLine.main(SqlLine.java:265){noformat}
was:
Geospatial queries do not work for JDBC/ODBC.
I can create a table with GEOMETRY from sqlline, like this:
{code:java}
CREATE TABLE GEO_TABLE(GID INTEGER PRIMARY KEY, THE_GEOM GEOMETRY);{code}
table creation works fine, I can add rows:
{code:java}
INSERT INTO GEO_TABLE(GID, THE_GEOM) VALUES (2, 'POINT(500 505)');{code}
but there's no way to select GEOMETRY objects:
{code:java}
SELECT THE_GEOM FROM GEO_TABLE;{code}
{noformat}
Error: class org.apache.ignite.binary.BinaryObjectException: Custom objects are
not supported (state=5,code=0)
java.sql.SQLException: class org.apache.ignite.binary.BinaryObjectException:
Custom objects are not supported
at
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:671)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:130)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:299)
at sqlline.Commands.execute(Commands.java:823)
at sqlline.Commands.sql(Commands.java:733)
at sqlline.SqlLine.dispatch(SqlLine.java:795)
at sqlline.SqlLine.begin(SqlLine.java:668)
at sqlline.SqlLine.start(SqlLine.java:373)
at sqlline.SqlLine.main(SqlLine.java:265){noformat}
> Geospatial queries does not work for JDBC/ODBC
> --
>
> Key: IGNITE-7654
> URL: https://issues.apache.org/jira/browse/IGNITE-7654
> Project: Ignite
> Issue Type: Bug
> Components: jdbc, odbc, sql, thin client
>Affects Versions: 2.3
>Reporter: Mikhail Cherkasov
>Priority: Major
> Fix For: 2.5
>
>
> Geospatial queries do not work for JDBC/ODBC.
> I can create a table with GEOMETRY from sqlline, like this:
> {code:java}
> CREATE TABLE GEO_TABLE(GID INTEGER PRIMARY KEY, THE_GEOM GEOMETRY);{code}
> I can add rows:
> {code:java}
> INSERT INTO GEO_TABLE(GID, THE_GEOM) VALUES (2, 'POINT(500 505)');{code}
> but there's no way to select GEOMETRY objects:
> {code:java}
> SELECT THE_GEOM FROM GEO_TABLE;{code}
> sqlline throws the following excpetion:
> {noformat}
> Error: class org.apache.ignite.binary.BinaryObjectException: Custom objects
> are not supported (state=5,code=0)
> java.sql.SQLException: class org.apache.ignite.binary.BinaryObjectException:
> Custom objects are not supported
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:671)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:130)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:299)
> at sqlline.Commands.execute(Commands.java:823)
> at sqlline.Commands.sql(Commands.java:733)
> at sqlline.SqlLine.dispatch(SqlLine.java:795)
> at sqlline.SqlLine.begin(SqlLine.java:668)
> at sqlline.SqlLine.start(SqlLine.java:373)
> at sqlline.SqlLine.main(SqlLine.java:265){noformat}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-7654) Geospatial queries does not work for JDBC/ODBC
Mikhail Cherkasov created IGNITE-7654:
-
Summary: Geospatial queries does not work for JDBC/ODBC
Key: IGNITE-7654
URL: https://issues.apache.org/jira/browse/IGNITE-7654
Project: Ignite
Issue Type: Bug
Components: jdbc, odbc, sql, thin client
Affects Versions: 2.3
Reporter: Mikhail Cherkasov
Fix For: 2.5
Geospatial queries do not work for JDBC/ODBC.
I can create a table with GEOMETRY from sqlline, like this:
{code:java}
CREATE TABLE GEO_TABLE(GID INTEGER PRIMARY KEY, THE_GEOM GEOMETRY);{code}
table creation works fine, I can add rows:
{code:java}
INSERT INTO GEO_TABLE(GID, THE_GEOM) VALUES (2, 'POINT(500 505)');{code}
but there's no way to select GEOMETRY objects:
{code:java}
SELECT THE_GEOM FROM GEO_TABLE;{code}
{noformat}
Error: class org.apache.ignite.binary.BinaryObjectException: Custom objects are
not supported (state=5,code=0)
java.sql.SQLException: class org.apache.ignite.binary.BinaryObjectException:
Custom objects are not supported
at
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:671)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:130)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:299)
at sqlline.Commands.execute(Commands.java:823)
at sqlline.Commands.sql(Commands.java:733)
at sqlline.SqlLine.dispatch(SqlLine.java:795)
at sqlline.SqlLine.begin(SqlLine.java:668)
at sqlline.SqlLine.start(SqlLine.java:373)
at sqlline.SqlLine.main(SqlLine.java:265){noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (IGNITE-7638) Page replacement process in PDS mode affect segment loaded pages table performance
[
https://issues.apache.org/jira/browse/IGNITE-7638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-7638:
---
Comment: was deleted
(was: Fast fix with migrating continious removed segments to empty if last one
is empty gives some considerable effect.
Segments statistics in my test is as follows:
{noformat}
Avg steps in loaded pages table, get: 348 steps, 4358 ops/sec, put: 1037
steps, 1380 ops/sec, capacity: 20242 size: 7978 removedCnt: 12023 emptyCnt:
241 rmv->empty cells: 20624
Avg steps in loaded pages table, get: 183 steps, 7715 ops/sec, put: 788 steps,
1624 ops/sec, capacity: 20242 size: 7978 removedCnt: 12060 emptyCnt: 204
rmv->empty cells: 18963
Avg steps in loaded pages table, get: 235 steps, 7874 ops/sec, put: 1050
steps, 1721 ops/sec, capacity: 20242 size: 7978 removedCnt: 12066 emptyCnt:
198 rmv->empty cells: 19910
Avg steps in loaded pages table, get: 421 steps, 8345 ops/sec, put: 2048
steps, 1643 ops/sec, capacity: 20242 size: 7978 removedCnt: 12233 emptyCnt: 31
rmv->empty cells: 17944
Avg steps in loaded pages table, get: 349 steps, 7883 ops/sec, put: 1683
steps, 1559 ops/sec, capacity: 20242 size: 7978 removedCnt: 12078 emptyCnt:
186 rmv->empty cells: 18935
Avg steps in loaded pages table, get: 264 steps, 8060 ops/sec, put: 1283
steps, 1568 ops/sec, capacity: 20242 size: 7978 removedCnt: 12105 emptyCnt:
159 rmv->empty cells: 18854
Avg steps in loaded pages table, get: 405 steps, 8289 ops/sec, put: 1781
steps, 1856 ops/sec, capacity: 20242 size: 7978 removedCnt: 12142 emptyCnt:
122 rmv->empty cells: 18529
Avg steps in loaded pages table, get: 347 steps, 8059 ops/sec, put: 1494
steps, 1873 ops/sec, capacity: 20242 size: 7978 removedCnt: 12097 emptyCnt:
167 rmv->empty cells: 19652
{noformat})
> Page replacement process in PDS mode affect segment loaded pages table
> performance
> --
>
> Key: IGNITE-7638
> URL: https://issues.apache.org/jira/browse/IGNITE-7638
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Critical
> Fix For: 2.5
>
>
> There is
> - durable memory segment in PDS enabled data region
> - page replacement started
> then Ignite performance slow down occurs, JFR & Visual VM shows get&put from
> FullPageIdTable requires significiant time to be executed (~5-10% оf samples
> count and up to 40% CPU usage)
> {noformat}
> Avg steps in loaded pages table, get: 9456 steps, put: 20243 steps,
> capacity: 20242 size: 7978
> {noformat}
> Effect of influence of FullPageID table is cumulative, once it starts to
> grow, number of steps required grows also.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7337) Spark Data Frames: support saving a data frame in Ignite
[
https://issues.apache.org/jira/browse/IGNITE-7337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357486#comment-16357486
]
Nikolay Izhikov commented on IGNITE-7337:
-
Just for the record:
As discussed with [~vkulichenko]:
{{allowOverwrite}} implemented as a user option
{{OPTION_STREAMER_ALLOW_OVERWRITE}}.
User has to decide which behaviour he prefer.
Default value is {{false}}.
> Spark Data Frames: support saving a data frame in Ignite
>
>
> Key: IGNITE-7337
> URL: https://issues.apache.org/jira/browse/IGNITE-7337
> Project: Ignite
> Issue Type: New Feature
> Components: spark
>Affects Versions: 2.3
>Reporter: Valentin Kulichenko
>Assignee: Nikolay Izhikov
>Priority: Major
> Fix For: 2.4
>
>
> Once Ignite data source for Spark is implemented, we need to add an ability
> to store a data frame in Ignite. Most likely if should be enough to provide
> implementation for the following traits:
> * {{InsertableRelation}}
> * {{CreatableRelationProvider}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-425) Introduce transformers for continuous queries
[
https://issues.apache.org/jira/browse/IGNITE-425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357481#comment-16357481
]
ASF GitHub Bot commented on IGNITE-425:
---
Github user nizhikov closed the pull request at:
https://github.com/apache/ignite/pull/2372
> Introduce transformers for continuous queries
> -
>
> Key: IGNITE-425
> URL: https://issues.apache.org/jira/browse/IGNITE-425
> Project: Ignite
> Issue Type: Sub-task
> Components: cache
>Affects Versions: 2.2
>Reporter: Yakov Zhdanov
>Assignee: Nikolay Izhikov
>Priority: Major
> Fix For: 2.5
>
>
> Currently if updated entry passes the filter, it is sent to node initiated
> the query entirely. It would be good to provide user with the ability to
> transform entry and, for example, select only fields that are important. This
> may bring huge economy to traffic and lower GC pressure as well.
> Possible signatures will be:
> {noformat}
> public final class ContinuousQuery {..} // T is a type transformer
> transforms to
> public ContinuousQuery setLocalListener(Listener locLsnr) {..} //
> Probably, we will have to introduce new listener type, since user may want to
> wipe out key as well.
> /* new method to add */
> public ContinuousQuery setRemoteTransformerFactory(Factory ContinuousQueryTransformer> factory) { ..}
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7606) Write removed dirty page during replacement without holding segment write lock
[ https://issues.apache.org/jira/browse/IGNITE-7606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357394#comment-16357394 ] ASF GitHub Bot commented on IGNITE-7606: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/3469 > Write removed dirty page during replacement without holding segment write lock > -- > > Key: IGNITE-7606 > URL: https://issues.apache.org/jira/browse/IGNITE-7606 > Project: Ignite > Issue Type: Improvement > Components: persistence >Reporter: Dmitriy Pavlov >Assignee: Dmitriy Pavlov >Priority: Major > Fix For: 2.5 > > Attachments: chart_holdingLock.png, chart_notHoldingLock.png, > chart_notHoldingLock2.png, putdumpAt17second.txt > > > If a dirty page under the checkpoint is found, following is suggested > - copy it to the local thread buffer, > - and then after performing all actions in region for evicting the page > - finish execution allocatePage()/acquirePage() > - unlock segment to allow other workers to operate > - perform the pwrite() call based on the data from local buffer > Now if page eviction started there is possible drops to 0 put/seconds in case > a lot of threads are watiting for same segment lock. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7438) LSQR: Sparse Equations and Least Squares for Lin Regression
[ https://issues.apache.org/jira/browse/IGNITE-7438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357236#comment-16357236 ] ASF GitHub Bot commented on IGNITE-7438: GitHub user dmitrievanthony opened a pull request: https://github.com/apache/ignite/pull/3494 IGNITE-7438 LSQR solver for Linear Regression You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7438 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/3494.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 #3494 commit 1fd21f05fa7f288e42d19126f4d4ea9a3a7f902f Author: dmitrievanthony Date: 2018-01-16T15:55:04Z IGNITE-7437 Initial version of d-learn framework in ML module. commit 104b3bb9badcea4d0d907cca39624cc84ef9544d Author: dmitrievanthony Date: 2018-01-16T20:05:04Z IGNITE-7437 Introduce DLearnContextTransformers into ML module. commit 006b749e4742698f837582b3224a93468c88511e Author: dmitrievanthony Date: 2018-01-16T20:18:39Z IGNITE-7437 Introduce DLearnContextTransformers into ML module (fix compilation issues). commit d8696b6210dccaa92f4de459a9590f9e0896c7db Author: dmitrievanthony Date: 2018-01-17T08:26:52Z IGNITE-7437 Move dataset API into d-learn context wrapper to avoid introducing an additional util classes. commit c03e58ef67debc2a2e42bfd9f829bfe5c5a60a45 Author: dmitrievanthony Date: 2018-01-17T10:30:16Z IGNITE-7437 Add ability to close learning context. commit 8cdc9c516f8a248f177e4a5fe9a49b027aba96e3 Author: dmitrievanthony Date: 2018-01-17T11:28:43Z IGNITE-7437 Reformat code and javadoc. commit 146c0785b2c125baf3216c6dd2ad8c38fec9f5a8 Author: dmitrievanthony Date: 2018-01-17T15:20:04Z IGNITE-7437 Add affinity tests for d-learn context factory. commit be830a8e133facb69fd1a6166b3ca4ec6a7de25b Author: dmitrievanthony Date: 2018-01-17T15:22:15Z Merge branch 'master' into ignite-7437 commit 6c4f191081019c91a4b78f40bdf6f52a9f46eb47 Author: dmitrievanthony Date: 2018-01-17T16:07:08Z IGNITE-7437 Add dataset loading examples (cache and local) for d-learn. commit 21b648b182305c34a061e55d7d2b287165c362eb Author: dmitrievanthony Date: 2018-01-17T16:40:12Z IGNITE-7437 Add dataset transformation example for d-learn. commit 87194ba42c7dd3250e0dac30dd11bb1a1283022c Author: dmitrievanthony Date: 2018-01-19T16:21:59Z IGNITE-7437 Use affinityCall/affinityRun in cache d-learn context implementation to guarantee partitions reservation during computation. commit a553f12f3fb0c3b64470d2e3002a5eb49013614c Author: dmitrievanthony Date: 2018-01-19T16:32:10Z IGNITE-7437 Reformat code. commit 03a6bfe1b47a259e1cf400762dca427ab4ecf928 Author: dmitrievanthony Date: 2018-01-19T17:32:49Z IGNITE-7437 Update Javadoc. commit e9c63f9f7f5f55dc60d9ac0b9bddb4f8ad9f6a67 Author: dmitrievanthony Date: 2018-01-22T08:51:37Z IGNITE-7437 Update Javadoc. commit 7ebd20a6ef1eca6063013a5f8a8361ae4f76a609 Author: dmitrievanthony Date: 2018-01-23T22:23:24Z IGNITE-7437 Introduce IDD (Ignite Distributed Dataset) as a prototype. commit 3c11f600b920fe19f57ca4203be5ac44219c4f52 Author: dmitrievanthony Date: 2018-01-24T16:50:12Z IGNITE-7437 Introduce DLC (Distributed Learning Context). commit 8381bd827cae78478532bf0e55446ff38b1d9e3a Author: dmitrievanthony Date: 2018-01-25T10:35:26Z IGNITE-7437 Update DLC and add examples. commit c21e43406a1a1d398277bc40a818d87752afb11a Author: dmitrievanthony Date: 2018-01-25T17:03:53Z IGNITE-7437 Update DLC and add examples. commit 9d72b1cb7b8129fe3290fe6ab2bd8433f90f9aae Author: dmitrievanthony Date: 2018-01-26T17:14:39Z IGNITE-7437 Update DLC and add examples. commit f83153e16b1dba9eed6c6e26b717726f8b416c96 Author: dmitrievanthony Date: 2018-01-27T15:15:06Z IGNITE-7437 Updated javadoc and tests, removed d-learn part. commit c39b3ebf2d0793a1044c75663fa9cbbcb0777ae7 Author: dmitrievanthony Date: 2018-01-27T15:17:34Z IGNITE-7437 Remove d-learn part from examples. commit a00ff930217c5d99901dc7491d5148b89f9c8788 Author: dmitrievanthony Date: 2018-01-29T11:09:39Z IGNITE-7437 Update examples for partition based dataset. commit 616c18e52b4bcd44b47f13c1eab37bcf16df3259 Author: dmitrievanthony Date: 2018-01-29T11:20:37Z IGNITE-7437 Add package-info.java files. commit ef092a6c1893199cb5542eabdd20d05b30327a6a Author: dmitrievanthony Date: 2018-01-29T11:22:24Z IGNITE-7437 Revert wrong changes. commit ad411dbe0b039fe63c43b25774357a4a95d3a91e Author: dmitrievanthony Date: 2018-01-30T13:45:05Z IGNITE-7437 Update unit tests for cache based and local datasets. commit 91f612a22c03a07bda7addcbc6a1e0
[jira] [Comment Edited] (IGNITE-6432) SpringCacheManager#getCacheNames() is empty
[
https://issues.apache.org/jira/browse/IGNITE-6432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357200#comment-16357200
]
Pavel Vinokurov edited comment on IGNITE-6432 at 2/8/18 4:52 PM:
-
[~vchibaev]
Not a bug.
Execution of cacheManager.getCache("refdata.labelType") instantiates new
cache.After that the cache could be returned via cacheManager.getCacheNames().
The ConcurrentMapCacheManager has same behavior with dynamic flag set to true.
was (Author: pvinokurov):
Not a bug.
Execution of cacheManager.getCache("refdata.labelType") instantiates new
cache.After that the cache could be returned via cacheManager.getCacheNames().
The ConcurrentMapCacheManager has same behavior with dynamic flag set to true.
> SpringCacheManager#getCacheNames() is empty
> ---
>
> Key: IGNITE-6432
> URL: https://issues.apache.org/jira/browse/IGNITE-6432
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Valeri Chibaev
>Priority: Major
>
> Application ignite started with org.apache.ignite.IgniteSpringBean, then
> SpringCacheManager created
> {code}
> class="org.apache.ignite.configuration.IgniteConfiguration"
> p:igniteInstanceName="ignite-grid">
>
>
>p:name="refdata.labelType" />
>
>
>
> p:configuration-ref="ignite-config" />
> class="org.apache.ignite.cache.spring.SpringCacheManager" depends-on="ignite"
> p:igniteInstanceName="ignite-grid" />
> {code}
> If I'll check cacheManager.getCacheNames() - it is empty.
> But if I check cacheManager.getCache("refdata.labelType") metrics and repeat
> call cacheManager.getCacheNames() - it is not empty.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-6432) SpringCacheManager#getCacheNames() is empty
[
https://issues.apache.org/jira/browse/IGNITE-6432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357200#comment-16357200
]
Pavel Vinokurov commented on IGNITE-6432:
-
Not a bug.
Execution of cacheManager.getCache("refdata.labelType") instantiates new
cache.After that the cache could be returned via cacheManager.getCacheNames().
The ConcurrentMapCacheManager has same behavior with dynamic flag set to true.
> SpringCacheManager#getCacheNames() is empty
> ---
>
> Key: IGNITE-6432
> URL: https://issues.apache.org/jira/browse/IGNITE-6432
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Valeri Chibaev
>Priority: Major
>
> Application ignite started with org.apache.ignite.IgniteSpringBean, then
> SpringCacheManager created
> {code}
> class="org.apache.ignite.configuration.IgniteConfiguration"
> p:igniteInstanceName="ignite-grid">
>
>
>p:name="refdata.labelType" />
>
>
>
> p:configuration-ref="ignite-config" />
> class="org.apache.ignite.cache.spring.SpringCacheManager" depends-on="ignite"
> p:igniteInstanceName="ignite-grid" />
> {code}
> If I'll check cacheManager.getCacheNames() - it is empty.
> But if I check cacheManager.getCache("refdata.labelType") metrics and repeat
> call cacheManager.getCacheNames() - it is not empty.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7649) transformer instance is not properly transfers into ScanQuery request.
[
https://issues.apache.org/jira/browse/IGNITE-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357168#comment-16357168
]
Stanilovsky Evgeny commented on IGNITE-7649:
[~amashenkov], yep, fix it! thanks.
> transformer instance is not properly transfers into ScanQuery request.
> --
>
> Key: IGNITE-7649
> URL: https://issues.apache.org/jira/browse/IGNITE-7649
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.3
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
> Fix For: 2.5
>
>
> to reproduce this case we need some simple changes in existing test:
> GridCacheQueryTransformerSelfTest#testKeepBinary
> change:
> {code:java}
> List res = binaryCache.query(new ScanQuery(),
> transformer).getAll();{code}
> into:
> {code:java}
> List res = binaryCache.query(new ScanQuery BinaryObject>().setPageSize(2), transformer).getAll();{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-7649) transformer instance is not properly transfers into ScanQuery request.
[
https://issues.apache.org/jira/browse/IGNITE-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stanilovsky Evgeny updated IGNITE-7649:
---
Summary: transformer instance is not properly transfers into ScanQuery
request. (was: transformer instance is not properly transfers into SqlQuery
request.)
> transformer instance is not properly transfers into ScanQuery request.
> --
>
> Key: IGNITE-7649
> URL: https://issues.apache.org/jira/browse/IGNITE-7649
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.3
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
> Fix For: 2.5
>
>
> to reproduce this case we need some simple changes in existing test:
> GridCacheQueryTransformerSelfTest#testKeepBinary
> change:
> {code:java}
> List res = binaryCache.query(new ScanQuery(),
> transformer).getAll();{code}
> into:
> {code:java}
> List res = binaryCache.query(new ScanQuery BinaryObject>().setPageSize(2), transformer).getAll();{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7513) Get rid of org.jsr166.ConcurrentHashMap8
[ https://issues.apache.org/jira/browse/IGNITE-7513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357150#comment-16357150 ] Anton Vinogradov commented on IGNITE-7513: -- [~andrey-kuznetsov], We have to check there is no performance drop before merge. > Get rid of org.jsr166.ConcurrentHashMap8 > > > Key: IGNITE-7513 > URL: https://issues.apache.org/jira/browse/IGNITE-7513 > Project: Ignite > Issue Type: Sub-task >Reporter: Andrey Kuznetsov >Assignee: Andrey Kuznetsov >Priority: Major > Fix For: 2.5 > > > This class was made of ConcurrentHashMapV8, an intermediate implementation of > Java8's ConcurrentHashMap. Now we should switch to standard CHM. Possibly, > we'll have to check for performance implications. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-6432) SpringCacheManager#getCacheNames() is empty
[
https://issues.apache.org/jira/browse/IGNITE-6432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Vinokurov reassigned IGNITE-6432:
---
Assignee: (was: Pavel Vinokurov)
> SpringCacheManager#getCacheNames() is empty
> ---
>
> Key: IGNITE-6432
> URL: https://issues.apache.org/jira/browse/IGNITE-6432
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Valeri Chibaev
>Priority: Major
>
> Application ignite started with org.apache.ignite.IgniteSpringBean, then
> SpringCacheManager created
> {code}
> class="org.apache.ignite.configuration.IgniteConfiguration"
> p:igniteInstanceName="ignite-grid">
>
>
>p:name="refdata.labelType" />
>
>
>
> p:configuration-ref="ignite-config" />
> class="org.apache.ignite.cache.spring.SpringCacheManager" depends-on="ignite"
> p:igniteInstanceName="ignite-grid" />
> {code}
> If I'll check cacheManager.getCacheNames() - it is empty.
> But if I check cacheManager.getCache("refdata.labelType") metrics and repeat
> call cacheManager.getCacheNames() - it is not empty.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-7431) Thin client Java API - cache replace/remove API
[ https://issues.apache.org/jira/browse/IGNITE-7431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kukushkin updated IGNITE-7431: - Description: Implement cache replace/remove thin client Java API including unit and system tests and samples. Cache replace(key, val) replace(key, oldVal, newVal) remove(key) remove(key, val) removeAll() removeAll(keys: Set) > Thin client Java API - cache replace/remove API > --- > > Key: IGNITE-7431 > URL: https://issues.apache.org/jira/browse/IGNITE-7431 > Project: Ignite > Issue Type: Sub-task >Reporter: Alexey Kukushkin >Assignee: Alexey Kukushkin >Priority: Major > Labels: data, java, thin > > Implement cache replace/remove thin client Java API including unit and system > tests and samples. > Cache > replace(key, val) > replace(key, oldVal, newVal) > remove(key) > remove(key, val) > removeAll() > removeAll(keys: Set) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7431) Thin client Java API - cache replace/remove API
[ https://issues.apache.org/jira/browse/IGNITE-7431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kukushkin updated IGNITE-7431: - Environment: (was: Implement cache replace/remove thin client Java API including unit and system tests and samples. Cache replace(key, val) replace(key, oldVal, newVal) remove(key) remove(key, val) removeAll() removeAll(keys: Set)) > Thin client Java API - cache replace/remove API > --- > > Key: IGNITE-7431 > URL: https://issues.apache.org/jira/browse/IGNITE-7431 > Project: Ignite > Issue Type: Sub-task >Reporter: Alexey Kukushkin >Assignee: Alexey Kukushkin >Priority: Major > Labels: data, java, thin > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-6432) SpringCacheManager#getCacheNames() is empty
[
https://issues.apache.org/jira/browse/IGNITE-6432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Vinokurov reassigned IGNITE-6432:
---
Assignee: Pavel Vinokurov
> SpringCacheManager#getCacheNames() is empty
> ---
>
> Key: IGNITE-6432
> URL: https://issues.apache.org/jira/browse/IGNITE-6432
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Valeri Chibaev
>Assignee: Pavel Vinokurov
>Priority: Major
>
> Application ignite started with org.apache.ignite.IgniteSpringBean, then
> SpringCacheManager created
> {code}
> class="org.apache.ignite.configuration.IgniteConfiguration"
> p:igniteInstanceName="ignite-grid">
>
>
>p:name="refdata.labelType" />
>
>
>
> p:configuration-ref="ignite-config" />
> class="org.apache.ignite.cache.spring.SpringCacheManager" depends-on="ignite"
> p:igniteInstanceName="ignite-grid" />
> {code}
> If I'll check cacheManager.getCacheNames() - it is empty.
> But if I check cacheManager.getCache("refdata.labelType") metrics and repeat
> call cacheManager.getCacheNames() - it is not empty.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-7538) Introduce new test project for Ignite 2.0+ with Java 8 / Java 9 compatibility
[ https://issues.apache.org/jira/browse/IGNITE-7538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Ivanov updated IGNITE-7538: - Description: After IGNITE-7203 and IGNITE-6730 there are two separate test project at CI which meet the problem of test configuration synchronization. It is necessary to devise a solution for overcoming this issue. Possible approaches: # Single project for tests with run with different parameters. Problems: #* Test History will show history for all builds with any parameters combination. #* Mute test will mute test for all parameters configuration. # Several project (differentiated by parameter) with build configuration synchronisation automation. Problems: #* Maintainability — how to seamlessly support build configuration synchronisation. Research for both approaches must be held. After corresponding research, following targets are required: # Speedup -- introduce more optimal architecture of build chain (with one build - multiple tests). # Java 8 / Java 9 compatibility. was: After IGNITE-7203 and IGNITE-6730 there are two separate test project at CI which meet the problem of test configuration synchronization. It is necessary to devise a solution for overcoming this issue. Possible approaches: # Single project for tests with run with different parameters. Problems: #* Test History will show history for all builds with any parameters combination. #* Mute test will mute test for all parameters configuration. # Several project (differentiated by parameter) with build configuration synchronisation automation. Problems: #* Maintainability — how to seamlessly support build configuration synchronisation. Research for both approaches must be held. > Introduce new test project for Ignite 2.0+ with Java 8 / Java 9 compatibility > - > > Key: IGNITE-7538 > URL: https://issues.apache.org/jira/browse/IGNITE-7538 > Project: Ignite > Issue Type: Task >Reporter: Peter Ivanov >Assignee: Peter Ivanov >Priority: Critical > > After IGNITE-7203 and IGNITE-6730 there are two separate test project at CI > which meet the problem of test configuration synchronization. It is necessary > to devise a solution for overcoming this issue. > Possible approaches: > # Single project for tests with run with different parameters. > Problems: > #* Test History will show history for all builds with any parameters > combination. > #* Mute test will mute test for all parameters configuration. > # Several project (differentiated by parameter) with build configuration > synchronisation automation. > Problems: > #* Maintainability — how to seamlessly support build configuration > synchronisation. > Research for both approaches must be held. > After corresponding research, following targets are required: > # Speedup -- introduce more optimal architecture of build chain (with one > build - multiple tests). > # Java 8 / Java 9 compatibility. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7538) Introduce new test project for Ignite 2.0+ with Java 8 / Java 9 compatibility
[ https://issues.apache.org/jira/browse/IGNITE-7538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Ivanov updated IGNITE-7538: - Issue Type: Task (was: Sub-task) Parent: (was: IGNITE-7234) > Introduce new test project for Ignite 2.0+ with Java 8 / Java 9 compatibility > - > > Key: IGNITE-7538 > URL: https://issues.apache.org/jira/browse/IGNITE-7538 > Project: Ignite > Issue Type: Task >Reporter: Peter Ivanov >Assignee: Peter Ivanov >Priority: Critical > > After IGNITE-7203 and IGNITE-6730 there are two separate test project at CI > which meet the problem of test configuration synchronization. It is necessary > to devise a solution for overcoming this issue. > Possible approaches: > # Single project for tests with run with different parameters. > Problems: > #* Test History will show history for all builds with any parameters > combination. > #* Mute test will mute test for all parameters configuration. > # Several project (differentiated by parameter) with build configuration > synchronisation automation. > Problems: > #* Maintainability — how to seamlessly support build configuration > synchronisation. > Research for both approaches must be held. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-7540) Sequential checkpoints cause overwrite of already cleaned & freed offheap page
[
https://issues.apache.org/jira/browse/IGNITE-7540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Kovalenko reassigned IGNITE-7540:
---
Assignee: Alexey Goncharuk (was: Pavel Kovalenko)
Ready to review
TC:
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&branch_IgniteTests24Java8=pull%2F3490%2Fhead
PR: https://github.com/apache/ignite/pull/3490
> Sequential checkpoints cause overwrite of already cleaned & freed offheap page
> --
>
> Key: IGNITE-7540
> URL: https://issues.apache.org/jira/browse/IGNITE-7540
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Affects Versions: 2.4
>Reporter: Ilya Kasnacheev
>Assignee: Alexey Goncharuk
>Priority: Major
> Attachments: IgnitePdsDestroyCacheTest.java
>
>
> The sequence of events as follows:
> in GridCacheProcessor.onExchangeDone(),
> {color:#660e7a}sharedCtx{color}.database().waitForCheckpoint({color:#008000}"caches
> stop"{color}) is peformed and then cache is destroyed and all its pages are
> freed and cleared asynchronously.
> However, it is entirely possible that after waitForCheckpoint(), next
> checkpoint will start immediately. It is typical when a lot of data being
> loaded into Ignite, leading to rapid checkpoint buffer depletion, as well as
> with artificially increased checkpoint frequency, as used in reproducer.
> Then, checkpointer will save (overwrite) metadata page:
> {code:java}
> at
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.writeUnlockPage(PageMemoryImpl.java:1330)
> at
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.writeUnlock(PageMemoryImpl.java:428)
> at
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.writeUnlock(PageMemoryImpl.java:422)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager.saveStoreMetadata(GridCacheOffheapManager.java:375)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager.onCheckpointBegin(GridCacheOffheapManager.java:163)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.markCheckpointBegin(GridCacheDatabaseSharedManager.java:2309)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.doCheckpoint(GridCacheDatabaseSharedManager.java:2088)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.body(GridCacheDatabaseSharedManager.java:2013)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:748){code}
> This will happen after cache is already destroyed and even after the page is
> already zeroed by PageMemoryImpl$ClearSegmentRunnable.run().
> Then, some new cache is being created, and in
> GridCacheOffheapManager$GridCacheDataStore.getOrAllocatePartitionMetas(),
> pageMem.acquirePage() will return this page, expected zeroed, but actually
> containing metadata for old cache's partition. Then, type ==
> PageIO.T_PART_META check will return true and the following exception is
> issued, leading to cache state inconsistency and data loss:
> {code:java}
> Caused by: java.lang.IllegalStateException: Failed to get page IO instance
> (page content is corrupted)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.io.IOVersions.forVersion(IOVersions.java:83)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.io.IOVersions.forPage(IOVersions.java:95)
> at
> org.apache.ignite.internal.processors.cache.persistence.freelist.PagesList.init(PagesList.java:175)
> at
> org.apache.ignite.internal.processors.cache.persistence.freelist.FreeListImpl.(FreeListImpl.java:370)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore$1.(GridCacheOffheapManager.java:932)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.init0(GridCacheOffheapManager.java:929)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.invoke(GridCacheOffheapManager.java:1295)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.invoke(IgniteCacheOffheapManagerImpl.java:344)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.storeValue(GridCacheMapEntry.java:3191)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.initialValue(GridCacheMapEntry.java:2571)
> at
> org.apache.ignite.internal.processors.datastreamer.DataSt
[jira] [Assigned] (IGNITE-7431) Thin client Java API - cache replace/remove API
[ https://issues.apache.org/jira/browse/IGNITE-7431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kukushkin reassigned IGNITE-7431: Assignee: Alexey Kukushkin > Thin client Java API - cache replace/remove API > --- > > Key: IGNITE-7431 > URL: https://issues.apache.org/jira/browse/IGNITE-7431 > Project: Ignite > Issue Type: Sub-task > Environment: Implement cache replace/remove thin client Java API > including unit and system tests and samples. > Cache > replace(key, val) > replace(key, oldVal, newVal) > remove(key) > remove(key, val) > removeAll() > removeAll(keys: Set) >Reporter: Alexey Kukushkin >Assignee: Alexey Kukushkin >Priority: Major > Labels: data, java, thin > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-7430) Thin client Java API - cache putAll/getAll
[ https://issues.apache.org/jira/browse/IGNITE-7430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kukushkin resolved IGNITE-7430. -- Resolution: Fixed > Thin client Java API - cache putAll/getAll > -- > > Key: IGNITE-7430 > URL: https://issues.apache.org/jira/browse/IGNITE-7430 > Project: Ignite > Issue Type: Sub-task > Environment: >Reporter: Alexey Kukushkin >Assignee: Alexey Kukushkin >Priority: Major > Labels: data, java, thin > > Implement cache putAll/getAll thin client Java API including unit and system > tests and samples. > Cache > putAll(keys: Set): Map > getAll -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7398) InstanceNotFoundException appears in the log when a cache is closed and MBeans are disabled
[ https://issues.apache.org/jira/browse/IGNITE-7398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357010#comment-16357010 ] ASF GitHub Bot commented on IGNITE-7398: GitHub user pvinokurov opened a pull request: https://github.com/apache/ignite/pull/3492 IGNITE-7398 Disabled MBean registration for cache group if IGNITE_MBE… You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7398 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/3492.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 #3492 commit a39f2f899842ca03e2f9ab90c336f8fa246b8843 Author: pvinokurov Date: 2018-02-08T14:22:43Z IGNITE-7398 Disabled MBean registration for cache group if IGNITE_MBEANS_DISABLED set to true > InstanceNotFoundException appears in the log when a cache is closed and > MBeans are disabled > --- > > Key: IGNITE-7398 > URL: https://issues.apache.org/jira/browse/IGNITE-7398 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.4 >Reporter: Stanislav Lukyanov >Assignee: Pavel Vinokurov >Priority: Minor > > If IGNITE_MBEANS_DISABLED is set to true, whenever a cache is started the > following error is logged: > javax.management.InstanceNotFoundException: > org.apache:clsLdr=18b4aac2,igniteInstanceName=mbeans.GridMBeanDisableSelfTest0,group=Cache > groups,name=MyCache > at > com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean(DefaultMBeanServerInterceptor.java:1095) > at > com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.exclusiveUnregisterMBean(DefaultMBeanServerInterceptor.java:427) > at > com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.unregisterMBean(DefaultMBeanServerInterceptor.java:415) > at > com.sun.jmx.mbeanserver.JmxMBeanServer.unregisterMBean(JmxMBeanServer.java:546) > at > org.apache.ignite.internal.processors.cache.GridCacheProcessor.cleanup(GridCacheProcessor.java:606) > at > org.apache.ignite.internal.processors.cache.GridCacheProcessor.stopCacheGroup(GridCacheProcessor.java:2264) > at > org.apache.ignite.internal.processors.cache.GridCacheProcessor.stopCacheGroup(GridCacheProcessor.java:2253) > at > org.apache.ignite.internal.processors.cache.GridCacheProcessor.stopCaches(GridCacheProcessor.java:907) > at > org.apache.ignite.internal.processors.cache.GridCacheProcessor.stop(GridCacheProcessor.java:872) > at org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:2316) > at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:2182) > at > org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2512) > at > org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2475) > at org.apache.ignite.internal.IgnitionEx.stop(IgnitionEx.java:362) > at org.apache.ignite.Ignition.stop(Ignition.java:224) > at org.apache.ignite.internal.IgniteKernal.close(IgniteKernal.java:3509) > at > org.apache.ignite.util.mbeans.GridMBeanDisableSelfTest.testCorrectMBeanInfo(GridMBeanDisableSelfTest.java:101) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at junit.framework.TestCase.runTest(TestCase.java:176) > at > org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2001) > at > org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:133) > at > org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1916) > at java.lang.Thread.run(Thread.java:748) > That's because GridCacheProcessor::cleanup unconditionally attempts to > unregister cache's MBean, not checking whether or not the cache actually has > an MBean registered for it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7430) Thin client Java API - cache putAll/getAll
[ https://issues.apache.org/jira/browse/IGNITE-7430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kukushkin updated IGNITE-7430: - Description: Implement cache putAll/getAll thin client Java API including unit and system tests and samples. Cache putAll(keys: Set): Map getAll > Thin client Java API - cache putAll/getAll > -- > > Key: IGNITE-7430 > URL: https://issues.apache.org/jira/browse/IGNITE-7430 > Project: Ignite > Issue Type: Sub-task > Environment: >Reporter: Alexey Kukushkin >Assignee: Alexey Kukushkin >Priority: Major > Labels: data, java, thin > > Implement cache putAll/getAll thin client Java API including unit and system > tests and samples. > Cache > putAll(keys: Set): Map > getAll -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-7632) NPE in IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.updateIgfsMetrics()
[
https://issues.apache.org/jira/browse/IGNITE-7632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Vinokurov reassigned IGNITE-7632:
---
Assignee: Pavel Vinokurov
> NPE in IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.updateIgfsMetrics()
> ---
>
> Key: IGNITE-7632
> URL: https://issues.apache.org/jira/browse/IGNITE-7632
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.3
>Reporter: Alexandr Kuramshin
>Assignee: Pavel Vinokurov
>Priority: Major
>
> Occurs on destroying cache while rebuilding indices in progress
> {noformat}
> Partition eviction failed, this can cause grid hang.
> java.lang.NullPointerException: null
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.updateIgfsMetrics(IgniteCacheOffheapManagerImpl.java:1576)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.finishRemove(IgniteCacheOffheapManagerImpl.java:1403)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.remove(IgniteCacheOffheapManagerImpl.java:1368)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.remove(GridCacheOffheapManager.java:1312)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.remove(IgniteCacheOffheapManagerImpl.java:368)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.removeValue(GridCacheMapEntry.java:3224)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheEntry.clearInternal(GridDhtCacheEntry.java:588)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLocalPartition.clearAll(GridDhtLocalPartition.java:895)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLocalPartition.tryEvict(GridDhtLocalPartition.java:753)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader$3.call(GridDhtPreloader.java:593)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader$3.call(GridDhtPreloader.java:580)
> at
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6639)
> at
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$2.body(GridClosureProcessor.java:967)
> ...
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-7652) ContinuousQueryWithTransformer needs to be documented
[ https://issues.apache.org/jira/browse/IGNITE-7652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-7652: Issue Type: Improvement (was: Bug) > ContinuousQueryWithTransformer needs to be documented > - > > Key: IGNITE-7652 > URL: https://issues.apache.org/jira/browse/IGNITE-7652 > Project: Ignite > Issue Type: Improvement > Components: cache >Affects Versions: 2.5 >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Fix For: 2.5 > > > As long as IGNITE-425 merged to master ContinuousQueryWithTransformer API > needs to be documented. Example has to be provided as well. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7653) del
[ https://issues.apache.org/jira/browse/IGNITE-7653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eduard Shangareev updated IGNITE-7653: -- Summary: del (was: Issue with saved license causes snapshot test fails) > del > --- > > Key: IGNITE-7653 > URL: https://issues.apache.org/jira/browse/IGNITE-7653 > Project: Ignite > Issue Type: Bug >Reporter: Eduard Shangareev >Assignee: Peter Ivanov >Priority: Major > > del -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7653) Issue with saved license causes snapshot test fails
[
https://issues.apache.org/jira/browse/IGNITE-7653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Shangareev updated IGNITE-7653:
--
Description: del (was: Example of fails
https://ggtc.gridgain.com/viewLog.html?buildId=1082616&tab=buildResultsDiv&buildTypeId=id8xIgniteGridGainTestsJava8_DbXSnapshotsSecurity#testNameId-6967724399324938567
{code}
org.apache.ignite.IgniteCheckedException: Snapshot feature is not allowed by
the licence.
{code}
It happens time to time. We rely on default license in tests where Ultimate
features are enabled.
But on some agents license file is presented which would be read by nodes and
because of it ultimate features would be disabled.
Another observation is that it happens only with windows-agents.)
> Issue with saved license causes snapshot test fails
> ---
>
> Key: IGNITE-7653
> URL: https://issues.apache.org/jira/browse/IGNITE-7653
> Project: Ignite
> Issue Type: Bug
>Reporter: Eduard Shangareev
>Assignee: Peter Ivanov
>Priority: Major
>
> del
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-7653) del
[ https://issues.apache.org/jira/browse/IGNITE-7653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eduard Shangareev reassigned IGNITE-7653: - Assignee: Eduard Shangareev (was: Peter Ivanov) > del > --- > > Key: IGNITE-7653 > URL: https://issues.apache.org/jira/browse/IGNITE-7653 > Project: Ignite > Issue Type: Bug >Reporter: Eduard Shangareev >Assignee: Eduard Shangareev >Priority: Major > > del -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7263) Daemon-mode Ignite node should not open&listen client port (10800)
[ https://issues.apache.org/jira/browse/IGNITE-7263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16356948#comment-16356948 ] ASF GitHub Bot commented on IGNITE-7263: GitHub user pvinokurov opened a pull request: https://github.com/apache/ignite/pull/3491 IGNITE-7263 Ignore client configuration for daemon node You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7263 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/3491.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 #3491 commit 4a1b6b874cc1b39ce3f10ada4c824dfc82c999c6 Author: pvinokurov Date: 2018-02-08T13:34:52Z IGNITE-7263 Ignore client configuration for daemon node > Daemon-mode Ignite node should not open&listen client port (10800) > -- > > Key: IGNITE-7263 > URL: https://issues.apache.org/jira/browse/IGNITE-7263 > Project: Ignite > Issue Type: Bug > Components: visor >Affects Versions: 2.1 >Reporter: Alexey Popov >Assignee: Pavel Vinokurov >Priority: Minor > Labels: core > > When I run a Visor console with default configuration file it opens a default > port (10800) for ODBC driver connection (and for thin JDBC, and for new > "thin" client). > Then I run several Ignite nodes. > So after that, the ODBC driver with default settings goes directly to a Visor > (daemon-mode Ignite) and does not able to get any data (daemon-mode Ignite > does not keep any data) > It is better to avoid such situation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-7653) Issue with saved license causes snapshot test fails
Eduard Shangareev created IGNITE-7653:
-
Summary: Issue with saved license causes snapshot test fails
Key: IGNITE-7653
URL: https://issues.apache.org/jira/browse/IGNITE-7653
Project: Ignite
Issue Type: Bug
Reporter: Eduard Shangareev
Assignee: Peter Ivanov
Example of fails
https://ggtc.gridgain.com/viewLog.html?buildId=1082616&tab=buildResultsDiv&buildTypeId=id8xIgniteGridGainTestsJava8_DbXSnapshotsSecurity#testNameId-6967724399324938567
{code}
org.apache.ignite.IgniteCheckedException: Snapshot feature is not allowed by
the licence.
{code}
It happens time to time. We rely on default license in tests where Ultimate
features are enabled.
But on some agents license file is presented which would be read by nodes and
because of it ultimate features would be disabled.
Another observation is that it happens only with windows-agents.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7540) Sequential checkpoints cause overwrite of already cleaned & freed offheap page
[
https://issues.apache.org/jira/browse/IGNITE-7540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16356941#comment-16356941
]
ASF GitHub Bot commented on IGNITE-7540:
GitHub user Jokser opened a pull request:
https://github.com/apache/ignite/pull/3490
IGNITE-7540 Sequential checkpoints cause overwrite of already cleaned &
freed offheap page
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-7540
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/3490.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 #3490
commit 17bdf9459a3234eefbd379506a1d0895cd88d3a5
Author: Pavel Kovalenko
Date: 2018-02-08T13:32:40Z
IGNITE-7540 Prevent page memory metadata corruption during checkpoint and
group destroying.
> Sequential checkpoints cause overwrite of already cleaned & freed offheap page
> --
>
> Key: IGNITE-7540
> URL: https://issues.apache.org/jira/browse/IGNITE-7540
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Affects Versions: 2.4
>Reporter: Ilya Kasnacheev
>Assignee: Pavel Kovalenko
>Priority: Major
> Attachments: IgnitePdsDestroyCacheTest.java
>
>
> The sequence of events as follows:
> in GridCacheProcessor.onExchangeDone(),
> {color:#660e7a}sharedCtx{color}.database().waitForCheckpoint({color:#008000}"caches
> stop"{color}) is peformed and then cache is destroyed and all its pages are
> freed and cleared asynchronously.
> However, it is entirely possible that after waitForCheckpoint(), next
> checkpoint will start immediately. It is typical when a lot of data being
> loaded into Ignite, leading to rapid checkpoint buffer depletion, as well as
> with artificially increased checkpoint frequency, as used in reproducer.
> Then, checkpointer will save (overwrite) metadata page:
> {code:java}
> at
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.writeUnlockPage(PageMemoryImpl.java:1330)
> at
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.writeUnlock(PageMemoryImpl.java:428)
> at
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.writeUnlock(PageMemoryImpl.java:422)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager.saveStoreMetadata(GridCacheOffheapManager.java:375)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager.onCheckpointBegin(GridCacheOffheapManager.java:163)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.markCheckpointBegin(GridCacheDatabaseSharedManager.java:2309)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.doCheckpoint(GridCacheDatabaseSharedManager.java:2088)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.body(GridCacheDatabaseSharedManager.java:2013)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:748){code}
> This will happen after cache is already destroyed and even after the page is
> already zeroed by PageMemoryImpl$ClearSegmentRunnable.run().
> Then, some new cache is being created, and in
> GridCacheOffheapManager$GridCacheDataStore.getOrAllocatePartitionMetas(),
> pageMem.acquirePage() will return this page, expected zeroed, but actually
> containing metadata for old cache's partition. Then, type ==
> PageIO.T_PART_META check will return true and the following exception is
> issued, leading to cache state inconsistency and data loss:
> {code:java}
> Caused by: java.lang.IllegalStateException: Failed to get page IO instance
> (page content is corrupted)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.io.IOVersions.forVersion(IOVersions.java:83)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.io.IOVersions.forPage(IOVersions.java:95)
> at
> org.apache.ignite.internal.processors.cache.persistence.freelist.PagesList.init(PagesList.java:175)
> at
> org.apache.ignite.internal.processors.cache.persistence.freelist.FreeListImpl.(FreeListImpl.java:370)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore$1.(GridCacheOffheapManager.java:932)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore
[jira] [Updated] (IGNITE-7430) Thin client Java API - cache putAll/getAll
[ https://issues.apache.org/jira/browse/IGNITE-7430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kukushkin updated IGNITE-7430: - Environment: (was: Implement cache putAll/getAll thin client Java API including unit and system tests and samples. Cache getAll(keys: Set): Map getAll ) > Thin client Java API - cache putAll/getAll > -- > > Key: IGNITE-7430 > URL: https://issues.apache.org/jira/browse/IGNITE-7430 > Project: Ignite > Issue Type: Sub-task > Environment: >Reporter: Alexey Kukushkin >Assignee: Alexey Kukushkin >Priority: Major > Labels: data, java, thin > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-7652) ContinuousQueryWithTransformer needs to be documented
Nikolay Izhikov created IGNITE-7652: --- Summary: ContinuousQueryWithTransformer needs to be documented Key: IGNITE-7652 URL: https://issues.apache.org/jira/browse/IGNITE-7652 Project: Ignite Issue Type: Bug Components: cache Affects Versions: 2.5 Reporter: Nikolay Izhikov Assignee: Nikolay Izhikov Fix For: 2.5 As long as IGNITE-425 merged to master ContinuousQueryWithTransformer API needs to be documented. Example has to be provided as well. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-7428) Thin client Java API - cache open/getName/getConfiguration/size
[ https://issues.apache.org/jira/browse/IGNITE-7428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kukushkin resolved IGNITE-7428. -- Resolution: Fixed > Thin client Java API - cache open/getName/getConfiguration/size > --- > > Key: IGNITE-7428 > URL: https://issues.apache.org/jira/browse/IGNITE-7428 > Project: Ignite > Issue Type: Sub-task >Reporter: Alexey Kukushkin >Assignee: Alexey Kukushkin >Priority: Major > Labels: data, java, thin > > Implement cache open/getName/getConfiguration/close/size thin client Java API > including unit and system tests and samples. > Cache > getName(): String > getConfiguration(clazz): Configuration > size(modes: CachePeekMode...) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-7430) Thin client Java API - cache putAll/getAll
[ https://issues.apache.org/jira/browse/IGNITE-7430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kukushkin reassigned IGNITE-7430: Assignee: Alexey Kukushkin > Thin client Java API - cache putAll/getAll > -- > > Key: IGNITE-7430 > URL: https://issues.apache.org/jira/browse/IGNITE-7430 > Project: Ignite > Issue Type: Sub-task > Environment: Implement cache putAll/getAll thin client Java API > including unit and system tests and samples. > Cache > getAll(keys: Set): Map > getAll > >Reporter: Alexey Kukushkin >Assignee: Alexey Kukushkin >Priority: Major > Labels: data, java, thin > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-6625) JDBC thin: support SSL connection to Ignite node
[ https://issues.apache.org/jira/browse/IGNITE-6625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16356888#comment-16356888 ] ASF GitHub Bot commented on IGNITE-6625: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/3233 > JDBC thin: support SSL connection to Ignite node > > > Key: IGNITE-6625 > URL: https://issues.apache.org/jira/browse/IGNITE-6625 > Project: Ignite > Issue Type: Improvement > Components: jdbc >Affects Versions: 2.2 >Reporter: Taras Ledkov >Assignee: Taras Ledkov >Priority: Major > Fix For: 2.5 > > > SSL connection must be supported for JDBC thin driver. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-7398) InstanceNotFoundException appears in the log when a cache is closed and MBeans are disabled
[ https://issues.apache.org/jira/browse/IGNITE-7398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Vinokurov reassigned IGNITE-7398: --- Assignee: Pavel Vinokurov > InstanceNotFoundException appears in the log when a cache is closed and > MBeans are disabled > --- > > Key: IGNITE-7398 > URL: https://issues.apache.org/jira/browse/IGNITE-7398 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.4 >Reporter: Stanislav Lukyanov >Assignee: Pavel Vinokurov >Priority: Minor > > If IGNITE_MBEANS_DISABLED is set to true, whenever a cache is started the > following error is logged: > javax.management.InstanceNotFoundException: > org.apache:clsLdr=18b4aac2,igniteInstanceName=mbeans.GridMBeanDisableSelfTest0,group=Cache > groups,name=MyCache > at > com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean(DefaultMBeanServerInterceptor.java:1095) > at > com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.exclusiveUnregisterMBean(DefaultMBeanServerInterceptor.java:427) > at > com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.unregisterMBean(DefaultMBeanServerInterceptor.java:415) > at > com.sun.jmx.mbeanserver.JmxMBeanServer.unregisterMBean(JmxMBeanServer.java:546) > at > org.apache.ignite.internal.processors.cache.GridCacheProcessor.cleanup(GridCacheProcessor.java:606) > at > org.apache.ignite.internal.processors.cache.GridCacheProcessor.stopCacheGroup(GridCacheProcessor.java:2264) > at > org.apache.ignite.internal.processors.cache.GridCacheProcessor.stopCacheGroup(GridCacheProcessor.java:2253) > at > org.apache.ignite.internal.processors.cache.GridCacheProcessor.stopCaches(GridCacheProcessor.java:907) > at > org.apache.ignite.internal.processors.cache.GridCacheProcessor.stop(GridCacheProcessor.java:872) > at org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:2316) > at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:2182) > at > org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2512) > at > org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2475) > at org.apache.ignite.internal.IgnitionEx.stop(IgnitionEx.java:362) > at org.apache.ignite.Ignition.stop(Ignition.java:224) > at org.apache.ignite.internal.IgniteKernal.close(IgniteKernal.java:3509) > at > org.apache.ignite.util.mbeans.GridMBeanDisableSelfTest.testCorrectMBeanInfo(GridMBeanDisableSelfTest.java:101) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at junit.framework.TestCase.runTest(TestCase.java:176) > at > org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2001) > at > org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:133) > at > org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1916) > at java.lang.Thread.run(Thread.java:748) > That's because GridCacheProcessor::cleanup unconditionally attempts to > unregister cache's MBean, not checking whether or not the cache actually has > an MBean registered for it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-7445) Thin client: SQL batching
[
https://issues.apache.org/jira/browse/IGNITE-7445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Daradur reassigned IGNITE-7445:
--
Assignee: Vyacheslav Daradur
> Thin client: SQL batching
> -
>
> Key: IGNITE-7445
> URL: https://issues.apache.org/jira/browse/IGNITE-7445
> Project: Ignite
> Issue Type: Improvement
> Components: thin client
>Affects Versions: 2.4
>Reporter: Pavel Tupitsyn
>Assignee: Vyacheslav Daradur
>Priority: Major
> Fix For: 2.5
>
>
> SQL batching allows executing multiple SQL queries in one client request,
> improving performance.
> See how JDBC does it in {{JdbcBatchExecuteRequest}}, add a similar thing in
> Thin Client protocol.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-2093) Add support for scan near cache to VisorQueryTask
[ https://issues.apache.org/jira/browse/IGNITE-2093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko reassigned IGNITE-2093: - Assignee: Pavel Konstantinov (was: Vasiliy Sisko) > Add support for scan near cache to VisorQueryTask > - > > Key: IGNITE-2093 > URL: https://issues.apache.org/jira/browse/IGNITE-2093 > Project: Ignite > Issue Type: Task > Components: cache >Affects Versions: 1.5.0.final >Reporter: Alexey Kuznetsov >Assignee: Pavel Konstantinov >Priority: Major > > VisorQueryTask can execute EXPLAIN, SQL and SCAN queries, but it is not so > hard add support for SCAN NEAR CACHE "pseudo query" that will work on some > node locally and will return > ccache.localEntries(CachePeekMode.NEAR).iterator(). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-2093) Add support for scan near cache to VisorQueryTask
[ https://issues.apache.org/jira/browse/IGNITE-2093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16356791#comment-16356791 ] Vasiliy Sisko commented on IGNITE-2093: --- Implemented -near argument of cache scan command. Implemented selection of node when -id and -id8 arguments are not specified. > Add support for scan near cache to VisorQueryTask > - > > Key: IGNITE-2093 > URL: https://issues.apache.org/jira/browse/IGNITE-2093 > Project: Ignite > Issue Type: Task > Components: cache >Affects Versions: 1.5.0.final >Reporter: Alexey Kuznetsov >Assignee: Vasiliy Sisko >Priority: Major > > VisorQueryTask can execute EXPLAIN, SQL and SCAN queries, but it is not so > hard add support for SCAN NEAR CACHE "pseudo query" that will work on some > node locally and will return > ccache.localEntries(CachePeekMode.NEAR).iterator(). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7651) Assertion error on cache start while reading meta pages
[
https://issues.apache.org/jira/browse/IGNITE-7651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Shangareev updated IGNITE-7651:
--
Summary: Assertion error on cache start while reading meta pages (was:
Assertion error on cache start)
> Assertion error on cache start while reading meta pages
> ---
>
> Key: IGNITE-7651
> URL: https://issues.apache.org/jira/browse/IGNITE-7651
> Project: Ignite
> Issue Type: Bug
>Reporter: Eduard Shangareev
>Priority: Critical
>
> We recently have added assertion. Now it has found issue with start cache
> after restart.
> {code:java}
> java.lang.AssertionError: calculatedOffset=16384, allocated=8192,
> headerSize=4096
> at
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStore.read(FilePageStore.java:341)
> at
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.read(FilePageStoreManager.java:322)
> at
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.read(FilePageStoreManager.java:306)
> at
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.acquirePage(PageMemoryImpl.java:658)
> at
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.acquirePage(PageMemoryImpl.java:578)
> at
> org.apache.ignite.internal.processors.cache.persistence.DataStructure.acquirePage(DataStructure.java:130)
> at
> org.apache.ignite.internal.processors.cache.persistence.freelist.PagesList.init(PagesList.java:167)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.reuse.ReuseListImpl.(ReuseListImpl.java:56)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager.initDataStructures(GridCacheOffheapManager.java:103)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.start(IgniteCacheOffheapManagerImpl.java:131)
> at
> org.apache.ignite.internal.processors.cache.CacheGroupContext.start(CacheGroupContext.java:893)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCacheGroup(GridCacheProcessor.java:1979)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1869)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCachesOnLocalJoin(GridCacheProcessor.java:1759)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.initCachesOnLocalJoin(GridDhtPartitionsExchangeFuture.java:769)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:651)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2337)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:748)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-7651) Assertion error on cache start
[
https://issues.apache.org/jira/browse/IGNITE-7651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Shangareev updated IGNITE-7651:
--
Description:
We recently have added assertion. Now it has found issue with start cache after
restart.
{code:java}
java.lang.AssertionError: calculatedOffset=16384, allocated=8192,
headerSize=4096
at
org.apache.ignite.internal.processors.cache.persistence.file.FilePageStore.read(FilePageStore.java:341)
at
org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.read(FilePageStoreManager.java:322)
at
org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.read(FilePageStoreManager.java:306)
at
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.acquirePage(PageMemoryImpl.java:658)
at
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.acquirePage(PageMemoryImpl.java:578)
at
org.apache.ignite.internal.processors.cache.persistence.DataStructure.acquirePage(DataStructure.java:130)
at
org.apache.ignite.internal.processors.cache.persistence.freelist.PagesList.init(PagesList.java:167)
at
org.apache.ignite.internal.processors.cache.persistence.tree.reuse.ReuseListImpl.(ReuseListImpl.java:56)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager.initDataStructures(GridCacheOffheapManager.java:103)
at
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.start(IgniteCacheOffheapManagerImpl.java:131)
at
org.apache.ignite.internal.processors.cache.CacheGroupContext.start(CacheGroupContext.java:893)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCacheGroup(GridCacheProcessor.java:1979)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1869)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCachesOnLocalJoin(GridCacheProcessor.java:1759)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.initCachesOnLocalJoin(GridDhtPartitionsExchangeFuture.java:769)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:651)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2337)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:748)
{code}
was:
We recently have added assertion. No
{code:java}
java.lang.AssertionError: calculatedOffset=16384, allocated=8192,
headerSize=4096
at
org.apache.ignite.internal.processors.cache.persistence.file.FilePageStore.read(FilePageStore.java:341)
at
org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.read(FilePageStoreManager.java:322)
at
org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.read(FilePageStoreManager.java:306)
at
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.acquirePage(PageMemoryImpl.java:658)
at
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.acquirePage(PageMemoryImpl.java:578)
at
org.apache.ignite.internal.processors.cache.persistence.DataStructure.acquirePage(DataStructure.java:130)
at
org.apache.ignite.internal.processors.cache.persistence.freelist.PagesList.init(PagesList.java:167)
at
org.apache.ignite.internal.processors.cache.persistence.tree.reuse.ReuseListImpl.(ReuseListImpl.java:56)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager.initDataStructures(GridCacheOffheapManager.java:103)
at
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.start(IgniteCacheOffheapManagerImpl.java:131)
at
org.apache.ignite.internal.processors.cache.CacheGroupContext.start(CacheGroupContext.java:893)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCacheGroup(GridCacheProcessor.java:1979)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1869)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCachesOnLocalJoin(GridCacheProcessor.java:1759)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.initCachesOnLocalJoin(GridDhtPartitionsExchangeFuture.java:769)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:651)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager
[jira] [Updated] (IGNITE-7651) Assertion error on cache start
[
https://issues.apache.org/jira/browse/IGNITE-7651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Shangareev updated IGNITE-7651:
--
Priority: Critical (was: Major)
> Assertion error on cache start
> --
>
> Key: IGNITE-7651
> URL: https://issues.apache.org/jira/browse/IGNITE-7651
> Project: Ignite
> Issue Type: Bug
>Reporter: Eduard Shangareev
>Priority: Critical
>
> {code:java}
> java.lang.AssertionError: calculatedOffset=16384, allocated=8192,
> headerSize=4096
> at
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStore.read(FilePageStore.java:341)
> at
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.read(FilePageStoreManager.java:322)
> at
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.read(FilePageStoreManager.java:306)
> at
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.acquirePage(PageMemoryImpl.java:658)
> at
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.acquirePage(PageMemoryImpl.java:578)
> at
> org.apache.ignite.internal.processors.cache.persistence.DataStructure.acquirePage(DataStructure.java:130)
> at
> org.apache.ignite.internal.processors.cache.persistence.freelist.PagesList.init(PagesList.java:167)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.reuse.ReuseListImpl.(ReuseListImpl.java:56)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager.initDataStructures(GridCacheOffheapManager.java:103)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.start(IgniteCacheOffheapManagerImpl.java:131)
> at
> org.apache.ignite.internal.processors.cache.CacheGroupContext.start(CacheGroupContext.java:893)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCacheGroup(GridCacheProcessor.java:1979)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1869)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCachesOnLocalJoin(GridCacheProcessor.java:1759)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.initCachesOnLocalJoin(GridDhtPartitionsExchangeFuture.java:769)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:651)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2337)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:748)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-7651) Assertion error on cache start
Eduard Shangareev created IGNITE-7651:
-
Summary: Assertion error on cache start
Key: IGNITE-7651
URL: https://issues.apache.org/jira/browse/IGNITE-7651
Project: Ignite
Issue Type: Bug
Reporter: Eduard Shangareev
{code:java}
java.lang.AssertionError: calculatedOffset=16384, allocated=8192,
headerSize=4096
at
org.apache.ignite.internal.processors.cache.persistence.file.FilePageStore.read(FilePageStore.java:341)
at
org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.read(FilePageStoreManager.java:322)
at
org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.read(FilePageStoreManager.java:306)
at
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.acquirePage(PageMemoryImpl.java:658)
at
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.acquirePage(PageMemoryImpl.java:578)
at
org.apache.ignite.internal.processors.cache.persistence.DataStructure.acquirePage(DataStructure.java:130)
at
org.apache.ignite.internal.processors.cache.persistence.freelist.PagesList.init(PagesList.java:167)
at
org.apache.ignite.internal.processors.cache.persistence.tree.reuse.ReuseListImpl.(ReuseListImpl.java:56)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager.initDataStructures(GridCacheOffheapManager.java:103)
at
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.start(IgniteCacheOffheapManagerImpl.java:131)
at
org.apache.ignite.internal.processors.cache.CacheGroupContext.start(CacheGroupContext.java:893)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCacheGroup(GridCacheProcessor.java:1979)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1869)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCachesOnLocalJoin(GridCacheProcessor.java:1759)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.initCachesOnLocalJoin(GridDhtPartitionsExchangeFuture.java:769)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:651)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2337)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:748)
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-7651) Assertion error on cache start
[
https://issues.apache.org/jira/browse/IGNITE-7651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Shangareev updated IGNITE-7651:
--
Description:
We recently have added assertion. No
{code:java}
java.lang.AssertionError: calculatedOffset=16384, allocated=8192,
headerSize=4096
at
org.apache.ignite.internal.processors.cache.persistence.file.FilePageStore.read(FilePageStore.java:341)
at
org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.read(FilePageStoreManager.java:322)
at
org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.read(FilePageStoreManager.java:306)
at
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.acquirePage(PageMemoryImpl.java:658)
at
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.acquirePage(PageMemoryImpl.java:578)
at
org.apache.ignite.internal.processors.cache.persistence.DataStructure.acquirePage(DataStructure.java:130)
at
org.apache.ignite.internal.processors.cache.persistence.freelist.PagesList.init(PagesList.java:167)
at
org.apache.ignite.internal.processors.cache.persistence.tree.reuse.ReuseListImpl.(ReuseListImpl.java:56)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager.initDataStructures(GridCacheOffheapManager.java:103)
at
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.start(IgniteCacheOffheapManagerImpl.java:131)
at
org.apache.ignite.internal.processors.cache.CacheGroupContext.start(CacheGroupContext.java:893)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCacheGroup(GridCacheProcessor.java:1979)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1869)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCachesOnLocalJoin(GridCacheProcessor.java:1759)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.initCachesOnLocalJoin(GridDhtPartitionsExchangeFuture.java:769)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:651)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2337)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:748)
{code}
was:
{code:java}
java.lang.AssertionError: calculatedOffset=16384, allocated=8192,
headerSize=4096
at
org.apache.ignite.internal.processors.cache.persistence.file.FilePageStore.read(FilePageStore.java:341)
at
org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.read(FilePageStoreManager.java:322)
at
org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.read(FilePageStoreManager.java:306)
at
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.acquirePage(PageMemoryImpl.java:658)
at
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.acquirePage(PageMemoryImpl.java:578)
at
org.apache.ignite.internal.processors.cache.persistence.DataStructure.acquirePage(DataStructure.java:130)
at
org.apache.ignite.internal.processors.cache.persistence.freelist.PagesList.init(PagesList.java:167)
at
org.apache.ignite.internal.processors.cache.persistence.tree.reuse.ReuseListImpl.(ReuseListImpl.java:56)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager.initDataStructures(GridCacheOffheapManager.java:103)
at
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.start(IgniteCacheOffheapManagerImpl.java:131)
at
org.apache.ignite.internal.processors.cache.CacheGroupContext.start(CacheGroupContext.java:893)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCacheGroup(GridCacheProcessor.java:1979)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1869)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCachesOnLocalJoin(GridCacheProcessor.java:1759)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.initCachesOnLocalJoin(GridDhtPartitionsExchangeFuture.java:769)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:651)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2337)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:1
[jira] [Updated] (IGNITE-7650) Web Console: Rework signin page.
[ https://issues.apache.org/jira/browse/IGNITE-7650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kalinin updated IGNITE-7650: -- Fix Version/s: 2.5 > Web Console: Rework signin page. > > > Key: IGNITE-7650 > URL: https://issues.apache.org/jira/browse/IGNITE-7650 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Alexander Kalinin >Assignee: Alexander Kalinin >Priority: Major > Fix For: 2.5 > > > * Add landing screen on signin page > * Refactor signin controller to component. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-7650) Web Console: Rework signin page.
Alexander Kalinin created IGNITE-7650: - Summary: Web Console: Rework signin page. Key: IGNITE-7650 URL: https://issues.apache.org/jira/browse/IGNITE-7650 Project: Ignite Issue Type: Improvement Components: wizards Reporter: Alexander Kalinin Assignee: Alexander Kalinin * Add landing screen on signin page * Refactor signin controller to component. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7393) Apache Ignite delivery in RPM / DEV packages
[ https://issues.apache.org/jira/browse/IGNITE-7393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Ivanov updated IGNITE-7393: - Description: Aggregation task for first stage of preparing Apache Ignite delivery through RPM / DEB packages. Steps: # Prepare source-based package build procedures for RPM and DEB. # Introduce these build procedures to Release Apache Ignite task in PublicTC. # Introduce upload / update schemes. was: Aggregation task for first stage of preparing Apache Ignite delivery through RPM / DEB packages. Steps: # Prepare source-based package build procedures for RPM and DEB. # Introduce these build procedures to Release Apache Ignite task in PublicTC. > Apache Ignite delivery in RPM / DEV packages > > > Key: IGNITE-7393 > URL: https://issues.apache.org/jira/browse/IGNITE-7393 > Project: Ignite > Issue Type: Task >Reporter: Peter Ivanov >Assignee: Peter Ivanov >Priority: Critical > Fix For: 2.5 > > > Aggregation task for first stage of preparing Apache Ignite delivery through > RPM / DEB packages. > Steps: > # Prepare source-based package build procedures for RPM and DEB. > # Introduce these build procedures to Release Apache Ignite task in PublicTC. > # Introduce upload / update schemes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-7649) transformer instance is not properly transfers into SqlQuery request.
[
https://issues.apache.org/jira/browse/IGNITE-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16356718#comment-16356718
]
Andrew Mashenkov edited comment on IGNITE-7649 at 2/8/18 9:43 AM:
--
[~zstan]
Do you mean ScanQuery?
Looks like duplicate of IGNITE-5804
was (Author: amashenkov):
[~zstan]
Do you mean ScanQuery?
Looks like duplicate of IGNITE-4918
> transformer instance is not properly transfers into SqlQuery request.
> -
>
> Key: IGNITE-7649
> URL: https://issues.apache.org/jira/browse/IGNITE-7649
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.3
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
> Fix For: 2.5
>
>
> to reproduce this case we need some simple changes in existing test:
> GridCacheQueryTransformerSelfTest#testKeepBinary
> change:
> {code:java}
> List res = binaryCache.query(new ScanQuery(),
> transformer).getAll();{code}
> into:
> {code:java}
> List res = binaryCache.query(new ScanQuery BinaryObject>().setPageSize(2), transformer).getAll();{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-7647) Apache Ignite RPM packages
[ https://issues.apache.org/jira/browse/IGNITE-7647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Ivanov updated IGNITE-7647: - Priority: Critical (was: Major) > Apache Ignite RPM packages > -- > > Key: IGNITE-7647 > URL: https://issues.apache.org/jira/browse/IGNITE-7647 > Project: Ignite > Issue Type: Improvement >Reporter: Peter Ivanov >Assignee: Peter Ivanov >Priority: Critical > Fix For: 2.5 > > > # Repack RPM specification to: > #* be able to build package from source code > #* divide single package into multiple packages (core + optional). > # Introduce process of PRM building in release procedure. > # Introduce repository update scheme. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7393) Apache Ignite delivery in RPM / DEV packages
[ https://issues.apache.org/jira/browse/IGNITE-7393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Ivanov updated IGNITE-7393: - Description: Aggregation task for first stage of preparing Apache Ignite delivery through RPM / DEB packages. Steps: # Prepare source-based package build procedures for RPM and DEB. # Introduce these build procedures to Release Apache Ignite task in PublicTC. was: Aggregation task for first stage of preparing Apache Ignite delivery through RPM / DEB packages. Steps: # Prepare source-based package build procedures for RPM and DEB. # Introduce these build procedures to Release Apache Ignite task in PublicTC (including generation of RPM / DEB repositories structure for deployment to apache.org/dist). # Introduce PPA DEB repository for Apache Ignite. > Apache Ignite delivery in RPM / DEV packages > > > Key: IGNITE-7393 > URL: https://issues.apache.org/jira/browse/IGNITE-7393 > Project: Ignite > Issue Type: Task >Reporter: Peter Ivanov >Assignee: Peter Ivanov >Priority: Critical > Fix For: 2.5 > > > Aggregation task for first stage of preparing Apache Ignite delivery through > RPM / DEB packages. > Steps: > # Prepare source-based package build procedures for RPM and DEB. > # Introduce these build procedures to Release Apache Ignite task in PublicTC. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7649) transformer instance is not properly transfers into SqlQuery request.
[
https://issues.apache.org/jira/browse/IGNITE-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16356718#comment-16356718
]
Andrew Mashenkov commented on IGNITE-7649:
--
[~zstan]
Do you mean ScanQuery?
Looks like duplicate of IGNITE-4918
> transformer instance is not properly transfers into SqlQuery request.
> -
>
> Key: IGNITE-7649
> URL: https://issues.apache.org/jira/browse/IGNITE-7649
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.3
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
> Fix For: 2.5
>
>
> to reproduce this case we need some simple changes in existing test:
> GridCacheQueryTransformerSelfTest#testKeepBinary
> change:
> {code:java}
> List res = binaryCache.query(new ScanQuery(),
> transformer).getAll();{code}
> into:
> {code:java}
> List res = binaryCache.query(new ScanQuery BinaryObject>().setPageSize(2), transformer).getAll();{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-7649) transformer instance is not properly transfers into SqlQuery request.
Stanilovsky Evgeny created IGNITE-7649:
--
Summary: transformer instance is not properly transfers into
SqlQuery request.
Key: IGNITE-7649
URL: https://issues.apache.org/jira/browse/IGNITE-7649
Project: Ignite
Issue Type: Bug
Components: cache
Affects Versions: 2.3
Reporter: Stanilovsky Evgeny
Assignee: Stanilovsky Evgeny
Fix For: 2.5
to reproduce this case we need some simple changes in existing test:
GridCacheQueryTransformerSelfTest#testKeepBinary
change:
{code:java}
List res = binaryCache.query(new ScanQuery(),
transformer).getAll();{code}
into:
{code:java}
List res = binaryCache.query(new ScanQuery().setPageSize(2), transformer).getAll();{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-7108) Apache Ignite DEB packages
[ https://issues.apache.org/jira/browse/IGNITE-7108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Ivanov updated IGNITE-7108: - Description: # Prepare source-based build of DEB package (using architecture from RPM package). # Introduce process of PRM building in release procedure. # Introduce repository delivery / update scheme. was:Pack apache-ignite into DEB package for distribution through DEB-based Linux distros (Ubuntu / Debian, etc.) > Apache Ignite DEB packages > -- > > Key: IGNITE-7108 > URL: https://issues.apache.org/jira/browse/IGNITE-7108 > Project: Ignite > Issue Type: New Feature > Components: binary >Reporter: Peter Ivanov >Assignee: Peter Ivanov >Priority: Critical > Labels: important > Fix For: 2.5 > > > # Prepare source-based build of DEB package (using architecture from RPM > package). > # Introduce process of PRM building in release procedure. > # Introduce repository delivery / update scheme. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7647) Apache Ignite RPM packages
[ https://issues.apache.org/jira/browse/IGNITE-7647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Ivanov updated IGNITE-7647: - Fix Version/s: 2.5 > Apache Ignite RPM packages > -- > > Key: IGNITE-7647 > URL: https://issues.apache.org/jira/browse/IGNITE-7647 > Project: Ignite > Issue Type: Improvement >Reporter: Peter Ivanov >Assignee: Peter Ivanov >Priority: Major > Fix For: 2.5 > > > # Repack RPM specification to: > #* be able to build package from source code > #* divide single package into multiple packages (core + optional). > # Introduce process of PRM building in release procedure. > # Introduce repository update scheme. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7647) Apache Ignite RPM packages
[ https://issues.apache.org/jira/browse/IGNITE-7647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Ivanov updated IGNITE-7647: - Issue Type: Improvement (was: Task) > Apache Ignite RPM packages > -- > > Key: IGNITE-7647 > URL: https://issues.apache.org/jira/browse/IGNITE-7647 > Project: Ignite > Issue Type: Improvement >Reporter: Peter Ivanov >Assignee: Peter Ivanov >Priority: Major > > # Repack RPM specification to: > #* be able to build package from source code > #* divide single package into multiple packages (core + optional). > # Introduce process of PRM building in release procedure. > # Introduce repository update scheme. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7647) Apache Ignite RPM packages
[ https://issues.apache.org/jira/browse/IGNITE-7647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Ivanov updated IGNITE-7647: - Description: # Repack RPM specification to: #* be able to build package from source code #* divide single package into multiple packages (core + optional). # Introduce process of PRM building in release procedure. # Introduce repository update scheme. was: # Repack RPM specification to: #* be able to build package from source code #* divide single package into multiple packages (core + optional). # Prepare repository update scheme. > Apache Ignite RPM packages > -- > > Key: IGNITE-7647 > URL: https://issues.apache.org/jira/browse/IGNITE-7647 > Project: Ignite > Issue Type: Task >Reporter: Peter Ivanov >Assignee: Peter Ivanov >Priority: Major > > # Repack RPM specification to: > #* be able to build package from source code > #* divide single package into multiple packages (core + optional). > # Introduce process of PRM building in release procedure. > # Introduce repository update scheme. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7647) Apache Ignite RPM packages
[ https://issues.apache.org/jira/browse/IGNITE-7647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Ivanov updated IGNITE-7647: - Description: # Repack RPM specification to: #* be able to build package from source code #* divide single package into multiple packages (core + optional). # Prepare repository update scheme. was: Repack RPM specification to: * be able to build package from source code * divide single package into multiple packages (core + optional). > Apache Ignite RPM packages > -- > > Key: IGNITE-7647 > URL: https://issues.apache.org/jira/browse/IGNITE-7647 > Project: Ignite > Issue Type: Task >Reporter: Peter Ivanov >Assignee: Peter Ivanov >Priority: Major > > # Repack RPM specification to: > #* be able to build package from source code > #* divide single package into multiple packages (core + optional). > # Prepare repository update scheme. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-7648) Revert IGNITE_ENABLE_FORCIBLE_NODE_KILL system property.
Alexei Scherbakov created IGNITE-7648: - Summary: Revert IGNITE_ENABLE_FORCIBLE_NODE_KILL system property. Key: IGNITE-7648 URL: https://issues.apache.org/jira/browse/IGNITE-7648 Project: Ignite Issue Type: Improvement Affects Versions: 2.3 Reporter: Alexei Scherbakov Assignee: Alexei Scherbakov Fix For: 2.5 IGNITE_ENABLE_FORCIBLE_NODE_KILL system property was introduced in IGNITE-5718 as a way to prevent unnecessary node drops in case of short network problems. I suppose it's wrong decision to fix it in such way. We had faced some issues in our production due to lack of automatic kicking of ill-behaving nodes (on example, hanging due to long GC pauses) until we realised the necessity of changing default behavior via property. Right solution is to kick nodes only if failure threshold is reached. Such behavior should be always enabled. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-7647) Apache Ignite RPM packages
Peter Ivanov created IGNITE-7647: Summary: Apache Ignite RPM packages Key: IGNITE-7647 URL: https://issues.apache.org/jira/browse/IGNITE-7647 Project: Ignite Issue Type: Task Reporter: Peter Ivanov Assignee: Peter Ivanov Repack RPM specification to: * be able to build package from source code * divide single package into multiple packages (core + optional). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-6625) JDBC thin: support SSL connection to Ignite node
[ https://issues.apache.org/jira/browse/IGNITE-6625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16356680#comment-16356680 ] Taras Ledkov commented on IGNITE-6625: -- [~isapego], please merge the patch to master. > JDBC thin: support SSL connection to Ignite node > > > Key: IGNITE-6625 > URL: https://issues.apache.org/jira/browse/IGNITE-6625 > Project: Ignite > Issue Type: Improvement > Components: jdbc >Affects Versions: 2.2 >Reporter: Taras Ledkov >Assignee: Taras Ledkov >Priority: Major > Fix For: 2.5 > > > SSL connection must be supported for JDBC thin driver. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7512) Variable updated should be checked for null before invocation of ctx.validateKeyAndValue(entry.key(), updated) in GridDhtAtomicCache.updateWithBatch
[ https://issues.apache.org/jira/browse/IGNITE-7512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16356677#comment-16356677 ] Sergey Kalashnikov commented on IGNITE-7512: [~agoncharuk], Could you please review this small fix? TC seems to be OK. https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&branch_IgniteTests24Java8=pull%2F3429%2Fhead > Variable updated should be checked for null before invocation of > ctx.validateKeyAndValue(entry.key(), updated) in > GridDhtAtomicCache.updateWithBatch > > > Key: IGNITE-7512 > URL: https://issues.apache.org/jira/browse/IGNITE-7512 > Project: Ignite > Issue Type: Bug >Reporter: Evgenii Zhuravlev >Assignee: Sergey Kalashnikov >Priority: Major > Fix For: 2.5 > > > Or it could lead to the NPE -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-6625) JDBC thin: support SSL connection to Ignite node
[ https://issues.apache.org/jira/browse/IGNITE-6625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16356676#comment-16356676 ] Igor Seliverstov commented on IGNITE-6625: -- [~tledkov-gridgain], looks OK to me. > JDBC thin: support SSL connection to Ignite node > > > Key: IGNITE-6625 > URL: https://issues.apache.org/jira/browse/IGNITE-6625 > Project: Ignite > Issue Type: Improvement > Components: jdbc >Affects Versions: 2.2 >Reporter: Taras Ledkov >Assignee: Taras Ledkov >Priority: Major > Fix For: 2.5 > > > SSL connection must be supported for JDBC thin driver. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-7646) OSGI tests fail to unlock build directory causing following builds to fail to start
Peter Ivanov created IGNITE-7646:
Summary: OSGI tests fail to unlock build directory causing
following builds to fail to start
Key: IGNITE-7646
URL: https://issues.apache.org/jira/browse/IGNITE-7646
Project: Ignite
Issue Type: Task
Reporter: Peter Ivanov
After running test suite [Ignite Tests 2.4+ \[Java 8\] Ignite
OSGi|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_IgniteOSGi]
under Windows based agent, following builds fail to start with error
{code}
[16:30:24]Failed to delete file:
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\data\cache\bundle1\version0.0\bundle.jar
[16:30:24]Failed to delete file:
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\data\cache\bundle2\version0.0\bundle.jar
[16:30:24]Failed to delete file:
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\data\cache\bundle3\version0.0\bundle.jar
[16:30:24]Failed to delete file:
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\data\cache\bundle4\version0.0\bundle.jar
[16:30:24]Failed to delete file:
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\data\cache\bundle5\version0.0\bundle.jar
[16:30:24]Failed to delete file:
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\data\cache\bundle6\version0.0\bundle.jar
[16:30:24]Failed to delete file:
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\data\cache\bundle7\version0.0\bundle.jar
[16:30:24]Failed to delete file:
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\data\cache\bundle8\version0.0\bundle.jar
[16:30:24]Failed to delete file:
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\data\cache\cache.lock
[16:30:24]Failed to delete file:
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\data\log\karaf.log
[16:30:24]Failed to delete file:
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\lib\boot\org.apache.karaf.diagnostic.boot-4.0.2.jar
[16:30:24]Failed to delete file:
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\lib\boot\org.apache.karaf.jaas.boot-4.0.2.jar
[16:30:24]Failed to delete file:
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\lib\boot\org.apache.karaf.main-4.0.2.jar
[16:30:24]Failed to delete file:
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\lib\boot\org.osgi.core-6.0.0.jar
[16:30:24]Failed to delete file:
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\lib\endorsed\javax.annotation-api-1.2.jar
[16:30:24]Failed to delete file:
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\lib\endorsed\org.apache.karaf.exception-4.0.2.jar
[16:30:24]Failed to delete file:
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\lib\endorsed\org.apache.servicemix.bundles.xalan-2.7.2_2.jar
[16:30:24]Failed to delete file:
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\lib\endorsed\org.apache.servicemix.bundles.xalan-serializer-2.7.2_1.jar
[16:30:24]Failed to delete file:
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\lib\endorsed\org.apache.servicemix.specs.activation-api-1.1-2.5.0.jar
[16:30:24]Failed to delete file:
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\lib\endorsed\org.apache.servicemix.specs.jaxb-api-2.2-2.5.0.jar
[16:30:24]Failed to delete file:
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\lib\endorsed\org.apache.servicemix.specs.jaxp-api-1.4-2.5.0.jar
[16:30:24]Failed to delete file:
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\lib\endorsed\org.apache.servicemix.specs.jaxws-api-2.2-2.5.0.jar
[16:30:24]Failed to delete file:
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\lib\endorsed\org.apache.servicemix.specs.saaj-api-1.3-2.5.0.jar
[16:30:24]Failed to delete file:
C:\BuildAgent\work\b
