[jira] [Created] (IGNITE-4750) SQL: Support GROUP_CONCAT function

[Denis Magda (JIRA)]

Denis Magda created IGNITE-4750:
---

 Summary: SQL: Support GROUP_CONCAT function
 Key: IGNITE-4750
 URL: https://issues.apache.org/jira/browse/IGNITE-4750
 Project: Ignite
  Issue Type: Task
Reporter: Denis Magda


GROUP_CONCAT function is not supported at the moment. Makes sense to fill this 
gap:
http://apache-ignite-users.70518.x6.nabble.com/GROUP-CONCAT-function-is-unsupported-td10757.html



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

[jira] [Commented] (IGNITE-4587) Discontinue and remove CacheAtomicWriteOrderMode.CLOCK mode

[Andrey Gura (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-4587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15880836#comment-15880836
 ] 

Andrey Gura commented on IGNITE-4587:
-

Hi, [~dreamx]

I've reviewed your pull request. First of all, please merge the latest changes 
from master branch. 

See my comments bellow:

# {{CacheAtomicWriteOrderMode}} enum contains now only one value {{PRIMARY}}. 
Given the fact that this enum makes sense only for atomic cache I would prefer 
to remove this enum. But better way is to discuss this on dev list. If there 
are no any objectives then we can just remove this enum and all methods' 
parameters of this type.
# {{GridDhtAtomicCache}} class {{isFastMap}} method always returns {{false}} 
now. So this method is also candidate for removal. 
# {{GridNearAtomicSingleUpdateFuture}} class {{mapSingleUpdate}} method. 
Parameter {{updVer}} is always {{null}} now. Please remove this parameter. Also 
please make sure that this parameter make sense for requests that will be 
created in this method. It seems that 
{{GridNearAtomicSingleUpdateFuture.updVer}} doesn't make sense also.
# {{GridNearAtomicUpdateFuture}} class. The same issue as for previous item but 
for {{mapSingleUpdate}} and {{mapUpdate}} methods and {{updVer}} parameter.

> Discontinue and remove CacheAtomicWriteOrderMode.CLOCK mode
> ---
>
> Key: IGNITE-4587
> URL: https://issues.apache.org/jira/browse/IGNITE-4587
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Denis Magda
>Assignee: Maksim Kozlov
> Fix For: 2.0
>
>
> {{CacheAtomicWriteOrderMode.CLOCK}} proved to be harmful in production due to 
> timing issues.
> It makes sense to remove it completely in 2.0 release. Migration guide has be 
> updated:
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0+Migration+Guide



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

[jira] [Updated] (IGNITE-3429) org.hibernate.cache.spi.CacheKey not properly serialized by binary marshaller

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov updated IGNITE-3429:
-
Priority: Major  (was: Critical)

> org.hibernate.cache.spi.CacheKey not properly serialized by binary marshaller
> -
>
> Key: IGNITE-3429
> URL: https://issues.apache.org/jira/browse/IGNITE-3429
> Project: Ignite
>  Issue Type: Bug
>  Components: cache, Hibernate L2 cache
>Affects Versions: 1.6
>Reporter: Valentin Kulichenko
>Assignee: Andrew Mashenkov
> Fix For: 1.9
>
>
> {{org.hibernate.cache.spi.CacheKey}} is a class used as a key for all entries 
> in the Hibernate L2 cache. This class contains {{type}} field and custom 
> {{equals}} logic where the type is used as a helper and does not participate 
> in comparison. Instances of the same type are producing different hash codes 
> in different JVMs, which actually breaks comparison when binary format is 
> used, where byte arrays are compared.
> The issue is described in more detail here: 
> http://stackoverflow.com/questions/38132263/apache-ignite-as-hibernate-l2-cache-storing-duplicate-entities



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

[jira] [Commented] (IGNITE-4106) SQL: parallelize sql queries over cache local partitions

[Andrew Mashenkov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-4106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15880386#comment-15880386
 ] 

Andrew Mashenkov commented on IGNITE-4106:
--

Segmented spatial index support added as well.

> SQL: parallelize sql queries over cache local partitions
> 
>
> Key: IGNITE-4106
> URL: https://issues.apache.org/jira/browse/IGNITE-4106
> Project: Ignite
>  Issue Type: Improvement
>  Components: SQL
>Affects Versions: 1.7
>Reporter: Andrew Mashenkov
>Assignee: Andrew Mashenkov
>  Labels: performance
> Fix For: 1.9
>
> Attachments: 1node-4thread.jfr, 4node-1thread.jfr
>
>
> If we run SQL query on cache partitioned over several cluster nodes, it will 
> be split into several queries running in parallel. But really we will have 
> one thread per query on each node.
> So, for now, to improve SQL query performance we need to run more Ignite 
> instances or split caches manually.
> It seems to be better to split local SQL queries over cache partitions, so we 
> would be able to parallelize SQL query on every single node and utilize CPU 
> more efficiently.



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

[jira] [Commented] (IGNITE-4539) RocketMQ data streamer

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-4539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15880210#comment-15880210
 ] 

ASF GitHub Bot commented on IGNITE-4539:


GitHub user shroman opened a pull request:

https://github.com/apache/ignite/pull/1571

IGNITE-4539: RocketMQ Streamer implementation.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/shroman/ignite IGNITE-4539

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/1571.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 #1571


commit b5c9318d41982a4d38e666d7d09f8cdaab648532
Author: shtykh_roman 
Date:   2017-01-26T07:01:38Z

IGNITE-4539: RocketMQ data streamer.

commit dc2eed604d6a90cd60930f058d90a8bf97017f7a
Author: shtykh_roman 
Date:   2017-02-21T10:10:24Z

Changed RocketMQ version to the latest release.

commit b8a69abb156312f79110e5a2504dfa1489b64579
Author: shtykh_roman 
Date:   2017-02-23T09:55:41Z

IGNITE-4539: reworked RocketMQ startup.

commit dadf826ceb207fa24910bcec54147f188c4104e1
Author: shtykh_roman 
Date:   2017-02-23T10:00:32Z

Merger with master.




> RocketMQ data streamer
> --
>
> Key: IGNITE-4539
> URL: https://issues.apache.org/jira/browse/IGNITE-4539
> Project: Ignite
>  Issue Type: New Feature
>  Components: streaming
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
> Fix For: 2.0
>
>
> Streamer for RocketMQ (https://github.com/rocketmq)



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

[jira] [Assigned] (IGNITE-933) GridFailFastNodeFailureDetectionSelfTest.testFailFast fails periodically

[Vadim Opolski (JIRA)]

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

Vadim Opolski reassigned IGNITE-933:


Assignee: Vadim Opolski  (was: Yakov Zhdanov)

> GridFailFastNodeFailureDetectionSelfTest.testFailFast fails periodically
> 
>
> Key: IGNITE-933
> URL: https://issues.apache.org/jira/browse/IGNITE-933
> Project: Ignite
>  Issue Type: Bug
>  Components: general, newbie
>Affects Versions: sprint-5
>Reporter: Denis Magda
>Assignee: Vadim Opolski
>  Labels: newbie
>
> The timeout for latch (500 millis) seems to be not enough for some machines. 
> Investigate and fix appropriately. 



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