[jira] [Assigned] (IGNITE-2228) .NET: Ensure async Task can be cancelled.
[ https://issues.apache.org/jira/browse/IGNITE-2228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn reassigned IGNITE-2228: -- Assignee: Pavel Tupitsyn > .NET: Ensure async Task can be cancelled. > - > > Key: IGNITE-2228 > URL: https://issues.apache.org/jira/browse/IGNITE-2228 > Project: Ignite > Issue Type: Bug > Components: interop >Affects Versions: ignite-1.4 >Reporter: Vladimir Ozerov >Assignee: Pavel Tupitsyn >Priority: Critical > Fix For: 1.6 > > > Java has IgniteFuture.cancel() method. Depending on the context, it perofrms > different things. From no-op to task/closure cancellation. > We need to ensure that TPL infrastructure in .NET is able to propagate > cancellation to Java future. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-2143) inner join produce wrong result and is very slow
[
https://issues.apache.org/jira/browse/IGNITE-2143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15067736#comment-15067736
]
Sergey Soldatov commented on IGNITE-2143:
-
Well, I did some testing and here is the result:
Query:
SELECT a.name, a.lang, a.desc, count(a.name) AS cnt, a.url
FROM ( SELECT repo_name AS name, lang AS lang, desc AS desc, repo_url AS url
FROM gitrecord WHERE type='WatchEvent' AND create_at BETWEEN
'2015-01-01T00:01:00Z' AND '2015-01-01T03:59:00Z') AS a INNER JOIN ( SELECT
repo_url AS url FROM gitrecord WHERE type='CreateEvent' AND create_at BETWEEN
'2015-01-01T00:01:00Z' AND '2015-01-01T03:59:00Z') AS b ON a.url=b.url GROUP BY
a.name, a.lang, a.desc, a.url HAVING cnt > 5 ORDER BY cnt DESC LIMIT 25
I used 1 node ignite to avoid problems with affinity. Without any indexes it
takes 300 sec. With indexes on create_at and type it takes 40 sec. The same
query in Spark works less than 5 sec.
Here is the explain on indexed version:
[[SELECT
A.NAME AS __C0,
A.LANG AS __C1,
A.DESC AS __C2,
COUNT(A.NAME) AS __C3,
A.URL AS __C4,
COUNT(A.NAME) AS __C5
FROM (
SELECT
REPO_URL AS URL
FROM "gitrecords".GITRECORD
/* "gitrecords"."create_at_idx": CREATE_AT >= '2015-01-01T00:01:00Z'
AND CREATE_AT <= '2015-01-01T03:59:00Z'
*/
WHERE (TYPE = 'CreateEvent')
AND ((CREATE_AT >= '2015-01-01T00:01:00Z')
AND (CREATE_AT <= '2015-01-01T03:59:00Z'))
) B
/* SELECT
REPO_URL AS URL
FROM "gitrecords".GITRECORD
/++ "gitrecords"."create_at_idx": CREATE_AT >= '2015-01-01T00:01:00Z'
AND CREATE_AT <= '2015-01-01T03:59:00Z'
++/
WHERE (TYPE = 'CreateEvent')
AND ((CREATE_AT >= '2015-01-01T00:01:00Z')
AND (CREATE_AT <= '2015-01-01T03:59:00Z'))
*/
INNER JOIN (
SELECT
REPO_NAME AS NAME,
LANG AS LANG,
DESC AS DESC,
REPO_URL AS URL
FROM "gitrecords".GITRECORD
/* "gitrecords"."create_at_idx": CREATE_AT >= '2015-01-01T00:01:00Z'
AND CREATE_AT <= '2015-01-01T03:59:00Z'
*/
WHERE (TYPE = 'WatchEvent')
AND ((CREATE_AT >= '2015-01-01T00:01:00Z')
AND (CREATE_AT <= '2015-01-01T03:59:00Z'))
) A
/* SELECT
REPO_NAME AS NAME,
LANG AS LANG,
DESC AS DESC,
REPO_URL AS URL
FROM "gitrecords".GITRECORD
/++ "gitrecords"."create_at_idx": CREATE_AT >= '2015-01-01T00:01:00Z'
AND CREATE_AT <= '2015-01-01T03:59:00Z'
++/
WHERE (REPO_URL IS ?1)
AND ((TYPE = 'WatchEvent')
AND ((CREATE_AT >= '2015-01-01T00:01:00Z')
AND (CREATE_AT <= '2015-01-01T03:59:00Z'))): URL = B.URL
*/
ON 1=1
WHERE A.URL = B.URL
GROUP BY A.NAME, A.LANG, A.DESC, A.URL], [SELECT
__C0 AS NAME,
__C1 AS LANG,
__C2 AS DESC,
CAST(SUM(__C3) AS BIGINT) AS CNT,
__C4 AS URL
FROM PUBLIC.__T0
/* "gitrecords"."merge_scan" */
WHERE __C5
GROUP BY __C0, __C1, __C2, __C4
ORDER BY 4 DESC
LIMIT 25]]
Hope it can help
> inner join produce wrong result and is very slow
>
>
> Key: IGNITE-2143
> URL: https://issues.apache.org/jira/browse/IGNITE-2143
> Project: Ignite
> Issue Type: Bug
> Components: SQL
>Affects Versions: 1.5
> Environment: 3 nodes in docker containers.
>Reporter: Sergey Soldatov
>Priority: Critical
> Attachments: config.xml, ignite-cache-1.0.0.jar
>
>
> I have following query for gitarchive records processing.
> {code}
> select
> lang, count(distinct ForkTable.repo_url) as cnt
> from (
> select repo_url, lang from gitrecord where type = 'ForkEvent' and
> lang is not null group by lang, repo_url) as ForkTable
> inner join (
> select repo_url, html_url from gitrecord where type='PullRequestEvent'
>
> group by repo_url, html_url) as PullTable
> on
> ForkTable.repo_url = PullTable.repo_url
> group by lang
> order by cnt desc
> {code}
> And there are two major problems:
> 1. It produces an incorrect result if it's running in cluster mode.
> 2. It's really slow. for 200k rows it takes 500+ seconds comparing to 20 on
> Spark for the same query
> Steps to reproduce:
> 1. Download github archive for 1 day and put it to hdfs ("/Data" in my case):
> {code}wget http://data.githubarchive.org/2015-01-01-{0..23}.json.gz{code}
> 2. copy attached ignite-cache-1.0.0.jar to Ignite's lib dir
> 3. run ignite with attached config.xml
> 4. run spark-shell
> {code}
> spark-shell --packages org.apache.ignite:ignite-spark:1.5.0-b1 --repositories
> http://www.gridgainsystems.com/nexus/content/repositories/external --jars
> /usr/lib/ignite-hadoop/libs/ignite-cache-1.0.0.jar --master
> spark://{spark-master}:7077
> {code}
> 5. load data and execute the
[jira] [Commented] (IGNITE-2216) Duplicate field names with aliases do not work in queries.
[ https://issues.apache.org/jira/browse/IGNITE-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15067742#comment-15067742 ] Vladimir Ozerov commented on IGNITE-2216: - Appears to be pretty complex fix. Moving to 1.6. > Duplicate field names with aliases do not work in queries. > -- > > Key: IGNITE-2216 > URL: https://issues.apache.org/jira/browse/IGNITE-2216 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: ignite-1.4 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Critical > Fix For: 1.6 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2216) Duplicate field names with aliases do not work in queries.
[ https://issues.apache.org/jira/browse/IGNITE-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-2216: Fix Version/s: (was: 1.5) 1.6 > Duplicate field names with aliases do not work in queries. > -- > > Key: IGNITE-2216 > URL: https://issues.apache.org/jira/browse/IGNITE-2216 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: ignite-1.4 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Critical > Fix For: 1.6 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-2213) Handle duplicate field names in BinaryMarshaller.
[
https://issues.apache.org/jira/browse/IGNITE-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov closed IGNITE-2213.
---
> Handle duplicate field names in BinaryMarshaller.
> -
>
> Key: IGNITE-2213
> URL: https://issues.apache.org/jira/browse/IGNITE-2213
> Project: Ignite
> Issue Type: Bug
> Components: general, interop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Blocker
> Fix For: 1.5
>
>
> Consider the following scenario:
> {code}
> class A {
> int field;
> }
> class B : class A {
> int field;
> }
> {code}
> In this case BinaryMarshaller will throw an exception about duplicate field
> names. And there is no sensible workaround for user.
> We can add some prefix/suffix to comflicting fields. E.g. A.field will be
> written as "field", B.field will be written as "field_B".
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (IGNITE-2213) Handle duplicate field names in BinaryMarshaller.
[
https://issues.apache.org/jira/browse/IGNITE-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov resolved IGNITE-2213.
-
Resolution: Fixed
> Handle duplicate field names in BinaryMarshaller.
> -
>
> Key: IGNITE-2213
> URL: https://issues.apache.org/jira/browse/IGNITE-2213
> Project: Ignite
> Issue Type: Bug
> Components: general, interop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Blocker
> Fix For: 1.5
>
>
> Consider the following scenario:
> {code}
> class A {
> int field;
> }
> class B : class A {
> int field;
> }
> {code}
> In this case BinaryMarshaller will throw an exception about duplicate field
> names. And there is no sensible workaround for user.
> We can add some prefix/suffix to comflicting fields. E.g. A.field will be
> written as "field", B.field will be written as "field_B".
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2219) ClassCastException from NodeIdMessage to AffinityTopologyVersion
[
https://issues.apache.org/jira/browse/IGNITE-2219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15067787#comment-15067787
]
Noam Liran commented on IGNITE-2219:
The error now reproduces quite frequently even on "fresh" clusters.
> ClassCastException from NodeIdMessage to AffinityTopologyVersion
>
>
> Key: IGNITE-2219
> URL: https://issues.apache.org/jira/browse/IGNITE-2219
> Project: Ignite
> Issue Type: Bug
>Affects Versions: ignite-1.4
> Environment: Ubuntu 12.04 64 bit
> java version "1.8.0_60"
> Java(TM) SE Runtime Environment (build 1.8.0_60-b27)
> Java HotSpot(TM) 64-Bit Server VM (build 25.60-b23, mixed mode)
> Ignite 1.4.0
>Reporter: Avihai Berkovitz
>
> We had a cluster up and running for a couple of days. Without doing anything
> new, we got the following error in one of the nodes:
> {noformat}
> Caught unhandled exception in NIO worker thread (restart the node).
> java.lang.ClassCastException:
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi$NodeIdMessage
> cannot be cast to
> org.apache.ignite.internal.processors.affinity.AffinityTopologyVersion
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsFullMessage.readFrom(GridDhtPartitionsFullMessage.java:176)
> ~[ignite-core-1.4.0.jar:1.4.0]
> at
> org.apache.ignite.internal.direct.DirectByteBufferStream.readMessage(DirectByteBufferStream.java:963)
> ~[ignite-core-1.4.0.jar:1.4.0]
> at
> org.apache.ignite.internal.direct.DirectMessageReader.readMessage(DirectMessageReader.java:252)
> ~[ignite-core-1.4.0.jar:1.4.0]
> at
> org.apache.ignite.internal.managers.communication.GridIoMessage.readFrom(GridIoMessage.java:249)
> ~[ignite-core-1.4.0.jar:1.4.0]
> at
> org.apache.ignite.internal.util.nio.GridDirectParser.decode(GridDirectParser.java:79)
> ~[ignite-core-1.4.0.jar:1.4.0]
> at
> org.apache.ignite.internal.util.nio.GridNioCodecFilter.onMessageReceived(GridNioCodecFilter.java:104)
> ~[ignite-core-1.4.0.jar:1.4.0]
> at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:107)
> ~[ignite-core-1.4.0.jar:1.4.0]
> at
> org.apache.ignite.internal.util.nio.GridConnectionBytesVerifyFilter.onMessageReceived(GridConnectionBytesVerifyFilter.java:78)
> ~[ignite-core-1.4.0.jar:1.4.0]
> at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:107)
> ~[ignite-core-1.4.0.jar:1.4.0]
> at
> org.apache.ignite.internal.util.nio.GridNioServer$HeadFilter.onMessageReceived(GridNioServer.java:2124)
> ~[ignite-core-1.4.0.jar:1.4.0]
> at
> org.apache.ignite.internal.util.nio.GridNioFilterChain.onMessageReceived(GridNioFilterChain.java:173)
> ~[ignite-core-1.4.0.jar:1.4.0]
> at
> org.apache.ignite.internal.util.nio.GridNioServer$DirectNioClientWorker.processRead(GridNioServer.java:898)
> ~[ignite-core-1.4.0.jar:1.4.0]
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeys(GridNioServer.java:1437)
> ~[ignite-core-1.4.0.jar:1.4.0]
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:1379)
> ~[ignite-core-1.4.0.jar:1.4.0]
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1263)
> ~[ignite-core-1.4.0.jar:1.4.0]
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> [ignite-core-1.4.0.jar:1.4.0]
> at java.lang.Thread.run(Thread.java:745) [na:1.8.0_60]
> {noformat}
> It happened only once so far, but killed the communication from this node.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-2229) Full text queries do not return valid results on unstable topology
Alexey Goncharuk created IGNITE-2229: Summary: Full text queries do not return valid results on unstable topology Key: IGNITE-2229 URL: https://issues.apache.org/jira/browse/IGNITE-2229 Project: Ignite Issue Type: Bug Components: cache Reporter: Alexey Goncharuk Fix For: 1.6 Added test org.apache.ignite.internal.processors.cache.IgniteCacheFullTextQueryNodeJoiningSelfTest that fails. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-2078) Need to clean cache after query in CacheQueryExample
[
https://issues.apache.org/jira/browse/IGNITE-2078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15067813#comment-15067813
]
Alexey Goncharuk commented on IGNITE-2078:
--
The duplicate output is caused by ignite-2229
> Need to clean cache after query in CacheQueryExample
>
>
> Key: IGNITE-2078
> URL: https://issues.apache.org/jira/browse/IGNITE-2078
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.5
> Environment: OS X 10.10.2
> jdk 1.7
>Reporter: Ilya Suntsov
>Assignee: Alexey Goncharuk
> Fix For: 1.5
>
>
> Steps to reproduce:
> 1. Build examples
> 2. Start several nodes: org/apache/ignite/examples/ExampleNodeStartup.java
> 3. Run org/apache/ignite/examples/datagrid/CacheQueryExample.java
> Example output:
> {noformat}
> >>> Cache query example started.
> >>> People with salaries between 0 and 1000 (queried with SCAN query):
> >>> Entry [key=AffinityKey [key=1717604734904449,
> >>> affKey=-6908357575301716955], val=Person [firstName=Jane, lastName=Doe,
> >>> id=1717604734904449, orgId=-6908357575301716955, resume=Jane Doe has
> >>> Bachelor Degree., salary=1000.0]]
> >>> Entry [key=AffinityKey [key=-591199628496362239,
> >>> affKey=-7983468300595888028], val=Person [firstName=John, lastName=Smith,
> >>> id=-591199628496362239, orgId=-7983468300595888028, resume=John Smith has
> >>> Bachelor Degree., salary=1000.0]]
> >>> People with salaries between 0 and 1000 (queried with SQL query):
> >>> Entry [key=AffinityKey [key=1717604734904449,
> >>> affKey=-6908357575301716955], val=Person [firstName=Jane, lastName=Doe,
> >>> id=1717604734904449, orgId=-6908357575301716955, resume=Jane Doe has
> >>> Bachelor Degree., salary=1000.0]]
> >>> Entry [key=AffinityKey [key=-591199628496362239,
> >>> affKey=-7983468300595888028], val=Person [firstName=John, lastName=Smith,
> >>> id=-591199628496362239, orgId=-7983468300595888028, resume=John Smith has
> >>> Bachelor Degree., salary=1000.0]]
> >>> People with salaries between 1000 and 2000 (queried with SQL query):
> >>> Entry [key=AffinityKey [key=6165286975353599015,
> >>> affKey=-7983468300595888028], val=Person [firstName=Jane, lastName=Smith,
> >>> id=6165286975353599015, orgId=-7983468300595888028, resume=Jane Smith has
> >>> Master Degree., salary=2000.0]]
> >>> Entry [key=AffinityKey [key=-3732623193094597924,
> >>> affKey=-6908357575301716955], val=Person [firstName=John, lastName=Doe,
> >>> id=-3732623193094597924, orgId=-6908357575301716955, resume=John Doe has
> >>> Master Degree., salary=2000.0]]
> >>> Following people are 'ApacheIgnite' employees:
> >>> Following people are 'Other' employees:
> >>> Entry [key=AffinityKey [key=-591199628496362239,
> >>> affKey=-7983468300595888028], val=Person [firstName=John, lastName=Smith,
> >>> id=-591199628496362239, orgId=-7983468300595888028, resume=John Smith has
> >>> Bachelor Degree., salary=1000.0]]
> >>> Following people have 'Master Degree' in their resumes:
> >>> Entry [key=AffinityKey [key=6165286975353599015,
> >>> affKey=-7983468300595888028], val=Person [firstName=Jane, lastName=Smith,
> >>> id=6165286975353599015, orgId=-7983468300595888028, resume=Jane Smith has
> >>> Master Degree., salary=2000.0]]
> >>> Entry [key=AffinityKey [key=-3732623193094597924,
> >>> affKey=-6908357575301716955], val=Person [firstName=John, lastName=Doe,
> >>> id=-3732623193094597924, orgId=-6908357575301716955, resume=John Doe has
> >>> Master Degree., salary=2000.0]]
> >>> Following people have 'Bachelor Degree' in their resumes:
> >>> Entry [key=AffinityKey [key=1717604734904449,
> >>> affKey=-6908357575301716955], val=Person [firstName=Jane, lastName=Doe,
> >>> id=1717604734904449, orgId=-6908357575301716955, resume=Jane Doe has
> >>> Bachelor Degree., salary=1000.0]]
> >>> Entry [key=AffinityKey [key=-591199628496362239,
> >>> affKey=-7983468300595888028], val=Person [firstName=John, lastName=Smith,
> >>> id=-591199628496362239, orgId=-7983468300595888028, resume=John Smith has
> >>> Bachelor Degree., salary=1000.0]]
> >>> Average salary for 'ApacheIgnite' employees:
> >>> [null]
> >>> Names of all employees:
> >>> [Jane Smith]
> >>> [Jane Doe]
> >>> [John Doe]
> >>> [John Smith]
> >>> Names of all employees and organizations they belong to:
> >>> [John Smith, Other]
> >>> Cache query example finished.
> [13:01:23] Ignite node stopped OK [uptime=00:00:01:297]
> {noformat}
> 4. Start example second time (don't stop nodes).
> Example output:
> {noformat}
> >>> Cache query example started.
> >>> People with salaries between 0 and 1000 (queried with SCAN query):
> >>> Entry [key=AffinityKey [key=1717604734904449,
> >>> affKey=-69083575
[jira] [Updated] (IGNITE-2078) Need to clean cache after query in CacheQueryExample
[
https://issues.apache.org/jira/browse/IGNITE-2078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-2078:
-
Fix Version/s: (was: 1.5)
1.6
> Need to clean cache after query in CacheQueryExample
>
>
> Key: IGNITE-2078
> URL: https://issues.apache.org/jira/browse/IGNITE-2078
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.5
> Environment: OS X 10.10.2
> jdk 1.7
>Reporter: Ilya Suntsov
>Assignee: Alexey Goncharuk
> Fix For: 1.6
>
>
> Steps to reproduce:
> 1. Build examples
> 2. Start several nodes: org/apache/ignite/examples/ExampleNodeStartup.java
> 3. Run org/apache/ignite/examples/datagrid/CacheQueryExample.java
> Example output:
> {noformat}
> >>> Cache query example started.
> >>> People with salaries between 0 and 1000 (queried with SCAN query):
> >>> Entry [key=AffinityKey [key=1717604734904449,
> >>> affKey=-6908357575301716955], val=Person [firstName=Jane, lastName=Doe,
> >>> id=1717604734904449, orgId=-6908357575301716955, resume=Jane Doe has
> >>> Bachelor Degree., salary=1000.0]]
> >>> Entry [key=AffinityKey [key=-591199628496362239,
> >>> affKey=-7983468300595888028], val=Person [firstName=John, lastName=Smith,
> >>> id=-591199628496362239, orgId=-7983468300595888028, resume=John Smith has
> >>> Bachelor Degree., salary=1000.0]]
> >>> People with salaries between 0 and 1000 (queried with SQL query):
> >>> Entry [key=AffinityKey [key=1717604734904449,
> >>> affKey=-6908357575301716955], val=Person [firstName=Jane, lastName=Doe,
> >>> id=1717604734904449, orgId=-6908357575301716955, resume=Jane Doe has
> >>> Bachelor Degree., salary=1000.0]]
> >>> Entry [key=AffinityKey [key=-591199628496362239,
> >>> affKey=-7983468300595888028], val=Person [firstName=John, lastName=Smith,
> >>> id=-591199628496362239, orgId=-7983468300595888028, resume=John Smith has
> >>> Bachelor Degree., salary=1000.0]]
> >>> People with salaries between 1000 and 2000 (queried with SQL query):
> >>> Entry [key=AffinityKey [key=6165286975353599015,
> >>> affKey=-7983468300595888028], val=Person [firstName=Jane, lastName=Smith,
> >>> id=6165286975353599015, orgId=-7983468300595888028, resume=Jane Smith has
> >>> Master Degree., salary=2000.0]]
> >>> Entry [key=AffinityKey [key=-3732623193094597924,
> >>> affKey=-6908357575301716955], val=Person [firstName=John, lastName=Doe,
> >>> id=-3732623193094597924, orgId=-6908357575301716955, resume=John Doe has
> >>> Master Degree., salary=2000.0]]
> >>> Following people are 'ApacheIgnite' employees:
> >>> Following people are 'Other' employees:
> >>> Entry [key=AffinityKey [key=-591199628496362239,
> >>> affKey=-7983468300595888028], val=Person [firstName=John, lastName=Smith,
> >>> id=-591199628496362239, orgId=-7983468300595888028, resume=John Smith has
> >>> Bachelor Degree., salary=1000.0]]
> >>> Following people have 'Master Degree' in their resumes:
> >>> Entry [key=AffinityKey [key=6165286975353599015,
> >>> affKey=-7983468300595888028], val=Person [firstName=Jane, lastName=Smith,
> >>> id=6165286975353599015, orgId=-7983468300595888028, resume=Jane Smith has
> >>> Master Degree., salary=2000.0]]
> >>> Entry [key=AffinityKey [key=-3732623193094597924,
> >>> affKey=-6908357575301716955], val=Person [firstName=John, lastName=Doe,
> >>> id=-3732623193094597924, orgId=-6908357575301716955, resume=John Doe has
> >>> Master Degree., salary=2000.0]]
> >>> Following people have 'Bachelor Degree' in their resumes:
> >>> Entry [key=AffinityKey [key=1717604734904449,
> >>> affKey=-6908357575301716955], val=Person [firstName=Jane, lastName=Doe,
> >>> id=1717604734904449, orgId=-6908357575301716955, resume=Jane Doe has
> >>> Bachelor Degree., salary=1000.0]]
> >>> Entry [key=AffinityKey [key=-591199628496362239,
> >>> affKey=-7983468300595888028], val=Person [firstName=John, lastName=Smith,
> >>> id=-591199628496362239, orgId=-7983468300595888028, resume=John Smith has
> >>> Bachelor Degree., salary=1000.0]]
> >>> Average salary for 'ApacheIgnite' employees:
> >>> [null]
> >>> Names of all employees:
> >>> [Jane Smith]
> >>> [Jane Doe]
> >>> [John Doe]
> >>> [John Smith]
> >>> Names of all employees and organizations they belong to:
> >>> [John Smith, Other]
> >>> Cache query example finished.
> [13:01:23] Ignite node stopped OK [uptime=00:00:01:297]
> {noformat}
> 4. Start example second time (don't stop nodes).
> Example output:
> {noformat}
> >>> Cache query example started.
> >>> People with salaries between 0 and 1000 (queried with SCAN query):
> >>> Entry [key=AffinityKey [key=1717604734904449,
> >>> affKey=-6908357575301716955], val=Person [firstName=Jane, lastN
[jira] [Commented] (IGNITE-2226) Replace dash in 1.5.0-final with dot 1.5.0.final
[ https://issues.apache.org/jira/browse/IGNITE-2226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15067856#comment-15067856 ] Anton Vinogradov commented on IGNITE-2226: -- Seems everything is ok, https://versionatorr.appspot.com/?a=1.5.0.final&b=1.5.0-b1 https://versionatorr.appspot.com/?a=1.5.0.final&b=1.5.0-final I'll update versions. > Replace dash in 1.5.0-final with dot 1.5.0.final > > > Key: IGNITE-2226 > URL: https://issues.apache.org/jira/browse/IGNITE-2226 > Project: Ignite > Issue Type: Bug > Components: build >Reporter: Dmitriy Setrakyan >Assignee: Anton Vinogradov >Priority: Blocker > Fix For: 1.5 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-2016) Update KafkaStreamer to fit new features introduced in Kafka 0.9
[
https://issues.apache.org/jira/browse/IGNITE-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15067859#comment-15067859
]
Denis Magda commented on IGNITE-2016:
-
Hi Roman, before taking look at the details of the implementation I have
several high level questions.
- In general as I see you've implemented a new Kafka streamer using Kafka
Connect API, correct?
If so is there any reason why we can't extend existed {{StreamAdapter}} like
current Ignite's {{KafkaStreamer}}, {{MqttStreamer}}, etc. does? It will be
more consistent if you create a kind of {{KafkaConnectStreamer}} and put all
the implementation details in there.
- I wouldn't mode create one more module cause we already have "ignite-kafka".
So my preference if you reuse the existed one.
- New streamer's configuration parameters should be passed through setters of
the implementation. Please refer to {{KafkaStreamer}}, {{MqttStreamer}} to as
an example.
> Update KafkaStreamer to fit new features introduced in Kafka 0.9
>
>
> Key: IGNITE-2016
> URL: https://issues.apache.org/jira/browse/IGNITE-2016
> Project: Ignite
> Issue Type: New Feature
> Components: streaming
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
>
> Particularly,
> - new consumer
> - Kafka Connect (Copycat)
> http://www.confluent.io/blog/apache-kafka-0.9-is-released
> This can be a a different integration task or a complete re-write of the
> current implementation, considering the fact that Kafka Connect is a new
> standard way for "large-scale, real-time data import and export for Kafka."
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2213) Handle duplicate field names in BinaryMarshaller.
[
https://issues.apache.org/jira/browse/IGNITE-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15067878#comment-15067878
]
Roman Shtykh commented on IGNITE-2213:
--
BinaryMarshallerSelfTest.testDuplicateFields() will fail in Java 8
assertEquals(1, objBin.field(fieldNameA)); -> assertEquals(new Integer(1),
objBin.field(fieldNameA)); etc.
> Handle duplicate field names in BinaryMarshaller.
> -
>
> Key: IGNITE-2213
> URL: https://issues.apache.org/jira/browse/IGNITE-2213
> Project: Ignite
> Issue Type: Bug
> Components: general, interop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Blocker
> Fix For: 1.5
>
>
> Consider the following scenario:
> {code}
> class A {
> int field;
> }
> class B : class A {
> int field;
> }
> {code}
> In this case BinaryMarshaller will throw an exception about duplicate field
> names. And there is no sensible workaround for user.
> We can add some prefix/suffix to comflicting fields. E.g. A.field will be
> written as "field", B.field will be written as "field_B".
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2016) Update KafkaStreamer to fit new features introduced in Kafka 0.9
[ https://issues.apache.org/jira/browse/IGNITE-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15067927#comment-15067927 ] Roman Shtykh commented on IGNITE-2016: -- Hi Denis, I think Anton had similar questions when he reviewed Flume integration ;) Please see my replies inline. D> In general as I see you've implemented a new Kafka streamer using Kafka Connect API, correct? D> If so is there any reason why we can't extend existed StreamAdapter like current Ignite's KafkaStreamer, MqttStreamer, etc. does? It will be more consistent if you create a kind of KafkaConnectStreamer and put all the implementation details in there. R> First of all, from what I see, Kafka Connect is going to be a standard way of integration for data import/export and streaming. This is coming with many 'perks' included like reliability, scalability, etc. R> I understand you would like to have Kafka client being invoked from Ignite and keep it consistent with other implementations, but here Kafka Connect is central and you have to invoke Ignite from Connect API (similarly to how it is done in Flume). D> I wouldn't mode create one more module cause we already have "ignite-kafka". So my preference if you reuse the existed one. D> New streamer's configuration parameters should be passed through setters of the implementation. Please refer to KafkaStreamer, MqttStreamer to as an example. R> Looking at how Kafka Connect and Flume is designed for integration with other systems, I think it is valid to have an alternative to using IgniteDataStreamer for these sort of integrations. R> Do you prefer to handle all Kafka reliability and scalability issues, etc. every time Kafka has modifications (or make users handle it, which is even worse), or using these out of the box? ;) I prefer the latter. R> That said, the current KafkaStreamer may be used too for some special cases. We can keep two packages for a while. But again I want to emphasize, it is not the duplicate solution. > Update KafkaStreamer to fit new features introduced in Kafka 0.9 > > > Key: IGNITE-2016 > URL: https://issues.apache.org/jira/browse/IGNITE-2016 > Project: Ignite > Issue Type: New Feature > Components: streaming >Reporter: Roman Shtykh >Assignee: Roman Shtykh > > Particularly, > - new consumer > - Kafka Connect (Copycat) > http://www.confluent.io/blog/apache-kafka-0.9-is-released > This can be a a different integration task or a complete re-write of the > current implementation, considering the fact that Kafka Connect is a new > standard way for "large-scale, real-time data import and export for Kafka." -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1963) CPP: Optimize interop memory
[
https://issues.apache.org/jira/browse/IGNITE-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego updated IGNITE-1963:
Description:
Current design of the {{InteropMemory}} class got some unavoidable overheads
and makes it difficult to implement adapter-like subclasses.
1. Considering that {{InteropMemory}} is the only class that can be used with
binary streams and binary readers/writers, it should have design that allows
writing adapter subclasses. For example, it could be std::vector class adapter
or stack-allocated array.
2. Current {{InteropUnpooledMemory}} implementation makes two heap memory
allocations during instance construction. It's a big overhead considering that
{{InteropUnpooledMemory}} instances construction happens often.
3. Consider replacing this class into two classes: read/write memory and read
only memory. It makes sense because Input streams do not modify memory they
operate on and It would allow us to implement reading in a more efficient way
because we wont be needing to implement {{Reallocate()}} method anymore.
was:
Current design of the {{InteropMemory}} class got some unavoidable overheads
and makes it difficult to implement adapter-like subclasses.
1. Considering that {{InteropMemory}} is the only class that can be used with
binary streams and binary readers/writers, it should have design that allows
writing adapter subclasses. For example, it could be std::vector class adapter
or stack-allocated array.
2. Current {{InteropUnpooledMemory}} implementation makes two heap memory
allocations during instance construction. It's a big overhead considering that
{{InteropUnpooledMemory}} instances construction happen often.
3. Consider replacing this class into two classes: read/write memory and read
only memory. It makes sense because Input streams do not modify memory they
operate on and It would allow us to implement reading in a more efficient way
because we wont be needing to implement {{Reallocate()}} method anymore.
> CPP: Optimize interop memory
>
>
> Key: IGNITE-1963
> URL: https://issues.apache.org/jira/browse/IGNITE-1963
> Project: Ignite
> Issue Type: Task
> Components: interop
>Affects Versions: ignite-1.4
>Reporter: Igor Sapego
>Priority: Minor
> Fix For: 1.6
>
>
> Current design of the {{InteropMemory}} class got some unavoidable overheads
> and makes it difficult to implement adapter-like subclasses.
> 1. Considering that {{InteropMemory}} is the only class that can be used with
> binary streams and binary readers/writers, it should have design that allows
> writing adapter subclasses. For example, it could be std::vector class
> adapter or stack-allocated array.
> 2. Current {{InteropUnpooledMemory}} implementation makes two heap memory
> allocations during instance construction. It's a big overhead considering
> that {{InteropUnpooledMemory}} instances construction happens often.
> 3. Consider replacing this class into two classes: read/write memory and read
> only memory. It makes sense because Input streams do not modify memory they
> operate on and It would allow us to implement reading in a more efficient way
> because we wont be needing to implement {{Reallocate()}} method anymore.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1963) CPP: Optimize interop memory
[
https://issues.apache.org/jira/browse/IGNITE-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego updated IGNITE-1963:
Description:
Current design of the {{InteropMemory}} class got some unavoidable overheads
and makes it difficult to implement adapter-like subclasses.
1. Considering that {{InteropMemory}} is the only class that can be used with
binary streams and binary readers/writers, it should have design that allows
writing adapter subclasses. For example, it could be std::vector class adapter
or stack-allocated array.
2. Current {{InteropUnpooledMemory}} implementation makes two heap memory
allocations during instance construction. It's a big overhead considering that
{{InteropUnpooledMemory}} instances construction happens often.
3. Consider replacing this class with two classes: read/write memory and read
only memory. It makes sense because Input streams do not modify memory they
operate on and It would allow us to implement reading in a more efficient way
because we wont be needing to implement {{Reallocate()}} method anymore.
was:
Current design of the {{InteropMemory}} class got some unavoidable overheads
and makes it difficult to implement adapter-like subclasses.
1. Considering that {{InteropMemory}} is the only class that can be used with
binary streams and binary readers/writers, it should have design that allows
writing adapter subclasses. For example, it could be std::vector class adapter
or stack-allocated array.
2. Current {{InteropUnpooledMemory}} implementation makes two heap memory
allocations during instance construction. It's a big overhead considering that
{{InteropUnpooledMemory}} instances construction happens often.
3. Consider replacing this class into two classes: read/write memory and read
only memory. It makes sense because Input streams do not modify memory they
operate on and It would allow us to implement reading in a more efficient way
because we wont be needing to implement {{Reallocate()}} method anymore.
> CPP: Optimize interop memory
>
>
> Key: IGNITE-1963
> URL: https://issues.apache.org/jira/browse/IGNITE-1963
> Project: Ignite
> Issue Type: Task
> Components: interop
>Affects Versions: ignite-1.4
>Reporter: Igor Sapego
>Priority: Minor
> Fix For: 1.6
>
>
> Current design of the {{InteropMemory}} class got some unavoidable overheads
> and makes it difficult to implement adapter-like subclasses.
> 1. Considering that {{InteropMemory}} is the only class that can be used with
> binary streams and binary readers/writers, it should have design that allows
> writing adapter subclasses. For example, it could be std::vector class
> adapter or stack-allocated array.
> 2. Current {{InteropUnpooledMemory}} implementation makes two heap memory
> allocations during instance construction. It's a big overhead considering
> that {{InteropUnpooledMemory}} instances construction happens often.
> 3. Consider replacing this class with two classes: read/write memory and read
> only memory. It makes sense because Input streams do not modify memory they
> operate on and It would allow us to implement reading in a more efficient way
> because we wont be needing to implement {{Reallocate()}} method anymore.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1963) CPP: Optimize interop memory
[
https://issues.apache.org/jira/browse/IGNITE-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego updated IGNITE-1963:
Description:
Current design of the {{InteropMemory}} class got some unavoidable overheads
and makes it difficult to implement adapter-like subclasses.
1. Considering that {{InteropMemory}} is the only class that can be used with
binary streams and binary readers/writers, it should have design that allows
writing adapter subclasses. For example, it could be std::vector class adapter
or stack-allocated array.
2. Current {{InteropUnpooledMemory}} implementation makes two heap memory
allocations during instance construction. It's a big overhead considering that
{{InteropUnpooledMemory}} instances construction happens often.
3. Consider replacing this class with two classes: read/write memory and read
only memory. It makes sense because Input streams do not modify memory they
operate on. That would allow us to implement reading in a more efficient way
because we wont be needing to implement {{Reallocate()}} method anymore.
was:
Current design of the {{InteropMemory}} class got some unavoidable overheads
and makes it difficult to implement adapter-like subclasses.
1. Considering that {{InteropMemory}} is the only class that can be used with
binary streams and binary readers/writers, it should have design that allows
writing adapter subclasses. For example, it could be std::vector class adapter
or stack-allocated array.
2. Current {{InteropUnpooledMemory}} implementation makes two heap memory
allocations during instance construction. It's a big overhead considering that
{{InteropUnpooledMemory}} instances construction happens often.
3. Consider replacing this class with two classes: read/write memory and read
only memory. It makes sense because Input streams do not modify memory they
operate on and It would allow us to implement reading in a more efficient way
because we wont be needing to implement {{Reallocate()}} method anymore.
> CPP: Optimize interop memory
>
>
> Key: IGNITE-1963
> URL: https://issues.apache.org/jira/browse/IGNITE-1963
> Project: Ignite
> Issue Type: Task
> Components: interop
>Affects Versions: ignite-1.4
>Reporter: Igor Sapego
>Priority: Minor
> Fix For: 1.6
>
>
> Current design of the {{InteropMemory}} class got some unavoidable overheads
> and makes it difficult to implement adapter-like subclasses.
> 1. Considering that {{InteropMemory}} is the only class that can be used with
> binary streams and binary readers/writers, it should have design that allows
> writing adapter subclasses. For example, it could be std::vector class
> adapter or stack-allocated array.
> 2. Current {{InteropUnpooledMemory}} implementation makes two heap memory
> allocations during instance construction. It's a big overhead considering
> that {{InteropUnpooledMemory}} instances construction happens often.
> 3. Consider replacing this class with two classes: read/write memory and read
> only memory. It makes sense because Input streams do not modify memory they
> operate on. That would allow us to implement reading in a more efficient way
> because we wont be needing to implement {{Reallocate()}} method anymore.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-2230) CPP: Implement "Bind offset" feature for the ODBC driver.
Igor Sapego created IGNITE-2230: --- Summary: CPP: Implement "Bind offset" feature for the ODBC driver. Key: IGNITE-2230 URL: https://issues.apache.org/jira/browse/IGNITE-2230 Project: Ignite Issue Type: Task Components: odbc Reporter: Igor Sapego Assignee: Igor Sapego Fix For: 1.6 This feature listed in the [ODBC Core Interface Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx] and should be implemented for our driver. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-2225) Externalizable classes are serialized twice with binary marshaller
[ https://issues.apache.org/jira/browse/IGNITE-2225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov resolved IGNITE-2225. - Resolution: Fixed > Externalizable classes are serialized twice with binary marshaller > -- > > Key: IGNITE-2225 > URL: https://issues.apache.org/jira/browse/IGNITE-2225 > Project: Ignite > Issue Type: Bug > Components: general >Reporter: Valentin Kulichenko >Assignee: Vladimir Ozerov >Priority: Blocker > Fix For: 1.5 > > > Test that reproduces that issue is attached to IGNITE-2212 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2216) Duplicate field names with aliases do not work in queries.
[ https://issues.apache.org/jira/browse/IGNITE-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-2216: Assignee: (was: Vladimir Ozerov) > Duplicate field names with aliases do not work in queries. > -- > > Key: IGNITE-2216 > URL: https://issues.apache.org/jira/browse/IGNITE-2216 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: ignite-1.4 >Reporter: Vladimir Ozerov >Priority: Critical > Fix For: 1.6 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-2225) Externalizable classes are serialized twice with binary marshaller
[ https://issues.apache.org/jira/browse/IGNITE-2225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov closed IGNITE-2225. --- > Externalizable classes are serialized twice with binary marshaller > -- > > Key: IGNITE-2225 > URL: https://issues.apache.org/jira/browse/IGNITE-2225 > Project: Ignite > Issue Type: Bug > Components: general >Reporter: Valentin Kulichenko >Assignee: Vladimir Ozerov >Priority: Blocker > Fix For: 1.5 > > > Test that reproduces that issue is attached to IGNITE-2212 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-2226) Replace dash in 1.5.0-final with dot 1.5.0.final
[ https://issues.apache.org/jira/browse/IGNITE-2226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15068022#comment-15068022 ] Anton Vinogradov commented on IGNITE-2226: -- .final version broke IgniteProductVersion & compatibility with previous versions. Fixes for both issues ready and checking at TC. > Replace dash in 1.5.0-final with dot 1.5.0.final > > > Key: IGNITE-2226 > URL: https://issues.apache.org/jira/browse/IGNITE-2226 > Project: Ignite > Issue Type: Bug > Components: build >Reporter: Dmitriy Setrakyan >Assignee: Anton Vinogradov >Priority: Blocker > Fix For: 1.5 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2231) 'Put' cache event treats entry created at lock acquisition time as old value
Denis Magda created IGNITE-2231:
---
Summary: 'Put' cache event treats entry created at lock
acquisition time as old value
Key: IGNITE-2231
URL: https://issues.apache.org/jira/browse/IGNITE-2231
Project: Ignite
Issue Type: Bug
Components: cache
Affects Versions: ignite-1.4
Reporter: Denis Magda
Assignee: Alexey Goncharuk
Fix For: 1.6
Subscribe for EVT_CACHE_OBJECT_PUT event on one node and perform 'put'
operations from the other to an empty transnational cache.
The subscriber will receive a notification saying that there was an old value
for a key at the time the new was being inserted. In fact the was no an old
value, the entry with a {{null}} as a value was generated as a part of implicit
lock acquisition.
This snippet of the code in {{GridCacheMapEntry}} generates a wrong event
(innerSet function)
{noformat}
if (evt && newVer != null &&
cctx.events().isRecordable(EVT_CACHE_OBJECT_PUT)) {
CacheObject evtOld = cctx.unwrapTemporary(old);
cctx.events().addEvent(partition(),
key,
evtNodeId,
tx == null ? null : tx.xid(),
newVer,
EVT_CACHE_OBJECT_PUT,
val,
val != null,
evtOld,
evtOld != null || hasValueUnlocked(),
subjId, null, taskName,
keepBinary);
}
{noformat}
Attached the test that lets reproduce the issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2231) 'Put' cache event treats entry created at lock acquisition time as old value
[
https://issues.apache.org/jira/browse/IGNITE-2231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda updated IGNITE-2231:
Attachment: EventsProcessingTest.java
> 'Put' cache event treats entry created at lock acquisition time as old value
>
>
> Key: IGNITE-2231
> URL: https://issues.apache.org/jira/browse/IGNITE-2231
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Alexey Goncharuk
> Labels: important
> Fix For: 1.6
>
> Attachments: EventsProcessingTest.java
>
>
> Subscribe for EVT_CACHE_OBJECT_PUT event on one node and perform 'put'
> operations from the other to an empty transnational cache.
> The subscriber will receive a notification saying that there was an old value
> for a key at the time the new was being inserted. In fact the was no an old
> value, the entry with a {{null}} as a value was generated as a part of
> implicit lock acquisition.
> This snippet of the code in {{GridCacheMapEntry}} generates a wrong event
> (innerSet function)
> {noformat}
> if (evt && newVer != null &&
> cctx.events().isRecordable(EVT_CACHE_OBJECT_PUT)) {
> CacheObject evtOld = cctx.unwrapTemporary(old);
> cctx.events().addEvent(partition(),
> key,
> evtNodeId,
> tx == null ? null : tx.xid(),
> newVer,
> EVT_CACHE_OBJECT_PUT,
> val,
> val != null,
> evtOld,
> evtOld != null || hasValueUnlocked(),
> subjId, null, taskName,
> keepBinary);
> }
> {noformat}
> Attached the test that lets reproduce the issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2200) CacheQueryExample failes after CacheClientBinaryQueryExample and vice versa
[
https://issues.apache.org/jira/browse/IGNITE-2200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-2200:
-
Fix Version/s: 1.5
> CacheQueryExample failes after CacheClientBinaryQueryExample and vice versa
> ---
>
> Key: IGNITE-2200
> URL: https://issues.apache.org/jira/browse/IGNITE-2200
> Project: Ignite
> Issue Type: Bug
>Reporter: Sergey Kozlov
>Assignee: Alexey Goncharuk
> Fix For: 1.5
>
>
> 1. Start remote node with config examples/config/example-ignite.xml
> 2. Run CacheClientBinaryQueryExample. It passed
> 3. Run CacheQueryExample. It failes:
> {noformat}
> >>> Cache query example started.
> Exception in thread "main" javax.cache.CacheException: class
> org.apache.ignite.IgniteCheckedException: Type ID collision detected
> [id=1178922291, clsName1=org.apache.ignite.examples.model.Organization,
> clsName2=org.apache.ignite.examples.model.binary.Organization]
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1618)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.cacheException(IgniteCacheProxy.java:1806)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.put(IgniteCacheProxy.java:1078)
> at
> org.apache.ignite.examples.datagrid.CacheQueryExample.initialize(CacheQueryExample.java:276)
> at
> org.apache.ignite.examples.datagrid.CacheQueryExample.main(CacheQueryExample.java:97)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at com.intellij.rt.execution.application.AppMain.main(AppMain.java:134)
> Caused by: class org.apache.ignite.IgniteCheckedException: Type ID collision
> detected [id=1178922291,
> clsName1=org.apache.ignite.examples.model.Organization,
> clsName2=org.apache.ignite.examples.model.binary.Organization]
> at
> org.apache.ignite.internal.MarshallerContextImpl.registerClassName(MarshallerContextImpl.java:116)
> at
> org.apache.ignite.internal.MarshallerContextAdapter.registerClass(MarshallerContextAdapter.java:157)
> at
> org.apache.ignite.internal.binary.BinaryContext.registerUserClassDescriptor(BinaryContext.java:576)
> at
> org.apache.ignite.internal.binary.BinaryContext.registerClassDescriptor(BinaryContext.java:555)
> at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForClass(BinaryContext.java:457)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:145)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:132)
> at
> org.apache.ignite.internal.binary.GridBinaryMarshaller.marshal(GridBinaryMarshaller.java:225)
> at
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.marshalToBinary(CacheObjectBinaryProcessorImpl.java:438)
> at
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.toBinary(CacheObjectBinaryProcessorImpl.java:777)
> at
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.toCacheObject(CacheObjectBinaryProcessorImpl.java:724)
> at
> org.apache.ignite.internal.processors.cache.GridCacheContext.toCacheObject(GridCacheContext.java:1798)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$UpdateState.mapSingleUpdate(GridNearAtomicUpdateFuture.java:1137)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$UpdateState.map(GridNearAtomicUpdateFuture.java:868)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.mapOnTopology(GridNearAtomicUpdateFuture.java:418)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.map(GridNearAtomicUpdateFuture.java:284)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$18.apply(GridDhtAtomicCache.java:924)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$18.apply(GridDhtAtomicCache.java:922)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.asyncOp(GridDhtAtomicCache.java:699)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsync0(GridDhtAtomicCache.java:922)
> at
> org.apache.
[jira] [Updated] (IGNITE-2200) CacheQueryExample failes after CacheClientBinaryQueryExample and vice versa
[
https://issues.apache.org/jira/browse/IGNITE-2200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-2200:
-
Priority: Blocker (was: Major)
> CacheQueryExample failes after CacheClientBinaryQueryExample and vice versa
> ---
>
> Key: IGNITE-2200
> URL: https://issues.apache.org/jira/browse/IGNITE-2200
> Project: Ignite
> Issue Type: Bug
>Reporter: Sergey Kozlov
>Assignee: Alexey Goncharuk
>Priority: Blocker
> Fix For: 1.5
>
>
> 1. Start remote node with config examples/config/example-ignite.xml
> 2. Run CacheClientBinaryQueryExample. It passed
> 3. Run CacheQueryExample. It failes:
> {noformat}
> >>> Cache query example started.
> Exception in thread "main" javax.cache.CacheException: class
> org.apache.ignite.IgniteCheckedException: Type ID collision detected
> [id=1178922291, clsName1=org.apache.ignite.examples.model.Organization,
> clsName2=org.apache.ignite.examples.model.binary.Organization]
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1618)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.cacheException(IgniteCacheProxy.java:1806)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.put(IgniteCacheProxy.java:1078)
> at
> org.apache.ignite.examples.datagrid.CacheQueryExample.initialize(CacheQueryExample.java:276)
> at
> org.apache.ignite.examples.datagrid.CacheQueryExample.main(CacheQueryExample.java:97)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at com.intellij.rt.execution.application.AppMain.main(AppMain.java:134)
> Caused by: class org.apache.ignite.IgniteCheckedException: Type ID collision
> detected [id=1178922291,
> clsName1=org.apache.ignite.examples.model.Organization,
> clsName2=org.apache.ignite.examples.model.binary.Organization]
> at
> org.apache.ignite.internal.MarshallerContextImpl.registerClassName(MarshallerContextImpl.java:116)
> at
> org.apache.ignite.internal.MarshallerContextAdapter.registerClass(MarshallerContextAdapter.java:157)
> at
> org.apache.ignite.internal.binary.BinaryContext.registerUserClassDescriptor(BinaryContext.java:576)
> at
> org.apache.ignite.internal.binary.BinaryContext.registerClassDescriptor(BinaryContext.java:555)
> at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForClass(BinaryContext.java:457)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:145)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:132)
> at
> org.apache.ignite.internal.binary.GridBinaryMarshaller.marshal(GridBinaryMarshaller.java:225)
> at
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.marshalToBinary(CacheObjectBinaryProcessorImpl.java:438)
> at
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.toBinary(CacheObjectBinaryProcessorImpl.java:777)
> at
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.toCacheObject(CacheObjectBinaryProcessorImpl.java:724)
> at
> org.apache.ignite.internal.processors.cache.GridCacheContext.toCacheObject(GridCacheContext.java:1798)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$UpdateState.mapSingleUpdate(GridNearAtomicUpdateFuture.java:1137)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$UpdateState.map(GridNearAtomicUpdateFuture.java:868)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.mapOnTopology(GridNearAtomicUpdateFuture.java:418)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.map(GridNearAtomicUpdateFuture.java:284)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$18.apply(GridDhtAtomicCache.java:924)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$18.apply(GridDhtAtomicCache.java:922)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.asyncOp(GridDhtAtomicCache.java:699)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsync0(GridDhtAto
[jira] [Commented] (IGNITE-2200) CacheQueryExample failes after CacheClientBinaryQueryExample and vice versa
[
https://issues.apache.org/jira/browse/IGNITE-2200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15068092#comment-15068092
]
Sergey Kozlov commented on IGNITE-2200:
---
Alexey, I just found that now CacheQueryExample failed even if it started on
clean environment: 3 remote nodes + CacheQuery Example
> CacheQueryExample failes after CacheClientBinaryQueryExample and vice versa
> ---
>
> Key: IGNITE-2200
> URL: https://issues.apache.org/jira/browse/IGNITE-2200
> Project: Ignite
> Issue Type: Bug
>Reporter: Sergey Kozlov
>Assignee: Alexey Goncharuk
>Priority: Blocker
> Fix For: 1.5
>
>
> 1. Start remote node with config examples/config/example-ignite.xml
> 2. Run CacheClientBinaryQueryExample. It passed
> 3. Run CacheQueryExample. It failes:
> {noformat}
> >>> Cache query example started.
> Exception in thread "main" javax.cache.CacheException: class
> org.apache.ignite.IgniteCheckedException: Type ID collision detected
> [id=1178922291, clsName1=org.apache.ignite.examples.model.Organization,
> clsName2=org.apache.ignite.examples.model.binary.Organization]
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1618)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.cacheException(IgniteCacheProxy.java:1806)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.put(IgniteCacheProxy.java:1078)
> at
> org.apache.ignite.examples.datagrid.CacheQueryExample.initialize(CacheQueryExample.java:276)
> at
> org.apache.ignite.examples.datagrid.CacheQueryExample.main(CacheQueryExample.java:97)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at com.intellij.rt.execution.application.AppMain.main(AppMain.java:134)
> Caused by: class org.apache.ignite.IgniteCheckedException: Type ID collision
> detected [id=1178922291,
> clsName1=org.apache.ignite.examples.model.Organization,
> clsName2=org.apache.ignite.examples.model.binary.Organization]
> at
> org.apache.ignite.internal.MarshallerContextImpl.registerClassName(MarshallerContextImpl.java:116)
> at
> org.apache.ignite.internal.MarshallerContextAdapter.registerClass(MarshallerContextAdapter.java:157)
> at
> org.apache.ignite.internal.binary.BinaryContext.registerUserClassDescriptor(BinaryContext.java:576)
> at
> org.apache.ignite.internal.binary.BinaryContext.registerClassDescriptor(BinaryContext.java:555)
> at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForClass(BinaryContext.java:457)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:145)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:132)
> at
> org.apache.ignite.internal.binary.GridBinaryMarshaller.marshal(GridBinaryMarshaller.java:225)
> at
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.marshalToBinary(CacheObjectBinaryProcessorImpl.java:438)
> at
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.toBinary(CacheObjectBinaryProcessorImpl.java:777)
> at
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.toCacheObject(CacheObjectBinaryProcessorImpl.java:724)
> at
> org.apache.ignite.internal.processors.cache.GridCacheContext.toCacheObject(GridCacheContext.java:1798)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$UpdateState.mapSingleUpdate(GridNearAtomicUpdateFuture.java:1137)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$UpdateState.map(GridNearAtomicUpdateFuture.java:868)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.mapOnTopology(GridNearAtomicUpdateFuture.java:418)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.map(GridNearAtomicUpdateFuture.java:284)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$18.apply(GridDhtAtomicCache.java:924)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$18.apply(GridDhtAtomicCache.java:922)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.asyncOp(GridDh
[jira] [Commented] (IGNITE-2230) CPP: Implement "Bind offset" feature for the ODBC driver.
[
https://issues.apache.org/jira/browse/IGNITE-2230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15068099#comment-15068099
]
Igor Sapego commented on IGNITE-2230:
-
This feature implemented by supporting attributes
{{SQL_ATTR_ROW_BIND_OFFSET_PTR}} and {{SQL_ATTR_PARAM_BIND_OFFSET_PTR}} for
functions {{SQLSetStmtAttr}} and {{SQLGetStmtAttr}}. This attributes later
transferred to {{ApplicationDataBuffer}} class during binding to be used to
access underlying data.
> CPP: Implement "Bind offset" feature for the ODBC driver.
> -
>
> Key: IGNITE-2230
> URL: https://issues.apache.org/jira/browse/IGNITE-2230
> Project: Ignite
> Issue Type: Task
> Components: odbc
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.6
>
>
> This feature listed in the [ODBC Core Interface
> Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx]
> and should be implemented for our driver.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2016) Update KafkaStreamer to fit new features introduced in Kafka 0.9
[ https://issues.apache.org/jira/browse/IGNITE-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15068100#comment-15068100 ] Roman Shtykh commented on IGNITE-2016: -- Denis, I would like to add that probably we shouldn't treat such (source-sink) integrations as Ignite data streamers to avoid confusion. It can go just under general 'integration' category. > Update KafkaStreamer to fit new features introduced in Kafka 0.9 > > > Key: IGNITE-2016 > URL: https://issues.apache.org/jira/browse/IGNITE-2016 > Project: Ignite > Issue Type: New Feature > Components: streaming >Reporter: Roman Shtykh >Assignee: Roman Shtykh > > Particularly, > - new consumer > - Kafka Connect (Copycat) > http://www.confluent.io/blog/apache-kafka-0.9-is-released > This can be a a different integration task or a complete re-write of the > current implementation, considering the fact that Kafka Connect is a new > standard way for "large-scale, real-time data import and export for Kafka." -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2202) Query result entries don't include versions
[ https://issues.apache.org/jira/browse/IGNITE-2202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-2202: Labels: important (was: ) > Query result entries don't include versions > --- > > Key: IGNITE-2202 > URL: https://issues.apache.org/jira/browse/IGNITE-2202 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Valentin Kulichenko >Priority: Critical > Labels: important > Fix For: 1.6 > > Attachments: QueryTest2.java > > > Cache entries returned as query results don't contain versions even if the > query is local. > Test attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2224) Add getEntry methods to the IgniteCache API
[
https://issues.apache.org/jira/browse/IGNITE-2224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda updated IGNITE-2224:
Labels: important newbie (was: newbie)
> Add getEntry methods to the IgniteCache API
> ---
>
> Key: IGNITE-2224
> URL: https://issues.apache.org/jira/browse/IGNITE-2224
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Reporter: Dmitriy Setrakyan
> Labels: important, newbie
> Fix For: 1.6
>
>
> We should have the following methods returning
> {{org.apache.ignite.cache.CacheEntry}}:
> {code}
> CacheEntry getEntry(K);
> Collection> getEntries(Collection);
> {code}
> These methods should be available on {{IgniteCache}} API. The returned
> entries should include the additional information available on the
> {{CacheEntry}}, like {{updateTime}} or {{version}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2116) ignite-osgi-karaf has only readme and license files
[
https://issues.apache.org/jira/browse/IGNITE-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15068126#comment-15068126
]
Raúl Kripalani commented on IGNITE-2116:
Hi [~avinogradov],
You don't need to be familiar with OSGi.
This module simply contains an XML file with placeholders that are replaced by
Maven Resource Filtering.
You just need to copy the file: {{target/classes/features.xml}} into the fabric
assembly module.
Regards,
Raúl.
> ignite-osgi-karaf has only readme and license files
> ---
>
> Key: IGNITE-2116
> URL: https://issues.apache.org/jira/browse/IGNITE-2116
> Project: Ignite
> Issue Type: Bug
> Components: build
>Affects Versions: 1.5
>Reporter: Sergey Kozlov
>Assignee: Anton Vinogradov
>Priority: Critical
> Fix For: 1.5
>
>
> {noformat}
> C:\Work\apache-ignite-fabric-1.5.0-b2-bin\libs\optional\ignite-osgi-karaf>dir
> ...
> 08.12.2015 12:34 .
> 08.12.2015 12:34 ..
> 08.12.2015 12:34 licenses
> 08.12.2015 12:34 735 README.txt
> ...
> C:\Work\apache-ignite-fabric-1.5.0-b2-bin\libs\optional\ignite-osgi-karaf>dir
> licenses
> ...
> 08.12.2015 12:34 .
> 08.12.2015 12:34 ..
> 08.12.2015 12:3411 358 apache-2.0.txt
> 08.12.2015 12:34 289 ignite-osgi-karaf-licenses.txt
> ...
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-2175) Not valid exceptions in case when example can't works with remote node started with server classpath (Java 7)
[
https://issues.apache.org/jira/browse/IGNITE-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15068145#comment-15068145
]
Anton Vinogradov edited comment on IGNITE-2175 at 12/22/15 1:58 PM:
Same fail when only one node started, and it's started from terminal.
was (Author: avinogradov):
Same fail when only one node started, and i's started from terminal.
> Not valid exceptions in case when example can't works with remote node
> started with server classpath (Java 7)
> -
>
> Key: IGNITE-2175
> URL: https://issues.apache.org/jira/browse/IGNITE-2175
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 1.5
> Environment: jdk 1.7
> OS X 10.10.2
>Reporter: Ilya Suntsov
>Assignee: Anton Vinogradov
>Priority: Critical
> Fix For: 1.5
>
>
> Steps for reproduce:
> 1. Start one node form IDEA and one more from terminal
> 2. Run StreamVisitorExample.
> Exception:
> {noformat}
> 16:41:23,807][SEVERE][pub-#13%null%][DataStreamProcessor] Failed to finish
> update job.
> javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException:
> org.apache.ignite.examples.streaming.StreamVisitorExample$Instrument
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1634)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.cacheException(IgniteCacheProxy.java:1806)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.get(IgniteCacheProxy.java:870)
> at
> org.apache.ignite.examples.streaming.StreamVisitorExample$1.apply(StreamVisitorExample.java:83)
> at
> org.apache.ignite.examples.streaming.StreamVisitorExample$1.apply(StreamVisitorExample.java:77)
> at org.apache.ignite.stream.StreamVisitor.receive(StreamVisitor.java:38)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerUpdateJob.call(DataStreamerUpdateJob.java:137)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.processRequest(DataStreamProcessor.java:298)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.access$000(DataStreamProcessor.java:49)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor$1.onMessage(DataStreamProcessor.java:76)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:819)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1600(GridIoManager.java:103)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:782)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: class org.apache.ignite.IgniteCheckedException:
> org.apache.ignite.examples.streaming.StreamVisitorExample$Instrument
> at
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7005)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:166)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:115)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4522)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1378)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProxyImpl.get(GridCacheProxyImpl.java:299)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.get(IgniteCacheProxy.java:863)
> ... 13 more
> Caused by: java.lang.ClassNotFoundException:
> org.apache.ignite.examples.streaming.StreamVisitorExample$Instrument
> at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:274)
> at
> org.apache.ignite.internal.util.IgniteUtils.forName(IgniteUtils.java:8172)
> at
> org.apache.ignite.internal.MarshallerContextAdapter.getClass(MarshallerContextAdapter.ja
[jira] [Commented] (IGNITE-2175) Not valid exceptions in case when example can't works with remote node started with server classpath (Java 7)
[
https://issues.apache.org/jira/browse/IGNITE-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15068145#comment-15068145
]
Anton Vinogradov commented on IGNITE-2175:
--
Same fail when only one node started, and i's started from terminal.
> Not valid exceptions in case when example can't works with remote node
> started with server classpath (Java 7)
> -
>
> Key: IGNITE-2175
> URL: https://issues.apache.org/jira/browse/IGNITE-2175
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 1.5
> Environment: jdk 1.7
> OS X 10.10.2
>Reporter: Ilya Suntsov
>Assignee: Anton Vinogradov
>Priority: Critical
> Fix For: 1.5
>
>
> Steps for reproduce:
> 1. Start one node form IDEA and one more from terminal
> 2. Run StreamVisitorExample.
> Exception:
> {noformat}
> 16:41:23,807][SEVERE][pub-#13%null%][DataStreamProcessor] Failed to finish
> update job.
> javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException:
> org.apache.ignite.examples.streaming.StreamVisitorExample$Instrument
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1634)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.cacheException(IgniteCacheProxy.java:1806)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.get(IgniteCacheProxy.java:870)
> at
> org.apache.ignite.examples.streaming.StreamVisitorExample$1.apply(StreamVisitorExample.java:83)
> at
> org.apache.ignite.examples.streaming.StreamVisitorExample$1.apply(StreamVisitorExample.java:77)
> at org.apache.ignite.stream.StreamVisitor.receive(StreamVisitor.java:38)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerUpdateJob.call(DataStreamerUpdateJob.java:137)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.processRequest(DataStreamProcessor.java:298)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.access$000(DataStreamProcessor.java:49)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor$1.onMessage(DataStreamProcessor.java:76)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:819)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1600(GridIoManager.java:103)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:782)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: class org.apache.ignite.IgniteCheckedException:
> org.apache.ignite.examples.streaming.StreamVisitorExample$Instrument
> at
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7005)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:166)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:115)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4522)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1378)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProxyImpl.get(GridCacheProxyImpl.java:299)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.get(IgniteCacheProxy.java:863)
> ... 13 more
> Caused by: java.lang.ClassNotFoundException:
> org.apache.ignite.examples.streaming.StreamVisitorExample$Instrument
> at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:274)
> at
> org.apache.ignite.internal.util.IgniteUtils.forName(IgniteUtils.java:8172)
> at
> org.apache.ignite.internal.MarshallerContextAdapter.getClass(MarshallerContextAdapter.java:185)
> at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:458)
> at
> org.apache.ignite.inte
[jira] [Assigned] (IGNITE-2116) ignite-osgi-karaf has only readme and license files
[
https://issues.apache.org/jira/browse/IGNITE-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov reassigned IGNITE-2116:
Assignee: Raúl Kripalani (was: Anton Vinogradov)
Done,
Please check
> ignite-osgi-karaf has only readme and license files
> ---
>
> Key: IGNITE-2116
> URL: https://issues.apache.org/jira/browse/IGNITE-2116
> Project: Ignite
> Issue Type: Bug
> Components: build
>Affects Versions: 1.5
>Reporter: Sergey Kozlov
>Assignee: Raúl Kripalani
>Priority: Critical
> Fix For: 1.5
>
>
> {noformat}
> C:\Work\apache-ignite-fabric-1.5.0-b2-bin\libs\optional\ignite-osgi-karaf>dir
> ...
> 08.12.2015 12:34 .
> 08.12.2015 12:34 ..
> 08.12.2015 12:34 licenses
> 08.12.2015 12:34 735 README.txt
> ...
> C:\Work\apache-ignite-fabric-1.5.0-b2-bin\libs\optional\ignite-osgi-karaf>dir
> licenses
> ...
> 08.12.2015 12:34 .
> 08.12.2015 12:34 ..
> 08.12.2015 12:3411 358 apache-2.0.txt
> 08.12.2015 12:34 289 ignite-osgi-karaf-licenses.txt
> ...
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-2232) Whole-product optimziations.
Vladimir Ozerov created IGNITE-2232: --- Summary: Whole-product optimziations. Key: IGNITE-2232 URL: https://issues.apache.org/jira/browse/IGNITE-2232 Project: Ignite Issue Type: Task Components: general Affects Versions: ignite-1.4 Reporter: Vladimir Ozerov Priority: Critical Fix For: 1.6 This is the top-level ticket for the bunch of optimizations in Ignite internals. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2219) ClassCastException from NodeIdMessage to AffinityTopologyVersion
[
https://issues.apache.org/jira/browse/IGNITE-2219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noam Liran updated IGNITE-2219:
---
Attachment: message-hex.txt
> ClassCastException from NodeIdMessage to AffinityTopologyVersion
>
>
> Key: IGNITE-2219
> URL: https://issues.apache.org/jira/browse/IGNITE-2219
> Project: Ignite
> Issue Type: Bug
>Affects Versions: ignite-1.4
> Environment: Ubuntu 12.04 64 bit
> java version "1.8.0_60"
> Java(TM) SE Runtime Environment (build 1.8.0_60-b27)
> Java HotSpot(TM) 64-Bit Server VM (build 25.60-b23, mixed mode)
> Ignite 1.4.0
>Reporter: Avihai Berkovitz
> Attachments: message-hex.txt
>
>
> We had a cluster up and running for a couple of days. Without doing anything
> new, we got the following error in one of the nodes:
> {noformat}
> Caught unhandled exception in NIO worker thread (restart the node).
> java.lang.ClassCastException:
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi$NodeIdMessage
> cannot be cast to
> org.apache.ignite.internal.processors.affinity.AffinityTopologyVersion
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsFullMessage.readFrom(GridDhtPartitionsFullMessage.java:176)
> ~[ignite-core-1.4.0.jar:1.4.0]
> at
> org.apache.ignite.internal.direct.DirectByteBufferStream.readMessage(DirectByteBufferStream.java:963)
> ~[ignite-core-1.4.0.jar:1.4.0]
> at
> org.apache.ignite.internal.direct.DirectMessageReader.readMessage(DirectMessageReader.java:252)
> ~[ignite-core-1.4.0.jar:1.4.0]
> at
> org.apache.ignite.internal.managers.communication.GridIoMessage.readFrom(GridIoMessage.java:249)
> ~[ignite-core-1.4.0.jar:1.4.0]
> at
> org.apache.ignite.internal.util.nio.GridDirectParser.decode(GridDirectParser.java:79)
> ~[ignite-core-1.4.0.jar:1.4.0]
> at
> org.apache.ignite.internal.util.nio.GridNioCodecFilter.onMessageReceived(GridNioCodecFilter.java:104)
> ~[ignite-core-1.4.0.jar:1.4.0]
> at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:107)
> ~[ignite-core-1.4.0.jar:1.4.0]
> at
> org.apache.ignite.internal.util.nio.GridConnectionBytesVerifyFilter.onMessageReceived(GridConnectionBytesVerifyFilter.java:78)
> ~[ignite-core-1.4.0.jar:1.4.0]
> at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:107)
> ~[ignite-core-1.4.0.jar:1.4.0]
> at
> org.apache.ignite.internal.util.nio.GridNioServer$HeadFilter.onMessageReceived(GridNioServer.java:2124)
> ~[ignite-core-1.4.0.jar:1.4.0]
> at
> org.apache.ignite.internal.util.nio.GridNioFilterChain.onMessageReceived(GridNioFilterChain.java:173)
> ~[ignite-core-1.4.0.jar:1.4.0]
> at
> org.apache.ignite.internal.util.nio.GridNioServer$DirectNioClientWorker.processRead(GridNioServer.java:898)
> ~[ignite-core-1.4.0.jar:1.4.0]
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeys(GridNioServer.java:1437)
> ~[ignite-core-1.4.0.jar:1.4.0]
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:1379)
> ~[ignite-core-1.4.0.jar:1.4.0]
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1263)
> ~[ignite-core-1.4.0.jar:1.4.0]
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> [ignite-core-1.4.0.jar:1.4.0]
> at java.lang.Thread.run(Thread.java:745) [na:1.8.0_60]
> {noformat}
> It happened only once so far, but killed the communication from this node.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-2233) Avoid boxing in BinaryContext collections
Vladimir Ozerov created IGNITE-2233: --- Summary: Avoid boxing in BinaryContext collections Key: IGNITE-2233 URL: https://issues.apache.org/jira/browse/IGNITE-2233 Project: Ignite Issue Type: Sub-task Components: general Affects Versions: ignite-1.4 Reporter: Vladimir Ozerov Assignee: Vladimir Ozerov Fix For: 1.6 The following methods generate visible GC pressure due to constant boxing of int keys: BinaryContext.descriptorForTypeId BinaryContext.userTypeIdMapper BinaryContext.schemaRegistry Possilbe solutions: 1) int -> Object maps (e.g. see Martin Thompson's Argona lib). 2) COW semantics instead of concurrent maps/sets as these collections are updated only during warmup. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2234) GridCacheMvccManager.contextReset() generates garbage.
Vladimir Ozerov created IGNITE-2234: --- Summary: GridCacheMvccManager.contextReset() generates garbage. Key: IGNITE-2234 URL: https://issues.apache.org/jira/browse/IGNITE-2234 Project: Ignite Issue Type: Sub-task Components: general Affects Versions: ignite-1.4 Reporter: Vladimir Ozerov Assignee: Vladimir Ozerov Fix For: 1.6 GridCacheMvccManager.contextReset() method operates on a thread-local LinkedList. Only two operations are used: "add" and "getLast". Once cache op is finished, it is reset - new LinkedList is created. Proposed solution: 1) Use TLS (array + index) instead of LinkedList; 2) Reset = (set index to 0) + (nullify all previous elements). The latter is needed because GridCacheMvccCandidate migth contain references to cache entries. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2235) GridNioServer$AbstractNioClientWorker,changeReqs can be changed to queue.
Vladimir Ozerov created IGNITE-2235: --- Summary: GridNioServer$AbstractNioClientWorker,changeReqs can be changed to queue. Key: IGNITE-2235 URL: https://issues.apache.org/jira/browse/IGNITE-2235 Project: Ignite Issue Type: Sub-task Components: general Affects Versions: ignite-1.4 Reporter: Vladimir Ozerov Assignee: Vladimir Ozerov Fix For: 1.6 GridNioServer$AbstractNioClientWorker,changeReqs is ConcurrentLinkedDeque8 currently. But: 1) It is used as queue, so more we can change it to ConcurrentLinkedQueue safely; 2) It has MPSC semantics, so may be we can employ more efficient algos here. E.g. http://www.1024cores.net/home/lock-free-algorithms/queues/non-intrusive-mpsc-node-based-queue which is used in Aeron and Akka. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2236) Simplify GridCompoundFuture.
Vladimir Ozerov created IGNITE-2236: --- Summary: Simplify GridCompoundFuture. Key: IGNITE-2236 URL: https://issues.apache.org/jira/browse/IGNITE-2236 Project: Ignite Issue Type: Sub-task Components: general Affects Versions: ignite-1.4 Reporter: Vladimir Ozerov Assignee: Vladimir Ozerov Priority: Critical Fix For: 1.6 Compount future is integral part of Ignite async/reactive design. However, it seems to be too heavy and inefficient. Need to evaluate possible ways to simplify and optimzie it. Particularly, the following methods generate a lot garbage: 1) 2) add 3) Listener.apply() But much more things could be improved here. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-2219) ClassCastException from NodeIdMessage to AffinityTopologyVersion
[
https://issues.apache.org/jira/browse/IGNITE-2219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15068213#comment-15068213
]
Noam Liran commented on IGNITE-2219:
We added debug prints in
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsFullMessage.readFrom(GridDhtPartitionsFullMessage.java)
and now have the problematic buffer;
We've attached the full message buffer at this point in hex; we also think
these log lines are relevant:
{noformat}
2015-12-22 14:21:11.800 WARN o.a.i.s.c.tcp.TcpCommunicationSpi
tcp-comm-worker-#1%null ctx: actor: - Connect timed out
(consider increasing 'failureDetectionTimeout' configuration property)
[addr=/0:0:0:0:0:0:0:1%lo:47105, failureDetectionTimeout=1]
2015-12-22 14:21:11.800 WARN o.a.i.s.c.tcp.TcpCommunicationSpi
tcp-comm-worker-#1%null ctx: actor: - Connect timed out
(consider increasing 'failureDetectionTimeout' configuration property)
[addr=/127.0.0.1:47105, failureDetectionTimeout=1]
2015-12-22 14:21:11.801 WARN o.a.i.s.c.tcp.TcpCommunicationSpi
tcp-comm-worker-#1%null ctx: actor: - Failed to connect
to a remote node (make sure that destination node is alive and operating system
firewall is disabled on local and remote hosts)
[addrs=[ip-10-0-1-62.eu-west-1.compute.internal/10.0.1.62:47105,
/0:0:0:0:0:0:0:1%lo:47105, /127.0.0.1:47105]]
2015-12-22 14:21:11.807 WARN o.a.i.i.p.c.GridCachePartitionExchangeManager
ignite-#23%sys-null% ctx: actor: - Failed to send
partitions full message [node=TcpDiscoveryNode
[id=fe615af4-4935-4edb-a947-cc431e97ea48, addrs=[0:0:0:0:0:0:0:1%lo, 10.0.1.62,
127.0.0.1], sockAddrs=[ip-10-0-1-62.eu-west-1.compute.internal/10.0.1.62:47504,
/0:0:0:0:0:0:0:1%lo:47504, /10.0.1.62:47504, /127.0.0.1:47504], discPort=47504,
order=10, intOrder=10, lastExchangeTime=1450793971531, loc=false,
ver=1.4.0#20150924-sha1:c2def5f6, isClient=false], err=class
o.a.i.IgniteCheckedException: Failed to send message (node may have left the
grid or TCP connection cannot be established due to firewall issues)
[node=TcpDiscoveryNode [id=fe615af4-4935-4edb-a947-cc431e97ea48,
addrs=[0:0:0:0:0:0:0:1%lo, 10.0.1.62, 127.0.0.1],
sockAddrs=[ip-10-0-1-62.eu-west-1.compute.internal/10.0.1.62:47504,
/0:0:0:0:0:0:0:1%lo:47504, /10.0.1.62:47504, /127.0.0.1:47504], discPort=47504,
order=10, intOrder=10, lastExchangeTime=1450793971531, loc=false,
ver=1.4.0#20150924-sha1:c2def5f6, isClient=false], topic=TOPIC_CACHE,
msg=GridDhtPartitionsFullMessage [parts={218603958=GridDhtPartitionFullMap
[nodeId=d2c6b831-09ca-426b-8de7-84a05157a752, nodeOrder=1, updateSeq=451,
size=18], 816937872=GridDhtPartitionFullMap
[nodeId=d2c6b831-09ca-426b-8de7-84a05157a752, nodeOrder=1, updateSeq=446,
size=18], -2100569601=GridDhtPartitionFullMap
[nodeId=d2c6b831-09ca-426b-8de7-84a05157a752, nodeOrder=1, updateSeq=464,
size=18], 689859866=GridDhtPartitionFullMap
[nodeId=d2c6b831-09ca-426b-8de7-84a05157a752, nodeOrder=1, updateSeq=467,
size=18], -423204530=GridDhtPartitionFullMap
[nodeId=d2c6b831-09ca-426b-8de7-84a05157a752, nodeOrder=1, updateSeq=462,
size=18], 1325947219=GridDhtPartitionFullMap
[nodeId=d2c6b831-09ca-426b-8de7-84a05157a752, nodeOrder=1, updateSeq=464,
size=18], 1059659892=GridDhtPartitionFullMap
[nodeId=d2c6b831-09ca-426b-8de7-84a05157a752, nodeOrder=1, updateSeq=459,
size=18]}, topVer=AffinityTopologyVersion [topVer=-1, minorTopVer=0],
partCnt=7, super=GridDhtPartitionsAbstractMessage [exchId=null, lastVer=null,
super=GridCacheMessage [msgId=909, depInfo=null, err=null,
skipPrepare=false]]], policy=2]]
{noformat}
The *really* interesting thing we found is this: in the full buffer, the first
field is the length of partsBytes: {{521F0100}} = {{0x00011f52}} = {{73554}}.
If you skip it (+ 4 bytes for the length itself) you get to this part of the
buffer:
{{FF0002000800}}
Since the first byte is 0xFF, it is being deserialized as {{NodeIdMessage}}
even though {{GridDhtPartitionsFullMessage}} mandates that at this point only
{{AffinityTopologyVersion}} should be found.
The thing is that, if you look a bit before that in the buffer you can actually
find {{AffinityTopologyVersion}}: {noformat}
... 41FC41FD41FE41FF41 6F
0002000800
{noformat}
Obviously something is a miss here: either partsBytes' length is 12 bytes too
long, or 12 bytes went missing somewhere.
Regards,
Noam and [~avihai.berkov...@microsoft.com]
> ClassCastException from NodeIdMessage to AffinityTopologyVersion
>
>
> Key: IGNITE-2219
> URL: https://issues.apache.org/jira/browse/IGNITE-2219
> Project: Ignite
> Issue Type: Bug
>Affects Vers
[jira] [Created] (IGNITE-2237) GridFutureAdapter: simplify and optimize.
Vladimir Ozerov created IGNITE-2237: --- Summary: GridFutureAdapter: simplify and optimize. Key: IGNITE-2237 URL: https://issues.apache.org/jira/browse/IGNITE-2237 Project: Ignite Issue Type: Sub-task Components: general Affects Versions: ignite-1.4 Reporter: Vladimir Ozerov Assignee: Vladimir Ozerov Priority: Critical Fix For: 1.6 The following ideas is to be evaluated: 1) "startTime" and "endTime" fields have virtually no value. They are used mostly for debug and tests. 2) "ignoreInterrupts" flag can be encapsulated into state. 3) "ArrayListener" concept looks overly complex. Looks like we do not need it at all -> array can be used directly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2237) GridFutureAdapter: simplify and optimize.
[ https://issues.apache.org/jira/browse/IGNITE-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-2237: Description: The following ideas is to be evaluated: 1) "startTime" and "endTime" fields have virtually no value. They are used mostly for debug and tests. 2) "ignoreInterrupts" flag can be encapsulated into state. 3) "ArrayListener" concept looks overly complex. Looks like we do not need it at all -> array can be used directly. 4) Modern JDK futures do not use AQS anymore. Instead, they park/unpark directly and store waiters in a kind of compact stack. Need to think about it. was: The following ideas is to be evaluated: 1) "startTime" and "endTime" fields have virtually no value. They are used mostly for debug and tests. 2) "ignoreInterrupts" flag can be encapsulated into state. 3) "ArrayListener" concept looks overly complex. Looks like we do not need it at all -> array can be used directly. > GridFutureAdapter: simplify and optimize. > - > > Key: IGNITE-2237 > URL: https://issues.apache.org/jira/browse/IGNITE-2237 > Project: Ignite > Issue Type: Sub-task > Components: general >Affects Versions: ignite-1.4 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Critical > Fix For: 1.6 > > > The following ideas is to be evaluated: > 1) "startTime" and "endTime" fields have virtually no value. They are used > mostly for debug and tests. > 2) "ignoreInterrupts" flag can be encapsulated into state. > 3) "ArrayListener" concept looks overly complex. Looks like we do not need it > at all -> array can be used directly. > 4) Modern JDK futures do not use AQS anymore. Instead, they park/unpark > directly and store waiters in a kind of compact stack. Need to think about it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2238) CPP: Implement basic cursor operations for the ODBC driver.
Igor Sapego created IGNITE-2238:
---
Summary: CPP: Implement basic cursor operations for the ODBC
driver.
Key: IGNITE-2238
URL: https://issues.apache.org/jira/browse/IGNITE-2238
Project: Ignite
Issue Type: Task
Components: odbc
Reporter: Igor Sapego
Assignee: Igor Sapego
Fix For: 1.6
This feature listed in the [ODBC Core Interface
Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx]
and should be implemented for our driver. It includes implementation of the
following functions:
- {{SQLCloseCursor}};
- {{SQLGetCursorName}};
- {{SQLSetCursorName}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2238) CPP: Implement basic cursor operations for the ODBC driver.
[
https://issues.apache.org/jira/browse/IGNITE-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15068266#comment-15068266
]
Igor Sapego commented on IGNITE-2238:
-
{{SQLCloseCursor}} is implemented.
{{SQLGetCursorName}} and {{SQLSetCursorName}} can not be implemented currently
because Ignite does not support named cursors.
> CPP: Implement basic cursor operations for the ODBC driver.
> ---
>
> Key: IGNITE-2238
> URL: https://issues.apache.org/jira/browse/IGNITE-2238
> Project: Ignite
> Issue Type: Task
> Components: odbc
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.6
>
>
> This feature listed in the [ODBC Core Interface
> Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx]
> and should be implemented for our driver. It includes implementation of the
> following functions:
> - {{SQLCloseCursor}};
> - {{SQLGetCursorName}};
> - {{SQLSetCursorName}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2238) CPP: Implement basic cursor operations for the ODBC driver.
[
https://issues.apache.org/jira/browse/IGNITE-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego updated IGNITE-2238:
Assignee: (was: Igor Sapego)
> CPP: Implement basic cursor operations for the ODBC driver.
> ---
>
> Key: IGNITE-2238
> URL: https://issues.apache.org/jira/browse/IGNITE-2238
> Project: Ignite
> Issue Type: Task
> Components: odbc
>Reporter: Igor Sapego
> Fix For: 1.6
>
>
> This feature listed in the [ODBC Core Interface
> Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx]
> and should be implemented for our driver. It includes implementation of the
> following functions:
> - {{SQLCloseCursor}};
> - {{SQLGetCursorName}};
> - {{SQLSetCursorName}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-2239) CPP: Implement SQLConnect function for the ODBC driver.
Igor Sapego created IGNITE-2239: --- Summary: CPP: Implement SQLConnect function for the ODBC driver. Key: IGNITE-2239 URL: https://issues.apache.org/jira/browse/IGNITE-2239 Project: Ignite Issue Type: Task Components: odbc Reporter: Igor Sapego Assignee: Igor Sapego Fix For: 1.6 This function is listed in the [ODBC Core Interface Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx] and should be implemented for our driver. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-2239) CPP: Implement SQLConnect function for the ODBC driver.
[
https://issues.apache.org/jira/browse/IGNITE-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15068320#comment-15068320
]
Igor Sapego commented on IGNITE-2239:
-
Implemented as follows:
- If the {{ServerName}} argument is equals default DSN name then trying to
establish connection with default parameters.
- If the {{ServerName}} argument is not equals default DSN name then return
error.
- All function parameters except of {{ServerName}} and {{ConnectionHandle}} are
ignored.
> CPP: Implement SQLConnect function for the ODBC driver.
> ---
>
> Key: IGNITE-2239
> URL: https://issues.apache.org/jira/browse/IGNITE-2239
> Project: Ignite
> Issue Type: Task
> Components: odbc
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.6
>
>
> This function is listed in the [ODBC Core Interface
> Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx]
> and should be implemented for our driver.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-2239) CPP: Implement SQLConnect function for the ODBC driver.
[
https://issues.apache.org/jira/browse/IGNITE-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15068320#comment-15068320
]
Igor Sapego edited comment on IGNITE-2239 at 12/22/15 4:11 PM:
---
Implemented as follows:
- If the {{ServerName}} argument is equals default DSN name then trying to
establish connection with default parameters.
- If the {{ServerName}} argument is not equals default DSN name then return
error.
- All function parameters except of {{ServerName}}, {{ServerNameLength}} and
{{ConnectionHandle}} are ignored.
was (Author: isapego):
Implemented as follows:
- If the {{ServerName}} argument is equals default DSN name then trying to
establish connection with default parameters.
- If the {{ServerName}} argument is not equals default DSN name then return
error.
- All function parameters except of {{ServerName}} and {{ConnectionHandle}} are
ignored.
> CPP: Implement SQLConnect function for the ODBC driver.
> ---
>
> Key: IGNITE-2239
> URL: https://issues.apache.org/jira/browse/IGNITE-2239
> Project: Ignite
> Issue Type: Task
> Components: odbc
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.6
>
>
> This function is listed in the [ODBC Core Interface
> Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx]
> and should be implemented for our driver.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2202) Query result entries don't include versions
[ https://issues.apache.org/jira/browse/IGNITE-2202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Setrakyan updated IGNITE-2202: -- Fix Version/s: (was: 1.6) > Query result entries don't include versions > --- > > Key: IGNITE-2202 > URL: https://issues.apache.org/jira/browse/IGNITE-2202 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Valentin Kulichenko >Priority: Critical > Labels: important > Attachments: QueryTest2.java > > > Cache entries returned as query results don't contain versions even if the > query is local. > Test attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-2202) Query result entries don't include versions
[ https://issues.apache.org/jira/browse/IGNITE-2202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15068349#comment-15068349 ] Dmitriy Setrakyan commented on IGNITE-2202: --- This ticket needs to be properly designed, as always including version into query results may hurt performance. One idea was to have a configuration flag which will control whether a cache entry on the client side should be unwrappable or not. > Query result entries don't include versions > --- > > Key: IGNITE-2202 > URL: https://issues.apache.org/jira/browse/IGNITE-2202 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Valentin Kulichenko >Priority: Critical > Labels: important > Attachments: QueryTest2.java > > > Cache entries returned as query results don't contain versions even if the > query is local. > Test attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2240) CPP: Implement SQLEndTran function for the ODBC driver.
Igor Sapego created IGNITE-2240: --- Summary: CPP: Implement SQLEndTran function for the ODBC driver. Key: IGNITE-2240 URL: https://issues.apache.org/jira/browse/IGNITE-2240 Project: Ignite Issue Type: Task Components: odbc Reporter: Igor Sapego Assignee: Igor Sapego Fix For: 1.6 This function listed in the [ODBC Core Interface Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx] and should be implemented for our driver. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-2240) CPP: Implement SQLEndTran function for the ODBC driver.
[ https://issues.apache.org/jira/browse/IGNITE-2240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15068369#comment-15068369 ] Igor Sapego commented on IGNITE-2240: - It is not necessary to implement true transactions; therefore, the application cannot specify SQL_ROLLBACK nor SQL_AUTOCOMMIT_OFF for the SQL_ATTR_AUTOCOMMIT connection attribute. So we only need to support SQL_COMMIT. > CPP: Implement SQLEndTran function for the ODBC driver. > --- > > Key: IGNITE-2240 > URL: https://issues.apache.org/jira/browse/IGNITE-2240 > Project: Ignite > Issue Type: Task > Components: odbc >Reporter: Igor Sapego >Assignee: Igor Sapego > Fix For: 1.6 > > > This function listed in the [ODBC Core Interface > Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx] > and should be implemented for our driver. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-2202) Query result entries don't include versions
[ https://issues.apache.org/jira/browse/IGNITE-2202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15068425#comment-15068425 ] Andrey Kornev commented on IGNITE-2202: --- I think this ticket aimed at solving one particular issue: if a query is local (as specified by the Query.isLocal()) then the entry version must be available. Just doing this would really help me a lot. > Query result entries don't include versions > --- > > Key: IGNITE-2202 > URL: https://issues.apache.org/jira/browse/IGNITE-2202 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Valentin Kulichenko >Priority: Critical > Labels: important > Attachments: QueryTest2.java > > > Cache entries returned as query results don't contain versions even if the > query is local. > Test attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-2219) ClassCastException from NodeIdMessage to AffinityTopologyVersion
[
https://issues.apache.org/jira/browse/IGNITE-2219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15068644#comment-15068644
]
Noam Liran commented on IGNITE-2219:
I think we know what the issue is.
The oldest node frequently sends full partition maps to other nodes in the
cluster.
This is done in {{sendAllPartitions()}} in
{{GridCachePartitionExchangeManager}} which is called on several occasions.
{{sendAllPartitions()}} creates a {{GridDhtPartitionsFullMessage}} and
populates it with the full partition maps.
Notice these are complex objects that are stored by reference.
It then iterates over all nodes in the cluster and sends the message to them,
one by one, asynchronously using {{cctx.io().sendNoRetry()}}.
This, in turn, calls {{GridDhtPartitionsFullMessage.prepareMarshal()}} for each
node separately (on the same message object).
If the maps somehow change, this will cause partsBytes (the serialized version
of the maps) to change *even though* some writers might have already started
sending it to other nodes.
Specifically, if the byte array length was already written in one packet and
the array changes to a different size, the written size will reflect the size
of the *new* array rather the old one and essentially cause a corruption of the
message.
We think this issue might actually happen frequently with other messages as
well since it is easy to overlook.
We thought that creating a separate message instance for each node might be a
quick fix for this but we're not sure if there are side effects for this.
Regards and Happy Christmas / Novy God!
Noam and [~avihai.berkov...@microsoft.com]
> ClassCastException from NodeIdMessage to AffinityTopologyVersion
>
>
> Key: IGNITE-2219
> URL: https://issues.apache.org/jira/browse/IGNITE-2219
> Project: Ignite
> Issue Type: Bug
>Affects Versions: ignite-1.4
> Environment: Ubuntu 12.04 64 bit
> java version "1.8.0_60"
> Java(TM) SE Runtime Environment (build 1.8.0_60-b27)
> Java HotSpot(TM) 64-Bit Server VM (build 25.60-b23, mixed mode)
> Ignite 1.4.0
>Reporter: Avihai Berkovitz
> Attachments: message-hex.txt
>
>
> We had a cluster up and running for a couple of days. Without doing anything
> new, we got the following error in one of the nodes:
> {noformat}
> Caught unhandled exception in NIO worker thread (restart the node).
> java.lang.ClassCastException:
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi$NodeIdMessage
> cannot be cast to
> org.apache.ignite.internal.processors.affinity.AffinityTopologyVersion
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsFullMessage.readFrom(GridDhtPartitionsFullMessage.java:176)
> ~[ignite-core-1.4.0.jar:1.4.0]
> at
> org.apache.ignite.internal.direct.DirectByteBufferStream.readMessage(DirectByteBufferStream.java:963)
> ~[ignite-core-1.4.0.jar:1.4.0]
> at
> org.apache.ignite.internal.direct.DirectMessageReader.readMessage(DirectMessageReader.java:252)
> ~[ignite-core-1.4.0.jar:1.4.0]
> at
> org.apache.ignite.internal.managers.communication.GridIoMessage.readFrom(GridIoMessage.java:249)
> ~[ignite-core-1.4.0.jar:1.4.0]
> at
> org.apache.ignite.internal.util.nio.GridDirectParser.decode(GridDirectParser.java:79)
> ~[ignite-core-1.4.0.jar:1.4.0]
> at
> org.apache.ignite.internal.util.nio.GridNioCodecFilter.onMessageReceived(GridNioCodecFilter.java:104)
> ~[ignite-core-1.4.0.jar:1.4.0]
> at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:107)
> ~[ignite-core-1.4.0.jar:1.4.0]
> at
> org.apache.ignite.internal.util.nio.GridConnectionBytesVerifyFilter.onMessageReceived(GridConnectionBytesVerifyFilter.java:78)
> ~[ignite-core-1.4.0.jar:1.4.0]
> at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:107)
> ~[ignite-core-1.4.0.jar:1.4.0]
> at
> org.apache.ignite.internal.util.nio.GridNioServer$HeadFilter.onMessageReceived(GridNioServer.java:2124)
> ~[ignite-core-1.4.0.jar:1.4.0]
> at
> org.apache.ignite.internal.util.nio.GridNioFilterChain.onMessageReceived(GridNioFilterChain.java:173)
> ~[ignite-core-1.4.0.jar:1.4.0]
> at
> org.apache.ignite.internal.util.nio.GridNioServer$DirectNioClientWorker.processRead(GridNioServer.java:898)
> ~[ignite-core-1.4.0.jar:1.4.0]
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeys(GridNioServer.java:1437)
> ~[ignite-core-1.4.0.jar:1.4.0]
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:1379)
> ~[ignite-core-1.4.0.jar:1.4.0]
> at
> org.apache.ignit
[jira] [Assigned] (IGNITE-2116) ignite-osgi-karaf has only readme and license files
[
https://issues.apache.org/jira/browse/IGNITE-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov reassigned IGNITE-2116:
-
Assignee: Sergey Kozlov (was: Raúl Kripalani)
> ignite-osgi-karaf has only readme and license files
> ---
>
> Key: IGNITE-2116
> URL: https://issues.apache.org/jira/browse/IGNITE-2116
> Project: Ignite
> Issue Type: Bug
> Components: build
>Affects Versions: 1.5
>Reporter: Sergey Kozlov
>Assignee: Sergey Kozlov
>Priority: Critical
> Fix For: 1.5
>
>
> {noformat}
> C:\Work\apache-ignite-fabric-1.5.0-b2-bin\libs\optional\ignite-osgi-karaf>dir
> ...
> 08.12.2015 12:34 .
> 08.12.2015 12:34 ..
> 08.12.2015 12:34 licenses
> 08.12.2015 12:34 735 README.txt
> ...
> C:\Work\apache-ignite-fabric-1.5.0-b2-bin\libs\optional\ignite-osgi-karaf>dir
> licenses
> ...
> 08.12.2015 12:34 .
> 08.12.2015 12:34 ..
> 08.12.2015 12:3411 358 apache-2.0.txt
> 08.12.2015 12:34 289 ignite-osgi-karaf-licenses.txt
> ...
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (IGNITE-2116) ignite-osgi-karaf has only readme and license files
[
https://issues.apache.org/jira/browse/IGNITE-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov resolved IGNITE-2116.
---
Resolution: Fixed
As reporter I assigned the issue to myself
> ignite-osgi-karaf has only readme and license files
> ---
>
> Key: IGNITE-2116
> URL: https://issues.apache.org/jira/browse/IGNITE-2116
> Project: Ignite
> Issue Type: Bug
> Components: build
>Affects Versions: 1.5
>Reporter: Sergey Kozlov
>Assignee: Sergey Kozlov
>Priority: Critical
> Fix For: 1.5
>
>
> {noformat}
> C:\Work\apache-ignite-fabric-1.5.0-b2-bin\libs\optional\ignite-osgi-karaf>dir
> ...
> 08.12.2015 12:34 .
> 08.12.2015 12:34 ..
> 08.12.2015 12:34 licenses
> 08.12.2015 12:34 735 README.txt
> ...
> C:\Work\apache-ignite-fabric-1.5.0-b2-bin\libs\optional\ignite-osgi-karaf>dir
> licenses
> ...
> 08.12.2015 12:34 .
> 08.12.2015 12:34 ..
> 08.12.2015 12:3411 358 apache-2.0.txt
> 08.12.2015 12:34 289 ignite-osgi-karaf-licenses.txt
> ...
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (IGNITE-2116) ignite-osgi-karaf has only readme and license files
[
https://issues.apache.org/jira/browse/IGNITE-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov closed IGNITE-2116.
-
> ignite-osgi-karaf has only readme and license files
> ---
>
> Key: IGNITE-2116
> URL: https://issues.apache.org/jira/browse/IGNITE-2116
> Project: Ignite
> Issue Type: Bug
> Components: build
>Affects Versions: 1.5
>Reporter: Sergey Kozlov
>Assignee: Sergey Kozlov
>Priority: Critical
> Fix For: 1.5
>
>
> {noformat}
> C:\Work\apache-ignite-fabric-1.5.0-b2-bin\libs\optional\ignite-osgi-karaf>dir
> ...
> 08.12.2015 12:34 .
> 08.12.2015 12:34 ..
> 08.12.2015 12:34 licenses
> 08.12.2015 12:34 735 README.txt
> ...
> C:\Work\apache-ignite-fabric-1.5.0-b2-bin\libs\optional\ignite-osgi-karaf>dir
> licenses
> ...
> 08.12.2015 12:34 .
> 08.12.2015 12:34 ..
> 08.12.2015 12:3411 358 apache-2.0.txt
> 08.12.2015 12:34 289 ignite-osgi-karaf-licenses.txt
> ...
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2241) CPP: Implement SQLGEtTypeInfo function for the ODBC driver.
[ https://issues.apache.org/jira/browse/IGNITE-2241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-2241: Issue Type: Task (was: Bug) > CPP: Implement SQLGEtTypeInfo function for the ODBC driver. > --- > > Key: IGNITE-2241 > URL: https://issues.apache.org/jira/browse/IGNITE-2241 > Project: Ignite > Issue Type: Task > Components: odbc >Reporter: Igor Sapego >Assignee: Igor Sapego > Fix For: 1.6 > > > This function is listed in the [ODBC Core Interface > Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx] > and should be implemented for our driver. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2241) CPP: Implement SQLGEtTypeInfo function for the ODBC driver.
Igor Sapego created IGNITE-2241: --- Summary: CPP: Implement SQLGEtTypeInfo function for the ODBC driver. Key: IGNITE-2241 URL: https://issues.apache.org/jira/browse/IGNITE-2241 Project: Ignite Issue Type: Bug Components: odbc Reporter: Igor Sapego Assignee: Igor Sapego Fix For: 1.6 This function is listed in the [ODBC Core Interface Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx] and should be implemented for our driver. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2242) CPP: Implement SQLGetData function for the ODBC driver.
Igor Sapego created IGNITE-2242: --- Summary: CPP: Implement SQLGetData function for the ODBC driver. Key: IGNITE-2242 URL: https://issues.apache.org/jira/browse/IGNITE-2242 Project: Ignite Issue Type: Task Components: odbc Reporter: Igor Sapego Assignee: Igor Sapego Fix For: 1.6 This function listed in the [ODBC Core Interface Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx] and should be implemented for our driver. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2243) CPP: Implement Environment attributes manipulation for the ODBC driver.
Igor Sapego created IGNITE-2243: --- Summary: CPP: Implement Environment attributes manipulation for the ODBC driver. Key: IGNITE-2243 URL: https://issues.apache.org/jira/browse/IGNITE-2243 Project: Ignite Issue Type: Task Components: odbc Reporter: Igor Sapego Assignee: Igor Sapego Fix For: 1.6 This function listed in the [ODBC Core Interface Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx] and should be implemented for our driver. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2243) CPP: Implement Environment attributes manipulation for the ODBC driver.
[
https://issues.apache.org/jira/browse/IGNITE-2243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego updated IGNITE-2243:
Description:
This feature listed in the [ODBC Core Interface
Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx]
and should be implemented for our driver.
The list of functions that should be implemented:
- {{SQLGetEnvAttr}}
- {{SQLSetEnvAttr}}
The minimum list of attributes that should be supported:
- {{SQL_ATTR_ODBC_VER}}
was:This function listed in the [ODBC Core Interface
Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx]
and should be implemented for our driver.
> CPP: Implement Environment attributes manipulation for the ODBC driver.
> ---
>
> Key: IGNITE-2243
> URL: https://issues.apache.org/jira/browse/IGNITE-2243
> Project: Ignite
> Issue Type: Task
> Components: odbc
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.6
>
>
> This feature listed in the [ODBC Core Interface
> Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx]
> and should be implemented for our driver.
> The list of functions that should be implemented:
> - {{SQLGetEnvAttr}}
> - {{SQLSetEnvAttr}}
> The minimum list of attributes that should be supported:
> - {{SQL_ATTR_ODBC_VER}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-2244) CPP: Implement Connection attributes manipulation for the ODBC driver.
Igor Sapego created IGNITE-2244:
---
Summary: CPP: Implement Connection attributes manipulation for the
ODBC driver.
Key: IGNITE-2244
URL: https://issues.apache.org/jira/browse/IGNITE-2244
Project: Ignite
Issue Type: Task
Components: odbc
Reporter: Igor Sapego
Assignee: Igor Sapego
Fix For: 1.6
This feature listed in the [ODBC Core Interface
Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx]
and should be implemented for our driver.
The list of functions that should be implemented:
- {{SQLGetEnvAttr}}
- {{SQLSetEnvAttr}}
The minimum list of attributes that should be supported:
- {{SQL_ATTR_ACCESS_MODE}}
- {{SQL_ATTR_ACCESS_MODE}}
- {{SQL_ATTR_ACCESS_MODE}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2244) CPP: Implement Connection attributes manipulation for the ODBC driver.
[
https://issues.apache.org/jira/browse/IGNITE-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego updated IGNITE-2244:
Description:
This feature listed in the [ODBC Core Interface
Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx]
and should be implemented for our driver.
The list of functions that should be implemented:
- {{SQLGetConnectAttr}}
- {{SQLSetConnectAttr}}
The minimum list of attributes that should be supported:
- {{SQL_ATTR_ACCESS_MODE}}
- {{SQL_ATTR_ODBC_CURSORS}}
- {{SQL_ATTR_QUIET_MODE}}
- {{SQL_ATTR_TRACE}}
- {{SQL_ATTR_TRACEFILE}}
- {{SQL_ATTR_TRANSLATE_LIB}}
- {{SQL_ATTR_TRANSLATE_OPTION}}
was:
This feature listed in the [ODBC Core Interface
Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx]
and should be implemented for our driver.
The list of functions that should be implemented:
- {{SQLGetEnvAttr}}
- {{SQLSetEnvAttr}}
The minimum list of attributes that should be supported:
- {{SQL_ATTR_ACCESS_MODE}}
- {{SQL_ATTR_ACCESS_MODE}}
- {{SQL_ATTR_ACCESS_MODE}}
> CPP: Implement Connection attributes manipulation for the ODBC driver.
> --
>
> Key: IGNITE-2244
> URL: https://issues.apache.org/jira/browse/IGNITE-2244
> Project: Ignite
> Issue Type: Task
> Components: odbc
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.6
>
>
> This feature listed in the [ODBC Core Interface
> Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx]
> and should be implemented for our driver.
> The list of functions that should be implemented:
> - {{SQLGetConnectAttr}}
> - {{SQLSetConnectAttr}}
> The minimum list of attributes that should be supported:
> - {{SQL_ATTR_ACCESS_MODE}}
> - {{SQL_ATTR_ODBC_CURSORS}}
> - {{SQL_ATTR_QUIET_MODE}}
> - {{SQL_ATTR_TRACE}}
> - {{SQL_ATTR_TRACEFILE}}
> - {{SQL_ATTR_TRANSLATE_LIB}}
> - {{SQL_ATTR_TRANSLATE_OPTION}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-2245) CPP: Implement Statement attributes manipulation for the ODBC driver.
Igor Sapego created IGNITE-2245:
---
Summary: CPP: Implement Statement attributes manipulation for the
ODBC driver.
Key: IGNITE-2245
URL: https://issues.apache.org/jira/browse/IGNITE-2245
Project: Ignite
Issue Type: Task
Components: odbc
Reporter: Igor Sapego
Assignee: Igor Sapego
Fix For: 1.6
This feature listed in the [ODBC Core Interface
Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx]
and should be implemented for our driver.
The list of functions that should be implemented:
- {{SQLGetStmtAttr}}
- {{SQLSetStmtAttr}}
The minimum list of attributes that should be supported:
- {{SQL_ATTR_APP_PARAM_DESC}}
- {{SQL_ATTR_APP_ROW_DESC}}
- {{SQL_ATTR_IMP_PARAM_DESC}}
- {{SQL_ATTR_IMP_ROW_DESC}}
- {{SQL_ATTR_METADATA_ID}}
- {{SQL_ATTR_NOSCAN}}
- {{SQL_ATTR_PARAM_BIND_OFFSET_PTR}}
- {{SQL_ATTR_PARAM_BIND_TYPE}}
- {{SQL_ATTR_PARAM_OPERATION_PTR}}
- {{SQL_ATTR_PARAM_STATUS_PTR}}
- {{SQL_ATTR_PARAMS_PROCESSED_PTR}}
- {{SQL_ATTR_PARAMSET_SIZE}}
- {{SQL_ATTR_ROW_ARRAY_SIZE}}
- {{SQL_ATTR_ROW_BIND_OFFSET_PTR}}
- {{SQL_ATTR_ROW_BIND_TYPE}}
- {{SQL_ATTR_ROW_STATUS_PTR}}
- {{SQL_ATTR_ROWS_FETCHED_PTR}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2245) CPP: Implement Statement attributes manipulation for the ODBC driver.
[
https://issues.apache.org/jira/browse/IGNITE-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15068801#comment-15068801
]
Igor Sapego commented on IGNITE-2245:
-
Following attributes are already implemented:
- {{SQL_ATTR_APP_PARAM_DESC}}
- {{SQL_ATTR_APP_ROW_DESC}}
- {{SQL_ATTR_IMP_PARAM_DESC}}
- {{SQL_ATTR_IMP_ROW_DESC}}
- {{SQL_ATTR_PARAM_BIND_OFFSET_PTR}}
- {{SQL_ATTR_ROW_ARRAY_SIZE}}
- {{SQL_ATTR_ROW_BIND_OFFSET_PTR}}
- {{SQL_ATTR_ROW_BIND_TYPE}}
- {{SQL_ATTR_ROW_STATUS_PTR}}
- {{SQL_ATTR_ROWS_FETCHED_PTR}}
Need to implement:
- {{SQL_ATTR_METADATA_ID}}
- {{SQL_ATTR_NOSCAN}}
- {{SQL_ATTR_PARAM_BIND_TYPE}}
- {{SQL_ATTR_PARAM_OPERATION_PTR}}
- {{SQL_ATTR_PARAM_STATUS_PTR}}
- {{SQL_ATTR_PARAMS_PROCESSED_PTR}}
- {{SQL_ATTR_PARAMSET_SIZE}}
> CPP: Implement Statement attributes manipulation for the ODBC driver.
> -
>
> Key: IGNITE-2245
> URL: https://issues.apache.org/jira/browse/IGNITE-2245
> Project: Ignite
> Issue Type: Task
> Components: odbc
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.6
>
>
> This feature listed in the [ODBC Core Interface
> Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx]
> and should be implemented for our driver.
> The list of functions that should be implemented:
> - {{SQLGetStmtAttr}}
> - {{SQLSetStmtAttr}}
> The minimum list of attributes that should be supported:
> - {{SQL_ATTR_APP_PARAM_DESC}}
> - {{SQL_ATTR_APP_ROW_DESC}}
> - {{SQL_ATTR_IMP_PARAM_DESC}}
> - {{SQL_ATTR_IMP_ROW_DESC}}
> - {{SQL_ATTR_METADATA_ID}}
> - {{SQL_ATTR_NOSCAN}}
> - {{SQL_ATTR_PARAM_BIND_OFFSET_PTR}}
> - {{SQL_ATTR_PARAM_BIND_TYPE}}
> - {{SQL_ATTR_PARAM_OPERATION_PTR}}
> - {{SQL_ATTR_PARAM_STATUS_PTR}}
> - {{SQL_ATTR_PARAMS_PROCESSED_PTR}}
> - {{SQL_ATTR_PARAMSET_SIZE}}
> - {{SQL_ATTR_ROW_ARRAY_SIZE}}
> - {{SQL_ATTR_ROW_BIND_OFFSET_PTR}}
> - {{SQL_ATTR_ROW_BIND_TYPE}}
> - {{SQL_ATTR_ROW_STATUS_PTR}}
> - {{SQL_ATTR_ROWS_FETCHED_PTR}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-2246) CPP: Implement Descriptors support for the ODBC driver.
Igor Sapego created IGNITE-2246:
---
Summary: CPP: Implement Descriptors support for the ODBC driver.
Key: IGNITE-2246
URL: https://issues.apache.org/jira/browse/IGNITE-2246
Project: Ignite
Issue Type: Task
Components: odbc
Reporter: Igor Sapego
Assignee: Igor Sapego
Fix For: 1.6
This feature listed in the [ODBC Core Interface
Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx]
and should be implemented for our driver.
This includes implementation of the following functions:
- {{SQLCopyDesc}}
- {{SQLGetDescField}}
- {{SQLGetDescRec}}
- {{SQLSetDescField}}
- {{SQLSetDescRec}}
Following header fields:
- {{SQL_DESC_ALLOC_TYPE}}
- {{SQL_DESC_ARRAY_SIZE}}
- {{SQL_DESC_ARRAY_STATUS_PTR}}
- {{SQL_DESC_BIND_OFFSET_PTR}}
- {{SQL_DESC_BIND_TYPE}}
- {{SQL_DESC_COUNT}}
- {{SQL_DESC_ROWS_PROCESSED_PTR}}
Following record fields:
- {{SQL_DESC_BASE_COLUMN_NAME}}
- {{SQL_DESC_CASE_SENSITIVE}}
- {{SQL_DESC_CONCISE_TYPE}}
- {{SQL_DESC_DATA_PTR}}
- {{SQL_DESC_DATETIME_INTERVAL_ CODE}}
- {{SQL_DESC_DATETIME_INTERVAL_ PRECISION}}
- {{SQL_DESC_DISPLAY_SIZE}}
- {{SQL_DESC_FIXED_PREC_SCALE}}
- {{SQL_DESC_INDICATOR_PTR}}
- {{SQL_DESC_LENGTH}}
- {{SQL_DESC_LITERAL_PREFIX}}
- {{SQL_DESC_LITERAL_SUFFIX}}
- {{SQL_DESC_LOCAL_TYPE_NAME}}
- {{SQL_DESC_NAME}}
- {{SQL_DESC_NULLABLE}}
- {{SQL_DESC_OCTET_LENGTH}}
- {{SQL_DESC_OCTET_LENGTH_PTR}}
- {{SQL_DESC_PARAMETER_TYPE}}
- {{SQL_DESC_PRECISION}}
- {{SQL_DESC_SCALE}}
- {{SQL_DESC_SEARCHABLE}}
- {{SQL_DESC_TYPE}}
- {{SQL_DESC_TYPE_NAME}}
- {{SQL_DESC_UNNAMED}}
- {{SQL_DESC_UNSIGNED}}
- {{SQL_DESC_UPDATABLE}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-2247) CPP: Implement error handling for the ODBC driver.
Igor Sapego created IGNITE-2247:
---
Summary: CPP: Implement error handling for the ODBC driver.
Key: IGNITE-2247
URL: https://issues.apache.org/jira/browse/IGNITE-2247
Project: Ignite
Issue Type: Task
Components: odbc
Reporter: Igor Sapego
Assignee: Igor Sapego
Fix For: 1.6
This feature listed in the [ODBC Core Interface
Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx]
and should be implemented for our driver.
The list of functions that should be implemented:
- {{SQLGetDiagField}}
- {{SQLGetDiagRec}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-2248) CPP: Implement obtaining the row-identifying column of tables for the ODBC driver.
Igor Sapego created IGNITE-2248:
---
Summary: CPP: Implement obtaining the row-identifying column of
tables for the ODBC driver.
Key: IGNITE-2248
URL: https://issues.apache.org/jira/browse/IGNITE-2248
Project: Ignite
Issue Type: Task
Components: odbc
Reporter: Igor Sapego
Assignee: Igor Sapego
Fix For: 1.6
This feature listed in the [ODBC Core Interface
Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx]
and should be implemented for our driver.
This means implementing obtaining the {{SQL_BEST_ROWID}} row-identifying column
of tables, by calling {{SQLSpecialColumns}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2241) CPP: Implement SQLGetTypeInfo function for the ODBC driver.
[ https://issues.apache.org/jira/browse/IGNITE-2241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-2241: Summary: CPP: Implement SQLGetTypeInfo function for the ODBC driver. (was: CPP: Implement SQLGEtTypeInfo function for the ODBC driver.) > CPP: Implement SQLGetTypeInfo function for the ODBC driver. > --- > > Key: IGNITE-2241 > URL: https://issues.apache.org/jira/browse/IGNITE-2241 > Project: Ignite > Issue Type: Task > Components: odbc >Reporter: Igor Sapego >Assignee: Igor Sapego > Fix For: 1.6 > > > This function is listed in the [ODBC Core Interface > Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx] > and should be implemented for our driver. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-2070) "Back to Clusters" link doesn't work on Security page
[ https://issues.apache.org/jira/browse/IGNITE-2070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov closed IGNITE-2070. -- Assignee: (was: Pavel Konstantinov) Tested > "Back to Clusters" link doesn't work on Security page > - > > Key: IGNITE-2070 > URL: https://issues.apache.org/jira/browse/IGNITE-2070 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Pavel Konstantinov > Fix For: 1.6 > > > Nothing happens when I clicking on it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-2211) Console SQL tab with wrong address.
[ https://issues.apache.org/jira/browse/IGNITE-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov closed IGNITE-2211. -- Assignee: (was: Pavel Konstantinov) Tested > Console SQL tab with wrong address. > --- > > Key: IGNITE-2211 > URL: https://issues.apache.org/jira/browse/IGNITE-2211 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.5 >Reporter: Vasiliy Sisko > Fix For: 1.6 > > > # Open some notebook. > # Change notebook id in URL to non-existent. > We can see empty notebook, but expect to see some error page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2249) Services are sometimes deserialized on client
Valentin Kulichenko created IGNITE-2249: --- Summary: Services are sometimes deserialized on client Key: IGNITE-2249 URL: https://issues.apache.org/jira/browse/IGNITE-2249 Project: Ignite Issue Type: Bug Components: managed services Reporter: Valentin Kulichenko Assignee: Valentin Kulichenko Priority: Critical Fix For: 1.6 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-2249) Services are sometimes deserialized on client
[ https://issues.apache.org/jira/browse/IGNITE-2249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15069171#comment-15069171 ] ASF GitHub Bot commented on IGNITE-2249: GitHub user vkulichenko opened a pull request: https://github.com/apache/ignite/pull/364 IGNITE-2249 - Do not deserialize services on client node You can merge this pull request into a Git repository by running: $ git pull https://github.com/vkulichenko/incubator-ignite ignite-2249 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/364.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 #364 commit 2467df505a6e550dc0c9225f5f669167a86a9c97 Author: Valentin Kulichenko Date: 2015-12-23T05:39:37Z IGNITE-2249 - Do not deserialize services on client node > Services are sometimes deserialized on client > - > > Key: IGNITE-2249 > URL: https://issues.apache.org/jira/browse/IGNITE-2249 > Project: Ignite > Issue Type: Bug > Components: managed services >Reporter: Valentin Kulichenko >Assignee: Valentin Kulichenko >Priority: Critical > Fix For: 1.6 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-2213) Handle duplicate field names in BinaryMarshaller.
[
https://issues.apache.org/jira/browse/IGNITE-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov resolved IGNITE-2213.
-
Roman, thanks for noticing it. Fixed.
> Handle duplicate field names in BinaryMarshaller.
> -
>
> Key: IGNITE-2213
> URL: https://issues.apache.org/jira/browse/IGNITE-2213
> Project: Ignite
> Issue Type: Bug
> Components: general, interop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Blocker
> Fix For: 1.5
>
>
> Consider the following scenario:
> {code}
> class A {
> int field;
> }
> class B : class A {
> int field;
> }
> {code}
> In this case BinaryMarshaller will throw an exception about duplicate field
> names. And there is no sensible workaround for user.
> We can add some prefix/suffix to comflicting fields. E.g. A.field will be
> written as "field", B.field will be written as "field_B".
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2149) Build Apache Ignite failed for Java8
[
https://issues.apache.org/jira/browse/IGNITE-2149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15069204#comment-15069204
]
Sergey Kozlov commented on IGNITE-2149:
---
{noformat}
[01:57:48] : [exec] [ERROR]
COMPILATION ERROR :
[01:57:48] : [exec] [INFO]
-
[01:57:49] : [exec] [ERROR]
/home/teamcity/buildAgent/work/4b78de95608af2b1/apache-ignite/modules/core/src/test/java/org/apache/ignite/internal/binary/BinaryMarshallerSelfTest.java:[2342,9]
reference to assertEquals is ambiguous
[01:57:49] : [exec] both method
assertEquals(java.lang.Object,java.lang.Object) in junit.framework.TestCase and
method assertEquals(int,int) in junit.framework.TestCase match
[01:57:49] : [exec] [ERROR]
/home/teamcity/buildAgent/work/4b78de95608af2b1/apache-ignite/modules/core/src/test/java/org/apache/ignite/internal/binary/BinaryMarshallerSelfTest.java:[2343,9]
reference to assertEquals is ambiguous
[01:57:49] : [exec] both method
assertEquals(java.lang.Object,java.lang.Object) in junit.framework.TestCase and
method assertEquals(int,int) in junit.framework.TestCase match
[01:57:49] : [exec] [ERROR]
/home/teamcity/buildAgent/work/4b78de95608af2b1/apache-ignite/modules/core/src/test/java/org/apache/ignite/internal/binary/BinaryMarshallerSelfTest.java:[2366,9]
reference to assertEquals is ambiguous
[01:57:49] : [exec] both method
assertEquals(java.lang.Object,java.lang.Object) in junit.framework.TestCase and
method assertEquals(int,int) in junit.framework.TestCase match
[01:57:49] : [exec] [ERROR]
/home/teamcity/buildAgent/work/4b78de95608af2b1/apache-ignite/modules/core/src/test/java/org/apache/ignite/internal/binary/BinaryMarshallerSelfTest.java:[2367,9]
reference to assertEquals is ambiguous
[01:57:49] : [exec] both method
assertEquals(java.lang.Object,java.lang.Object) in junit.framework.TestCase and
method assertEquals(int,int) in junit.framework.TestCase match
[01:57:49] : [exec] [INFO] 4 errors
{noformat}
> Build Apache Ignite failed for Java8
>
>
> Key: IGNITE-2149
> URL: https://issues.apache.org/jira/browse/IGNITE-2149
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.5
>Reporter: Sergey Kozlov
>Assignee: Sergey Kozlov
>Priority: Blocker
> Fix For: 1.5
>
>
> {noformat}
> [19:20:12] : [exec] [WARNING]
> COMPILATION WARNING :
> [19:20:12] : [exec] [INFO]
> -
> [19:20:12] : [exec] [WARNING]
> /home/teamcity/buildAgent/work/4b78de95608af2b1/apache-ignite/modules/indexing/src/test/java/org/apache/ignite/internal/processors/cache/ttl/CacheTtlAbstractSelfTest.java:
> Some input files use unchecked or unsafe operations.
> [19:20:12] : [exec] [WARNING]
> /home/teamcity/buildAgent/work/4b78de95608af2b1/apache-ignite/modules/indexing/src/test/java/org/apache/ignite/internal/processors/cache/ttl/CacheTtlAbstractSelfTest.java:
> Recompile with -Xlint:unchecked for details.
> [19:20:12] : [exec] [INFO] 2
> warnings
> [19:20:12] : [exec] [INFO]
> -
> [19:20:12] : [exec] [INFO]
> -
> [19:20:12] : [exec] [ERROR]
> COMPILATION ERROR :
> [19:20:12] : [exec] [INFO]
> -
> [19:20:12] : [exec] [ERROR]
> /home/teamcity/buildAgent/work/4b78de95608af2b1/apache-ignite/modules/indexing/src/test/java/org/apache/ignite/internal/processors/cache/IgniteBinaryObjectFieldsQuerySelfTest.java:[213,17]
> reference to assertEquals is ambiguous
> [19:20:12] : [exec] both method
> assertEquals(java.lang.Object,java.lang.Object) in junit.framework.TestCase
> and method assertEquals(int,int) in junit.framework.TestCase match
> [19:20:12] :
[jira] [Closed] (IGNITE-2213) Handle duplicate field names in BinaryMarshaller.
[
https://issues.apache.org/jira/browse/IGNITE-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov closed IGNITE-2213.
---
> Handle duplicate field names in BinaryMarshaller.
> -
>
> Key: IGNITE-2213
> URL: https://issues.apache.org/jira/browse/IGNITE-2213
> Project: Ignite
> Issue Type: Bug
> Components: general, interop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Blocker
> Fix For: 1.5
>
>
> Consider the following scenario:
> {code}
> class A {
> int field;
> }
> class B : class A {
> int field;
> }
> {code}
> In this case BinaryMarshaller will throw an exception about duplicate field
> names. And there is no sensible workaround for user.
> We can add some prefix/suffix to comflicting fields. E.g. A.field will be
> written as "field", B.field will be written as "field_B".
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2149) Build Apache Ignite failed for Java8
[
https://issues.apache.org/jira/browse/IGNITE-2149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov updated IGNITE-2149:
--
Assignee: (was: Sergey Kozlov)
> Build Apache Ignite failed for Java8
>
>
> Key: IGNITE-2149
> URL: https://issues.apache.org/jira/browse/IGNITE-2149
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.5
>Reporter: Sergey Kozlov
>Priority: Blocker
> Fix For: 1.5
>
>
> {noformat}
> [19:20:12] : [exec] [WARNING]
> COMPILATION WARNING :
> [19:20:12] : [exec] [INFO]
> -
> [19:20:12] : [exec] [WARNING]
> /home/teamcity/buildAgent/work/4b78de95608af2b1/apache-ignite/modules/indexing/src/test/java/org/apache/ignite/internal/processors/cache/ttl/CacheTtlAbstractSelfTest.java:
> Some input files use unchecked or unsafe operations.
> [19:20:12] : [exec] [WARNING]
> /home/teamcity/buildAgent/work/4b78de95608af2b1/apache-ignite/modules/indexing/src/test/java/org/apache/ignite/internal/processors/cache/ttl/CacheTtlAbstractSelfTest.java:
> Recompile with -Xlint:unchecked for details.
> [19:20:12] : [exec] [INFO] 2
> warnings
> [19:20:12] : [exec] [INFO]
> -
> [19:20:12] : [exec] [INFO]
> -
> [19:20:12] : [exec] [ERROR]
> COMPILATION ERROR :
> [19:20:12] : [exec] [INFO]
> -
> [19:20:12] : [exec] [ERROR]
> /home/teamcity/buildAgent/work/4b78de95608af2b1/apache-ignite/modules/indexing/src/test/java/org/apache/ignite/internal/processors/cache/IgniteBinaryObjectFieldsQuerySelfTest.java:[213,17]
> reference to assertEquals is ambiguous
> [19:20:12] : [exec] both method
> assertEquals(java.lang.Object,java.lang.Object) in junit.framework.TestCase
> and method assertEquals(int,int) in junit.framework.TestCase match
> [19:20:12] : [exec] [INFO] 1 error
> [19:20:12] : [exec] [INFO]
> -
> [19:20:12] : [exec] [INFO]
>
> [19:20:12] : [exec] [INFO] Reactor
> Summary:
> [19:20:12] : [exec] [INFO]
> [19:20:12] : [exec] [INFO]
> ignite-apache-license-gen . SUCCESS [1.177s]
> [19:20:12] : [exec] [INFO]
> ignite-tools .. SUCCESS [6.047s]
> [19:20:12] : [exec] [INFO]
> ignite-core ... SUCCESS [1:11.104s]
> [19:20:12] : [exec] [INFO]
> ignite-log4j .. SUCCESS [1.929s]
> [19:20:12] : [exec] [INFO]
> ignite-urideploy .. SUCCESS [2.380s]
> [19:20:12] : [exec] [INFO]
> ignite-spring . SUCCESS [2.634s]
> [19:20:12] : [exec] [INFO]
> ignite-hadoop . SUCCESS [5.968s]
> [19:20:12] : [exec] [INFO]
> ignite-extdata-p2p SUCCESS [2.085s]
> [19:20:12] : [exec] [INFO]
> ignite-extdata-uri-dep SUCCESS [1.272s]
> [19:20:12] : [exec] [INFO]
> ignite-extdata-uri SUCCESS [0.388s]
> [19:20:12] : [exec] [INFO]
> ignite-indexing ... FAILURE [1.375s]
> [19:20:12] : [exec] [INFO]
> ignite-rest-http .. SKIPPED
> [19:20:12] : [exec] [INFO]
> ignite-clients SKIPPED
> [19:20:12] :
[jira] [Updated] (IGNITE-2202) Local server query result doesn't include versions in entries
[ https://issues.apache.org/jira/browse/IGNITE-2202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-2202: Fix Version/s: 1.6 > Local server query result doesn't include versions in entries > - > > Key: IGNITE-2202 > URL: https://issues.apache.org/jira/browse/IGNITE-2202 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Valentin Kulichenko >Priority: Critical > Labels: important > Fix For: 1.6 > > Attachments: QueryTest2.java > > > Cache entries returned as query results don't contain versions even if the > query is local. > Test attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-2202) Local server query result doesn't include versions in entries
[ https://issues.apache.org/jira/browse/IGNITE-2202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15069219#comment-15069219 ] Valentin Kulichenko commented on IGNITE-2202: - This ticket is about local query on server (changed title to more informative). Moved back to 1.6 > Local server query result doesn't include versions in entries > - > > Key: IGNITE-2202 > URL: https://issues.apache.org/jira/browse/IGNITE-2202 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Valentin Kulichenko >Priority: Critical > Labels: important > Fix For: 1.6 > > Attachments: QueryTest2.java > > > Cache entries returned as query results don't contain versions even if the > query is local. > Test attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2202) Local server query result doesn't include versions in entries
[ https://issues.apache.org/jira/browse/IGNITE-2202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-2202: Summary: Local server query result doesn't include versions in entries (was: Query result entries don't include versions) > Local server query result doesn't include versions in entries > - > > Key: IGNITE-2202 > URL: https://issues.apache.org/jira/browse/IGNITE-2202 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Valentin Kulichenko >Priority: Critical > Labels: important > Fix For: 1.6 > > Attachments: QueryTest2.java > > > Cache entries returned as query results don't contain versions even if the > query is local. > Test attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-2226) Replace dash in 1.5.0-final with dot 1.5.0.final
[ https://issues.apache.org/jira/browse/IGNITE-2226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov resolved IGNITE-2226. -- Resolution: Fixed > Replace dash in 1.5.0-final with dot 1.5.0.final > > > Key: IGNITE-2226 > URL: https://issues.apache.org/jira/browse/IGNITE-2226 > Project: Ignite > Issue Type: Bug > Components: build >Reporter: Dmitriy Setrakyan >Assignee: Anton Vinogradov >Priority: Blocker > Fix For: 1.5 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-2226) Replace dash in 1.5.0-final with dot 1.5.0.final
[ https://issues.apache.org/jira/browse/IGNITE-2226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov closed IGNITE-2226. Done > Replace dash in 1.5.0-final with dot 1.5.0.final > > > Key: IGNITE-2226 > URL: https://issues.apache.org/jira/browse/IGNITE-2226 > Project: Ignite > Issue Type: Bug > Components: build >Reporter: Dmitriy Setrakyan >Assignee: Anton Vinogradov >Priority: Blocker > Fix For: 1.5 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-2220) upgrade gulp tasks
[ https://issues.apache.org/jira/browse/IGNITE-2220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15069254#comment-15069254 ] ASF GitHub Bot commented on IGNITE-2220: GitHub user Dmitriyff opened a pull request: https://github.com/apache/ignite/pull/365 IGNITE-2220 added support to eslint You can merge this pull request into a Git repository by running: $ git pull https://github.com/Dmitriyff/ignite ignite-2220 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/365.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 #365 commit 9681cf1334b5b32558de7dcbc655a5013e9d1cab Author: Dmitriyff Date: 2015-12-22T02:59:20Z IGNITE-2220 added support eslint commit 6148eca7ea844b8ffbcd5354b285931cf22d3569 Author: Dmitriyff Date: 2015-12-22T08:50:58Z IGNITE-2220 pretify js files commit d043d7210215d36028e3e940b5f86fedfda52d2c Author: Dmitriyff Date: 2015-12-23T06:58:15Z IGNITE-2220 added check js style to task bundle commit 7e7486039c3cb1256eab9189a9ab9b5b6084ff3f Author: Dmitriyff Date: 2015-12-23T06:58:31Z Merge branch 'ignite-843-rc2' of https://github.com/apache/ignite into ignite-2220 > upgrade gulp tasks > -- > > Key: IGNITE-2220 > URL: https://issues.apache.org/jira/browse/IGNITE-2220 > Project: Ignite > Issue Type: Sub-task >Affects Versions: 1.6 >Reporter: Dmitriyff >Assignee: Dmitriyff > Fix For: 1.6 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-2217) Add BinaryConfiguration support to cluster screen
[ https://issues.apache.org/jira/browse/IGNITE-2217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov reassigned IGNITE-2217: Assignee: Alexey Kuznetsov (was: Vasiliy Sisko) > Add BinaryConfiguration support to cluster screen > - > > Key: IGNITE-2217 > URL: https://issues.apache.org/jira/browse/IGNITE-2217 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov > Fix For: 1.6 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2250) Client section on Summary contains ServerConfigurationFactory java class
[ https://issues.apache.org/jira/browse/IGNITE-2250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov updated IGNITE-2250: --- Assignee: Alexey Kuznetsov > Client section on Summary contains ServerConfigurationFactory java class > > > Key: IGNITE-2250 > URL: https://issues.apache.org/jira/browse/IGNITE-2250 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Alexey Kuznetsov > Fix For: 1.6 > > > Should contain ClientConfigurationFactory -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2250) Client section on Summary contains ServerConfigurationFactory java class
Pavel Konstantinov created IGNITE-2250: -- Summary: Client section on Summary contains ServerConfigurationFactory java class Key: IGNITE-2250 URL: https://issues.apache.org/jira/browse/IGNITE-2250 Project: Ignite Issue Type: Sub-task Reporter: Pavel Konstantinov Should contain ClientConfigurationFactory -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2251) Please add a tooltip on Client Summary on POJO tab...
Pavel Konstantinov created IGNITE-2251: -- Summary: Please add a tooltip on Client Summary on POJO tab... Key: IGNITE-2251 URL: https://issues.apache.org/jira/browse/IGNITE-2251 Project: Ignite Issue Type: Sub-task Reporter: Pavel Konstantinov Assignee: Alexey Kuznetsov ...for 'Generate constructors' and 'Include key fields' checkboxes -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-2202) Local server query result doesn't include versions in entries
[
https://issues.apache.org/jira/browse/IGNITE-2202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15069362#comment-15069362
]
Denis Magda commented on IGNITE-2202:
-
Finally, the following should be supported.
- if {{Query.isLocal() == true}} then it must be possible to obtain a versioned
entry from the result set on a server node that executed a query;
- make sure to throw {{UnsupportedOperationException}} if {{unwrap}} is called
on client nodes.
> Local server query result doesn't include versions in entries
> -
>
> Key: IGNITE-2202
> URL: https://issues.apache.org/jira/browse/IGNITE-2202
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Reporter: Valentin Kulichenko
>Priority: Critical
> Labels: important
> Fix For: 1.6
>
> Attachments: QueryTest2.java
>
>
> Cache entries returned as query results don't contain versions even if the
> query is local.
> Test attached.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
