[jira] [Commented] (IGNITE-8154) Add an ability to provide ExceptionListener to JmsStreamer
[
https://issues.apache.org/jira/browse/IGNITE-8154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16446928#comment-16446928
]
ASF GitHub Bot commented on IGNITE-8154:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3828
> Add an ability to provide ExceptionListener to JmsStreamer
> --
>
> Key: IGNITE-8154
> URL: https://issues.apache.org/jira/browse/IGNITE-8154
> Project: Ignite
> Issue Type: Improvement
> Components: streaming
>Affects Versions: 2.4
>Reporter: Valentin Kulichenko
>Assignee: Anton Kurbanov
>Priority: Major
> Fix For: 2.6
>
>
> JMS API allows to provide custom {{ExceptionListener}} that is invoked when
> an exception occurs within JMS queue/topic. Currently, {{JmsStreamer}}
> doesn't use this in any way which creates two issues:
> * If there is an exception, it's lost and not even logged.
> * User can't provide their own listener.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8154) Add an ability to provide ExceptionListener to JmsStreamer
[
https://issues.apache.org/jira/browse/IGNITE-8154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16446927#comment-16446927
]
Valentin Kulichenko commented on IGNITE-8154:
-
[~antkr], merged to master. Thanks for the contribution!
> Add an ability to provide ExceptionListener to JmsStreamer
> --
>
> Key: IGNITE-8154
> URL: https://issues.apache.org/jira/browse/IGNITE-8154
> Project: Ignite
> Issue Type: Improvement
> Components: streaming
>Affects Versions: 2.4
>Reporter: Valentin Kulichenko
>Assignee: Anton Kurbanov
>Priority: Major
> Fix For: 2.6
>
>
> JMS API allows to provide custom {{ExceptionListener}} that is invoked when
> an exception occurs within JMS queue/topic. Currently, {{JmsStreamer}}
> doesn't use this in any way which creates two issues:
> * If there is an exception, it's lost and not even logged.
> * User can't provide their own listener.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (IGNITE-8154) Add an ability to provide ExceptionListener to JmsStreamer
[
https://issues.apache.org/jira/browse/IGNITE-8154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko closed IGNITE-8154.
---
> Add an ability to provide ExceptionListener to JmsStreamer
> --
>
> Key: IGNITE-8154
> URL: https://issues.apache.org/jira/browse/IGNITE-8154
> Project: Ignite
> Issue Type: Improvement
> Components: streaming
>Affects Versions: 2.4
>Reporter: Valentin Kulichenko
>Assignee: Anton Kurbanov
>Priority: Major
> Fix For: 2.6
>
>
> JMS API allows to provide custom {{ExceptionListener}} that is invoked when
> an exception occurs within JMS queue/topic. Currently, {{JmsStreamer}}
> doesn't use this in any way which creates two issues:
> * If there is an exception, it's lost and not even logged.
> * User can't provide their own listener.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8266) Remove afterTestsStopped method due to stopAllGrids by default
[
https://issues.apache.org/jira/browse/IGNITE-8266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16446825#comment-16446825
]
Maxim Muzafarov commented on IGNITE-8266:
-
[~NIzhikov],
Changes ready for review. Can you look at them?
In this PR we are removing all boilerplate code related to stopAllGrids by
default.
TC looks good:
[#1337 (20 Apr 18
17:43)|https://ci.ignite.apache.org/viewLog.html?buildId=1230464] – javadoc
broken, but not through my changes
[#1346 (21 Apr 18
04:20)|https://ci.ignite.apache.org/viewLog.html?buildId=1232781] – next build
javadoc is OK
> Remove afterTestsStopped method due to stopAllGrids by default
> --
>
> Key: IGNITE-8266
> URL: https://issues.apache.org/jira/browse/IGNITE-8266
> Project: Ignite
> Issue Type: Sub-task
>Affects Versions: 2.5
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Minor
> Labels: test
> Fix For: 2.6
>
>
> Remove this types of method from test in whole ignite-core module.
> {code:java}
> @Override protected void afterTestsStopped() throws Exception {
> super.afterTestsStopped();
> stopAllGrids();
> }{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-8350) GA Grid: Prepare documentation for 2.5
Turik Campbell created IGNITE-8350: -- Summary: GA Grid: Prepare documentation for 2.5 Key: IGNITE-8350 URL: https://issues.apache.org/jira/browse/IGNITE-8350 Project: Ignite Issue Type: New Feature Components: documentation Reporter: Turik Campbell Assignee: Turik Campbell Fix For: 2.5 Review documentation and prepare for 2.5. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7077) Spark Data Frame Support. Strategy to convert complete query to Ignite SQL
[ https://issues.apache.org/jira/browse/IGNITE-7077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16446680#comment-16446680 ] Nikolay Izhikov commented on IGNITE-7077: - [~vkulichenko] > Nikolay, can you please do this? Sure. I didn't do that earlier. Is there any instruction how to merge commits into release branch? > Spark Data Frame Support. Strategy to convert complete query to Ignite SQL > -- > > Key: IGNITE-7077 > URL: https://issues.apache.org/jira/browse/IGNITE-7077 > Project: Ignite > Issue Type: New Feature > Components: spark >Affects Versions: 2.3 >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Labels: bigdata > Fix For: 2.5 > > > Basic support of Spark Data Frame for Ignite implemented in IGNITE-3084. > We need to implement custom spark strategy that can convert whole Spark SQL > query to Ignite SQL Query if query consists of only Ignite tables. > The strategy does nothing if spark query includes not only Ignite tables. > Memsql implementation can be taken as an example - > https://github.com/memsql/memsql-spark-connector -- This message was sent by Atlassian JIRA (v7.6.3#76005)
