[jira] [Closed] (IGNITE-12951) Update documents for migrated extensions
[
https://issues.apache.org/jira/browse/IGNITE-12951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Saikat Maitra closed IGNITE-12951.
--
> Update documents for migrated extensions
>
>
> Key: IGNITE-12951
> URL: https://issues.apache.org/jira/browse/IGNITE-12951
> Project: Ignite
> Issue Type: Sub-task
> Components: streaming
>Reporter: Saikat Maitra
>Assignee: Saikat Maitra
>Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> # Update README for migrated extensions.The newly migrated extensions modules
> have suffix -ext in the artifact name.Review and update extensions README
> docs to correct artifact name. An example for correct artifact name would be
> ignite-flink-ext
> # We need to update some sections (maven artifacts name, a paragraph about
> the extensions repository) in existing docs before the extension is released:
> https://github.com/apache/ignite/tree/master/docs/_docs/extensions-and-integrations
> #
> {quote}{{As for the extensions web page, I see its structure as follows. It
> goeswith a header introducing the extensions repository and covering types
> ofcontributions that are welcomed there. Then down below in the body we
> listall the available extensions - it can be a simple table with an
> extensionname, description, URL or a bit more advanced interface with a grid
> layoutlike on this page [1]. With the grid layout, we can add logos of
> theprojects Ignite is integrated with in addition to the
> name/description/URL.Let me know what you think.[1]
> [https://ignite.apache.org/screencasts.html]}}{quote}
>
> {{[http://apache-ignite-developers.2346864.n4.nabble.com/IGNITE-12358-Migrate-ZeroMQ-module-to-ignite-extensions-td45067.html#a46863]}}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12952) Enable travis ci for ignite-extensions
[ https://issues.apache.org/jira/browse/IGNITE-12952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saikat Maitra updated IGNITE-12952: --- Labels: BLOCKED (was: ) > Enable travis ci for ignite-extensions > -- > > Key: IGNITE-12952 > URL: https://issues.apache.org/jira/browse/IGNITE-12952 > Project: Ignite > Issue Type: Sub-task > Components: streaming >Reporter: Saikat Maitra >Priority: Minor > Labels: BLOCKED > > Enable travis ci for ignite-extensions. > We have recently enabled travis ci in ignite repo and checking for build > results for PR and merge to master process. > This subtask is to enable travis ci in ignite-extensions repo. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-13648) Tests failing for extensions modules
[
https://issues.apache.org/jira/browse/IGNITE-13648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Saikat Maitra closed IGNITE-13648.
--
> Tests failing for extensions modules
>
>
> Key: IGNITE-13648
> URL: https://issues.apache.org/jira/browse/IGNITE-13648
> Project: Ignite
> Issue Type: Sub-task
> Components: streaming
>Reporter: Saikat Maitra
>Assignee: Saikat Maitra
>Priority: Major
>
> Tests failing for extensions modules
>
> {code}
> org.apache.ignite.IgniteException: Failed to start manager:
> GridManagerAdapter [enabled=true,
> name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
> at
> org.apache.ignite.stream.kafka.connect.IgniteSinkConnectorTest.beforeTestsStarted(IgniteSinkConnectorTest.java:136)
> Caused by: org.apache.ignite.IgniteCheckedException: Failed to start manager:
> GridManagerAdapter [enabled=true,
> name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
> at
> org.apache.ignite.stream.kafka.connect.IgniteSinkConnectorTest.beforeTestsStarted(IgniteSinkConnectorTest.java:136)
> Caused by: org.apache.ignite.IgniteCheckedException: Remote node has peer
> class loading enabled flag different from local [locId8=dfc9ddaf,
> locPeerClassLoading=true, rmtId8=fee013c8, rmtPeerClassLoading=false,
> rmtAddrs=[9dc3d9f4b167/127.0.0.1, /172.17.0.6], rmtNode=ClusterNode
> [id=fee013c8-d398-4cdc-92f5-c368c5fc663a, order=1, addr=[127.0.0.1,
> 172.17.0.6], daemon=false]]
> at
> org.apache.ignite.stream.kafka.connect.IgniteSinkConnectorTest.beforeTestsStarted(IgniteSinkConnectorTest.java:136)
> {code}
>
>
> {code}
> org.apache.ignite.IgniteException: Failed to start manager:
> GridManagerAdapter [enabled=true,
> name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
> at
> org.apache.ignite.stream.kafka.connect.IgniteSourceConnectorTest.beforeTestsStarted(IgniteSourceConnectorTest.java:96)
> Caused by: org.apache.ignite.IgniteCheckedException: Failed to start manager:
> GridManagerAdapter [enabled=true,
> name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
> at
> org.apache.ignite.stream.kafka.connect.IgniteSourceConnectorTest.beforeTestsStarted(IgniteSourceConnectorTest.java:96)
> Caused by: org.apache.ignite.IgniteCheckedException: Remote node has peer
> class loading enabled flag different from local [locId8=bbb64dda,
> locPeerClassLoading=true, rmtId8=fee013c8, rmtPeerClassLoading=false,
> rmtAddrs=[9dc3d9f4b167/127.0.0.1, /172.17.0.6], rmtNode=ClusterNode
> [id=fee013c8-d398-4cdc-92f5-c368c5fc663a, order=1, addr=[127.0.0.1,
> 172.17.0.6], daemon=false]]
> at
> org.apache.ignite.stream.kafka.connect.IgniteSourceConnectorTest.beforeTestsStarted(IgniteSourceConnectorTest.java:96)
> {code}
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13648) Tests failing for extensions modules
[
https://issues.apache.org/jira/browse/IGNITE-13648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17262299#comment-17262299
]
Saikat Maitra commented on IGNITE-13648:
[~slava.koptilin]
Thank you for reviewing the changes. Much appreciate it.
Regards,
Saikat
> Tests failing for extensions modules
>
>
> Key: IGNITE-13648
> URL: https://issues.apache.org/jira/browse/IGNITE-13648
> Project: Ignite
> Issue Type: Sub-task
> Components: streaming
>Reporter: Saikat Maitra
>Assignee: Saikat Maitra
>Priority: Major
>
> Tests failing for extensions modules
>
> {code}
> org.apache.ignite.IgniteException: Failed to start manager:
> GridManagerAdapter [enabled=true,
> name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
> at
> org.apache.ignite.stream.kafka.connect.IgniteSinkConnectorTest.beforeTestsStarted(IgniteSinkConnectorTest.java:136)
> Caused by: org.apache.ignite.IgniteCheckedException: Failed to start manager:
> GridManagerAdapter [enabled=true,
> name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
> at
> org.apache.ignite.stream.kafka.connect.IgniteSinkConnectorTest.beforeTestsStarted(IgniteSinkConnectorTest.java:136)
> Caused by: org.apache.ignite.IgniteCheckedException: Remote node has peer
> class loading enabled flag different from local [locId8=dfc9ddaf,
> locPeerClassLoading=true, rmtId8=fee013c8, rmtPeerClassLoading=false,
> rmtAddrs=[9dc3d9f4b167/127.0.0.1, /172.17.0.6], rmtNode=ClusterNode
> [id=fee013c8-d398-4cdc-92f5-c368c5fc663a, order=1, addr=[127.0.0.1,
> 172.17.0.6], daemon=false]]
> at
> org.apache.ignite.stream.kafka.connect.IgniteSinkConnectorTest.beforeTestsStarted(IgniteSinkConnectorTest.java:136)
> {code}
>
>
> {code}
> org.apache.ignite.IgniteException: Failed to start manager:
> GridManagerAdapter [enabled=true,
> name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
> at
> org.apache.ignite.stream.kafka.connect.IgniteSourceConnectorTest.beforeTestsStarted(IgniteSourceConnectorTest.java:96)
> Caused by: org.apache.ignite.IgniteCheckedException: Failed to start manager:
> GridManagerAdapter [enabled=true,
> name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
> at
> org.apache.ignite.stream.kafka.connect.IgniteSourceConnectorTest.beforeTestsStarted(IgniteSourceConnectorTest.java:96)
> Caused by: org.apache.ignite.IgniteCheckedException: Remote node has peer
> class loading enabled flag different from local [locId8=bbb64dda,
> locPeerClassLoading=true, rmtId8=fee013c8, rmtPeerClassLoading=false,
> rmtAddrs=[9dc3d9f4b167/127.0.0.1, /172.17.0.6], rmtNode=ClusterNode
> [id=fee013c8-d398-4cdc-92f5-c368c5fc663a, order=1, addr=[127.0.0.1,
> 172.17.0.6], daemon=false]]
> at
> org.apache.ignite.stream.kafka.connect.IgniteSourceConnectorTest.beforeTestsStarted(IgniteSourceConnectorTest.java:96)
> {code}
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (IGNITE-13539) Remove references for migrated Ignite Extensions modules from the assembly and osgi-karaf
[ https://issues.apache.org/jira/browse/IGNITE-13539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saikat Maitra closed IGNITE-13539. -- > Remove references for migrated Ignite Extensions modules from the assembly > and osgi-karaf > -- > > Key: IGNITE-13539 > URL: https://issues.apache.org/jira/browse/IGNITE-13539 > Project: Ignite > Issue Type: Sub-task >Reporter: Saikat Maitra >Assignee: Saikat Maitra >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > Remove references for migrated Ignite Extensions modules from the > assembly/dependencies-apache-ignite-slim.xml and assembly/lib/Readme.txt > > Also, for migrated Ignite Extensions modules the > modules/osgi-karaf/src/main/resources/features.xml should refer to ignite-ext > now. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12951) Update documents for migrated extensions
[
https://issues.apache.org/jira/browse/IGNITE-12951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17239413#comment-17239413
]
Saikat Maitra commented on IGNITE-12951:
[~dmagda]
Thank you for the review, I have merged the changes and applied the cherry-pick
commit to ignite-2.9-docs branch.
Regards,
Saikat
> Update documents for migrated extensions
>
>
> Key: IGNITE-12951
> URL: https://issues.apache.org/jira/browse/IGNITE-12951
> Project: Ignite
> Issue Type: Sub-task
> Components: streaming
>Reporter: Saikat Maitra
>Assignee: Saikat Maitra
>Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> # Update README for migrated extensions.The newly migrated extensions modules
> have suffix -ext in the artifact name.Review and update extensions README
> docs to correct artifact name. An example for correct artifact name would be
> ignite-flink-ext
> # We need to update some sections (maven artifacts name, a paragraph about
> the extensions repository) in existing docs before the extension is released:
> https://github.com/apache/ignite/tree/master/docs/_docs/extensions-and-integrations
> #
> {quote}{{As for the extensions web page, I see its structure as follows. It
> goeswith a header introducing the extensions repository and covering types
> ofcontributions that are welcomed there. Then down below in the body we
> listall the available extensions - it can be a simple table with an
> extensionname, description, URL or a bit more advanced interface with a grid
> layoutlike on this page [1]. With the grid layout, we can add logos of
> theprojects Ignite is integrated with in addition to the
> name/description/URL.Let me know what you think.[1]
> [https://ignite.apache.org/screencasts.html]}}{quote}
>
> {{[http://apache-ignite-developers.2346864.n4.nabble.com/IGNITE-12358-Migrate-ZeroMQ-module-to-ignite-extensions-td45067.html#a46863]}}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-13539) Remove references for migrated Ignite Extensions modules from the assembly and osgi-karaf
[ https://issues.apache.org/jira/browse/IGNITE-13539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saikat Maitra reassigned IGNITE-13539: -- Assignee: Saikat Maitra > Remove references for migrated Ignite Extensions modules from the assembly > and osgi-karaf > -- > > Key: IGNITE-13539 > URL: https://issues.apache.org/jira/browse/IGNITE-13539 > Project: Ignite > Issue Type: Sub-task >Reporter: Saikat Maitra >Assignee: Saikat Maitra >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Remove references for migrated Ignite Extensions modules from the > assembly/dependencies-apache-ignite-slim.xml and assembly/lib/Readme.txt > > Also, for migrated Ignite Extensions modules the > modules/osgi-karaf/src/main/resources/features.xml should refer to ignite-ext > now. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-12951) Update documents for migrated extensions
[jira] [Reopened] (IGNITE-13648) Tests failing for extensions modules
[
https://issues.apache.org/jira/browse/IGNITE-13648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Saikat Maitra reopened IGNITE-13648:
> Tests failing for extensions modules
>
>
> Key: IGNITE-13648
> URL: https://issues.apache.org/jira/browse/IGNITE-13648
> Project: Ignite
> Issue Type: Sub-task
> Components: streaming
>Reporter: Saikat Maitra
>Assignee: Saikat Maitra
>Priority: Major
>
> Tests failing for extensions modules
>
> {code}
> org.apache.ignite.IgniteException: Failed to start manager:
> GridManagerAdapter [enabled=true,
> name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
> at
> org.apache.ignite.stream.kafka.connect.IgniteSinkConnectorTest.beforeTestsStarted(IgniteSinkConnectorTest.java:136)
> Caused by: org.apache.ignite.IgniteCheckedException: Failed to start manager:
> GridManagerAdapter [enabled=true,
> name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
> at
> org.apache.ignite.stream.kafka.connect.IgniteSinkConnectorTest.beforeTestsStarted(IgniteSinkConnectorTest.java:136)
> Caused by: org.apache.ignite.IgniteCheckedException: Remote node has peer
> class loading enabled flag different from local [locId8=dfc9ddaf,
> locPeerClassLoading=true, rmtId8=fee013c8, rmtPeerClassLoading=false,
> rmtAddrs=[9dc3d9f4b167/127.0.0.1, /172.17.0.6], rmtNode=ClusterNode
> [id=fee013c8-d398-4cdc-92f5-c368c5fc663a, order=1, addr=[127.0.0.1,
> 172.17.0.6], daemon=false]]
> at
> org.apache.ignite.stream.kafka.connect.IgniteSinkConnectorTest.beforeTestsStarted(IgniteSinkConnectorTest.java:136)
> {code}
>
>
> {code}
> org.apache.ignite.IgniteException: Failed to start manager:
> GridManagerAdapter [enabled=true,
> name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
> at
> org.apache.ignite.stream.kafka.connect.IgniteSourceConnectorTest.beforeTestsStarted(IgniteSourceConnectorTest.java:96)
> Caused by: org.apache.ignite.IgniteCheckedException: Failed to start manager:
> GridManagerAdapter [enabled=true,
> name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
> at
> org.apache.ignite.stream.kafka.connect.IgniteSourceConnectorTest.beforeTestsStarted(IgniteSourceConnectorTest.java:96)
> Caused by: org.apache.ignite.IgniteCheckedException: Remote node has peer
> class loading enabled flag different from local [locId8=bbb64dda,
> locPeerClassLoading=true, rmtId8=fee013c8, rmtPeerClassLoading=false,
> rmtAddrs=[9dc3d9f4b167/127.0.0.1, /172.17.0.6], rmtNode=ClusterNode
> [id=fee013c8-d398-4cdc-92f5-c368c5fc663a, order=1, addr=[127.0.0.1,
> 172.17.0.6], daemon=false]]
> at
> org.apache.ignite.stream.kafka.connect.IgniteSourceConnectorTest.beforeTestsStarted(IgniteSourceConnectorTest.java:96)
> {code}
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13648) Tests failing for extensions modules
[
https://issues.apache.org/jira/browse/IGNITE-13648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17227887#comment-17227887
]
Saikat Maitra commented on IGNITE-13648:
In teamcity the issue is reproducible. Raised a PR to fix the issue.
> Tests failing for extensions modules
>
>
> Key: IGNITE-13648
> URL: https://issues.apache.org/jira/browse/IGNITE-13648
> Project: Ignite
> Issue Type: Sub-task
> Components: streaming
>Reporter: Saikat Maitra
>Assignee: Saikat Maitra
>Priority: Major
>
> Tests failing for extensions modules
>
> {code}
> org.apache.ignite.IgniteException: Failed to start manager:
> GridManagerAdapter [enabled=true,
> name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
> at
> org.apache.ignite.stream.kafka.connect.IgniteSinkConnectorTest.beforeTestsStarted(IgniteSinkConnectorTest.java:136)
> Caused by: org.apache.ignite.IgniteCheckedException: Failed to start manager:
> GridManagerAdapter [enabled=true,
> name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
> at
> org.apache.ignite.stream.kafka.connect.IgniteSinkConnectorTest.beforeTestsStarted(IgniteSinkConnectorTest.java:136)
> Caused by: org.apache.ignite.IgniteCheckedException: Remote node has peer
> class loading enabled flag different from local [locId8=dfc9ddaf,
> locPeerClassLoading=true, rmtId8=fee013c8, rmtPeerClassLoading=false,
> rmtAddrs=[9dc3d9f4b167/127.0.0.1, /172.17.0.6], rmtNode=ClusterNode
> [id=fee013c8-d398-4cdc-92f5-c368c5fc663a, order=1, addr=[127.0.0.1,
> 172.17.0.6], daemon=false]]
> at
> org.apache.ignite.stream.kafka.connect.IgniteSinkConnectorTest.beforeTestsStarted(IgniteSinkConnectorTest.java:136)
> {code}
>
>
> {code}
> org.apache.ignite.IgniteException: Failed to start manager:
> GridManagerAdapter [enabled=true,
> name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
> at
> org.apache.ignite.stream.kafka.connect.IgniteSourceConnectorTest.beforeTestsStarted(IgniteSourceConnectorTest.java:96)
> Caused by: org.apache.ignite.IgniteCheckedException: Failed to start manager:
> GridManagerAdapter [enabled=true,
> name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
> at
> org.apache.ignite.stream.kafka.connect.IgniteSourceConnectorTest.beforeTestsStarted(IgniteSourceConnectorTest.java:96)
> Caused by: org.apache.ignite.IgniteCheckedException: Remote node has peer
> class loading enabled flag different from local [locId8=bbb64dda,
> locPeerClassLoading=true, rmtId8=fee013c8, rmtPeerClassLoading=false,
> rmtAddrs=[9dc3d9f4b167/127.0.0.1, /172.17.0.6], rmtNode=ClusterNode
> [id=fee013c8-d398-4cdc-92f5-c368c5fc663a, order=1, addr=[127.0.0.1,
> 172.17.0.6], daemon=false]]
> at
> org.apache.ignite.stream.kafka.connect.IgniteSourceConnectorTest.beforeTestsStarted(IgniteSourceConnectorTest.java:96)
> {code}
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (IGNITE-13407) Upgrade ignite.version to 2.10.0-SNAPSHOT in Ignite Extensions
[ https://issues.apache.org/jira/browse/IGNITE-13407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saikat Maitra closed IGNITE-13407. -- > Upgrade ignite.version to 2.10.0-SNAPSHOT in Ignite Extensions > -- > > Key: IGNITE-13407 > URL: https://issues.apache.org/jira/browse/IGNITE-13407 > Project: Ignite > Issue Type: Sub-task > Components: streaming >Reporter: Saikat Maitra >Assignee: Saikat Maitra >Priority: Major > > Upgrade ignite.version to 2.10.0-SNAPSHOT in Ignite Extensions -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-13407) Upgrade ignite.version to 2.10.0-SNAPSHOT in Ignite Extensions
[ https://issues.apache.org/jira/browse/IGNITE-13407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saikat Maitra resolved IGNITE-13407. Resolution: Done > Upgrade ignite.version to 2.10.0-SNAPSHOT in Ignite Extensions > -- > > Key: IGNITE-13407 > URL: https://issues.apache.org/jira/browse/IGNITE-13407 > Project: Ignite > Issue Type: Sub-task > Components: streaming >Reporter: Saikat Maitra >Assignee: Saikat Maitra >Priority: Major > > Upgrade ignite.version to 2.10.0-SNAPSHOT in Ignite Extensions -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-13648) Tests failing for extensions modules
[
https://issues.apache.org/jira/browse/IGNITE-13648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Saikat Maitra resolved IGNITE-13648.
Resolution: Cannot Reproduce
> Tests failing for extensions modules
>
>
> Key: IGNITE-13648
> URL: https://issues.apache.org/jira/browse/IGNITE-13648
> Project: Ignite
> Issue Type: Sub-task
> Components: streaming
>Reporter: Saikat Maitra
>Assignee: Saikat Maitra
>Priority: Major
>
> Tests failing for extensions modules
>
> {code}
> org.apache.ignite.IgniteException: Failed to start manager:
> GridManagerAdapter [enabled=true,
> name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
> at
> org.apache.ignite.stream.kafka.connect.IgniteSinkConnectorTest.beforeTestsStarted(IgniteSinkConnectorTest.java:136)
> Caused by: org.apache.ignite.IgniteCheckedException: Failed to start manager:
> GridManagerAdapter [enabled=true,
> name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
> at
> org.apache.ignite.stream.kafka.connect.IgniteSinkConnectorTest.beforeTestsStarted(IgniteSinkConnectorTest.java:136)
> Caused by: org.apache.ignite.IgniteCheckedException: Remote node has peer
> class loading enabled flag different from local [locId8=dfc9ddaf,
> locPeerClassLoading=true, rmtId8=fee013c8, rmtPeerClassLoading=false,
> rmtAddrs=[9dc3d9f4b167/127.0.0.1, /172.17.0.6], rmtNode=ClusterNode
> [id=fee013c8-d398-4cdc-92f5-c368c5fc663a, order=1, addr=[127.0.0.1,
> 172.17.0.6], daemon=false]]
> at
> org.apache.ignite.stream.kafka.connect.IgniteSinkConnectorTest.beforeTestsStarted(IgniteSinkConnectorTest.java:136)
> {code}
>
>
> {code}
> org.apache.ignite.IgniteException: Failed to start manager:
> GridManagerAdapter [enabled=true,
> name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
> at
> org.apache.ignite.stream.kafka.connect.IgniteSourceConnectorTest.beforeTestsStarted(IgniteSourceConnectorTest.java:96)
> Caused by: org.apache.ignite.IgniteCheckedException: Failed to start manager:
> GridManagerAdapter [enabled=true,
> name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
> at
> org.apache.ignite.stream.kafka.connect.IgniteSourceConnectorTest.beforeTestsStarted(IgniteSourceConnectorTest.java:96)
> Caused by: org.apache.ignite.IgniteCheckedException: Remote node has peer
> class loading enabled flag different from local [locId8=bbb64dda,
> locPeerClassLoading=true, rmtId8=fee013c8, rmtPeerClassLoading=false,
> rmtAddrs=[9dc3d9f4b167/127.0.0.1, /172.17.0.6], rmtNode=ClusterNode
> [id=fee013c8-d398-4cdc-92f5-c368c5fc663a, order=1, addr=[127.0.0.1,
> 172.17.0.6], daemon=false]]
> at
> org.apache.ignite.stream.kafka.connect.IgniteSourceConnectorTest.beforeTestsStarted(IgniteSourceConnectorTest.java:96)
> {code}
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13648) Tests failing for extensions modules
[
https://issues.apache.org/jira/browse/IGNITE-13648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17224393#comment-17224393
]
Saikat Maitra commented on IGNITE-13648:
Unable to reproduce the errors in local.
> Tests failing for extensions modules
>
>
> Key: IGNITE-13648
> URL: https://issues.apache.org/jira/browse/IGNITE-13648
> Project: Ignite
> Issue Type: Sub-task
> Components: streaming
>Reporter: Saikat Maitra
>Assignee: Saikat Maitra
>Priority: Major
>
> Tests failing for extensions modules
>
> {code}
> org.apache.ignite.IgniteException: Failed to start manager:
> GridManagerAdapter [enabled=true,
> name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
> at
> org.apache.ignite.stream.kafka.connect.IgniteSinkConnectorTest.beforeTestsStarted(IgniteSinkConnectorTest.java:136)
> Caused by: org.apache.ignite.IgniteCheckedException: Failed to start manager:
> GridManagerAdapter [enabled=true,
> name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
> at
> org.apache.ignite.stream.kafka.connect.IgniteSinkConnectorTest.beforeTestsStarted(IgniteSinkConnectorTest.java:136)
> Caused by: org.apache.ignite.IgniteCheckedException: Remote node has peer
> class loading enabled flag different from local [locId8=dfc9ddaf,
> locPeerClassLoading=true, rmtId8=fee013c8, rmtPeerClassLoading=false,
> rmtAddrs=[9dc3d9f4b167/127.0.0.1, /172.17.0.6], rmtNode=ClusterNode
> [id=fee013c8-d398-4cdc-92f5-c368c5fc663a, order=1, addr=[127.0.0.1,
> 172.17.0.6], daemon=false]]
> at
> org.apache.ignite.stream.kafka.connect.IgniteSinkConnectorTest.beforeTestsStarted(IgniteSinkConnectorTest.java:136)
> {code}
>
>
> {code}
> org.apache.ignite.IgniteException: Failed to start manager:
> GridManagerAdapter [enabled=true,
> name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
> at
> org.apache.ignite.stream.kafka.connect.IgniteSourceConnectorTest.beforeTestsStarted(IgniteSourceConnectorTest.java:96)
> Caused by: org.apache.ignite.IgniteCheckedException: Failed to start manager:
> GridManagerAdapter [enabled=true,
> name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
> at
> org.apache.ignite.stream.kafka.connect.IgniteSourceConnectorTest.beforeTestsStarted(IgniteSourceConnectorTest.java:96)
> Caused by: org.apache.ignite.IgniteCheckedException: Remote node has peer
> class loading enabled flag different from local [locId8=bbb64dda,
> locPeerClassLoading=true, rmtId8=fee013c8, rmtPeerClassLoading=false,
> rmtAddrs=[9dc3d9f4b167/127.0.0.1, /172.17.0.6], rmtNode=ClusterNode
> [id=fee013c8-d398-4cdc-92f5-c368c5fc663a, order=1, addr=[127.0.0.1,
> 172.17.0.6], daemon=false]]
> at
> org.apache.ignite.stream.kafka.connect.IgniteSourceConnectorTest.beforeTestsStarted(IgniteSourceConnectorTest.java:96)
> {code}
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (IGNITE-13648) Tests failing for extensions modules
[
https://issues.apache.org/jira/browse/IGNITE-13648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Saikat Maitra closed IGNITE-13648.
--
> Tests failing for extensions modules
>
>
> Key: IGNITE-13648
> URL: https://issues.apache.org/jira/browse/IGNITE-13648
> Project: Ignite
> Issue Type: Sub-task
> Components: streaming
>Reporter: Saikat Maitra
>Assignee: Saikat Maitra
>Priority: Major
>
> Tests failing for extensions modules
>
> {code}
> org.apache.ignite.IgniteException: Failed to start manager:
> GridManagerAdapter [enabled=true,
> name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
> at
> org.apache.ignite.stream.kafka.connect.IgniteSinkConnectorTest.beforeTestsStarted(IgniteSinkConnectorTest.java:136)
> Caused by: org.apache.ignite.IgniteCheckedException: Failed to start manager:
> GridManagerAdapter [enabled=true,
> name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
> at
> org.apache.ignite.stream.kafka.connect.IgniteSinkConnectorTest.beforeTestsStarted(IgniteSinkConnectorTest.java:136)
> Caused by: org.apache.ignite.IgniteCheckedException: Remote node has peer
> class loading enabled flag different from local [locId8=dfc9ddaf,
> locPeerClassLoading=true, rmtId8=fee013c8, rmtPeerClassLoading=false,
> rmtAddrs=[9dc3d9f4b167/127.0.0.1, /172.17.0.6], rmtNode=ClusterNode
> [id=fee013c8-d398-4cdc-92f5-c368c5fc663a, order=1, addr=[127.0.0.1,
> 172.17.0.6], daemon=false]]
> at
> org.apache.ignite.stream.kafka.connect.IgniteSinkConnectorTest.beforeTestsStarted(IgniteSinkConnectorTest.java:136)
> {code}
>
>
> {code}
> org.apache.ignite.IgniteException: Failed to start manager:
> GridManagerAdapter [enabled=true,
> name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
> at
> org.apache.ignite.stream.kafka.connect.IgniteSourceConnectorTest.beforeTestsStarted(IgniteSourceConnectorTest.java:96)
> Caused by: org.apache.ignite.IgniteCheckedException: Failed to start manager:
> GridManagerAdapter [enabled=true,
> name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
> at
> org.apache.ignite.stream.kafka.connect.IgniteSourceConnectorTest.beforeTestsStarted(IgniteSourceConnectorTest.java:96)
> Caused by: org.apache.ignite.IgniteCheckedException: Remote node has peer
> class loading enabled flag different from local [locId8=bbb64dda,
> locPeerClassLoading=true, rmtId8=fee013c8, rmtPeerClassLoading=false,
> rmtAddrs=[9dc3d9f4b167/127.0.0.1, /172.17.0.6], rmtNode=ClusterNode
> [id=fee013c8-d398-4cdc-92f5-c368c5fc663a, order=1, addr=[127.0.0.1,
> 172.17.0.6], daemon=false]]
> at
> org.apache.ignite.stream.kafka.connect.IgniteSourceConnectorTest.beforeTestsStarted(IgniteSourceConnectorTest.java:96)
> {code}
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-13648) Tests failing for extensions modules
Saikat Maitra created IGNITE-13648:
--
Summary: Tests failing for extensions modules
Key: IGNITE-13648
URL: https://issues.apache.org/jira/browse/IGNITE-13648
Project: Ignite
Issue Type: Sub-task
Components: streaming
Reporter: Saikat Maitra
Tests failing for extensions modules
{code}
org.apache.ignite.IgniteException: Failed to start manager: GridManagerAdapter
[enabled=true,
name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
at
org.apache.ignite.stream.kafka.connect.IgniteSinkConnectorTest.beforeTestsStarted(IgniteSinkConnectorTest.java:136)
Caused by: org.apache.ignite.IgniteCheckedException: Failed to start manager:
GridManagerAdapter [enabled=true,
name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
at
org.apache.ignite.stream.kafka.connect.IgniteSinkConnectorTest.beforeTestsStarted(IgniteSinkConnectorTest.java:136)
Caused by: org.apache.ignite.IgniteCheckedException: Remote node has peer class
loading enabled flag different from local [locId8=dfc9ddaf,
locPeerClassLoading=true, rmtId8=fee013c8, rmtPeerClassLoading=false,
rmtAddrs=[9dc3d9f4b167/127.0.0.1, /172.17.0.6], rmtNode=ClusterNode
[id=fee013c8-d398-4cdc-92f5-c368c5fc663a, order=1, addr=[127.0.0.1,
172.17.0.6], daemon=false]]
at
org.apache.ignite.stream.kafka.connect.IgniteSinkConnectorTest.beforeTestsStarted(IgniteSinkConnectorTest.java:136)
{code}
{code}
org.apache.ignite.IgniteException: Failed to start manager: GridManagerAdapter
[enabled=true,
name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
at
org.apache.ignite.stream.kafka.connect.IgniteSourceConnectorTest.beforeTestsStarted(IgniteSourceConnectorTest.java:96)
Caused by: org.apache.ignite.IgniteCheckedException: Failed to start manager:
GridManagerAdapter [enabled=true,
name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
at
org.apache.ignite.stream.kafka.connect.IgniteSourceConnectorTest.beforeTestsStarted(IgniteSourceConnectorTest.java:96)
Caused by: org.apache.ignite.IgniteCheckedException: Remote node has peer class
loading enabled flag different from local [locId8=bbb64dda,
locPeerClassLoading=true, rmtId8=fee013c8, rmtPeerClassLoading=false,
rmtAddrs=[9dc3d9f4b167/127.0.0.1, /172.17.0.6], rmtNode=ClusterNode
[id=fee013c8-d398-4cdc-92f5-c368c5fc663a, order=1, addr=[127.0.0.1,
172.17.0.6], daemon=false]]
at
org.apache.ignite.stream.kafka.connect.IgniteSourceConnectorTest.beforeTestsStarted(IgniteSourceConnectorTest.java:96)
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-13648) Tests failing for extensions modules
[
https://issues.apache.org/jira/browse/IGNITE-13648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Saikat Maitra reassigned IGNITE-13648:
--
Assignee: Saikat Maitra
> Tests failing for extensions modules
>
>
> Key: IGNITE-13648
> URL: https://issues.apache.org/jira/browse/IGNITE-13648
> Project: Ignite
> Issue Type: Sub-task
> Components: streaming
>Reporter: Saikat Maitra
>Assignee: Saikat Maitra
>Priority: Major
>
> Tests failing for extensions modules
>
> {code}
> org.apache.ignite.IgniteException: Failed to start manager:
> GridManagerAdapter [enabled=true,
> name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
> at
> org.apache.ignite.stream.kafka.connect.IgniteSinkConnectorTest.beforeTestsStarted(IgniteSinkConnectorTest.java:136)
> Caused by: org.apache.ignite.IgniteCheckedException: Failed to start manager:
> GridManagerAdapter [enabled=true,
> name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
> at
> org.apache.ignite.stream.kafka.connect.IgniteSinkConnectorTest.beforeTestsStarted(IgniteSinkConnectorTest.java:136)
> Caused by: org.apache.ignite.IgniteCheckedException: Remote node has peer
> class loading enabled flag different from local [locId8=dfc9ddaf,
> locPeerClassLoading=true, rmtId8=fee013c8, rmtPeerClassLoading=false,
> rmtAddrs=[9dc3d9f4b167/127.0.0.1, /172.17.0.6], rmtNode=ClusterNode
> [id=fee013c8-d398-4cdc-92f5-c368c5fc663a, order=1, addr=[127.0.0.1,
> 172.17.0.6], daemon=false]]
> at
> org.apache.ignite.stream.kafka.connect.IgniteSinkConnectorTest.beforeTestsStarted(IgniteSinkConnectorTest.java:136)
> {code}
>
>
> {code}
> org.apache.ignite.IgniteException: Failed to start manager:
> GridManagerAdapter [enabled=true,
> name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
> at
> org.apache.ignite.stream.kafka.connect.IgniteSourceConnectorTest.beforeTestsStarted(IgniteSourceConnectorTest.java:96)
> Caused by: org.apache.ignite.IgniteCheckedException: Failed to start manager:
> GridManagerAdapter [enabled=true,
> name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
> at
> org.apache.ignite.stream.kafka.connect.IgniteSourceConnectorTest.beforeTestsStarted(IgniteSourceConnectorTest.java:96)
> Caused by: org.apache.ignite.IgniteCheckedException: Remote node has peer
> class loading enabled flag different from local [locId8=bbb64dda,
> locPeerClassLoading=true, rmtId8=fee013c8, rmtPeerClassLoading=false,
> rmtAddrs=[9dc3d9f4b167/127.0.0.1, /172.17.0.6], rmtNode=ClusterNode
> [id=fee013c8-d398-4cdc-92f5-c368c5fc663a, order=1, addr=[127.0.0.1,
> 172.17.0.6], daemon=false]]
> at
> org.apache.ignite.stream.kafka.connect.IgniteSourceConnectorTest.beforeTestsStarted(IgniteSourceConnectorTest.java:96)
> {code}
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12951) Update documents for migrated extensions
[
https://issues.apache.org/jira/browse/IGNITE-12951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17223887#comment-17223887
]
Saikat Maitra commented on IGNITE-12951:
[~dmagda]
Thank you for updating the details in the Jira issue. I will update the
documents.
> Update documents for migrated extensions
>
>
> Key: IGNITE-12951
> URL: https://issues.apache.org/jira/browse/IGNITE-12951
> Project: Ignite
> Issue Type: Sub-task
> Components: streaming
>Reporter: Saikat Maitra
>Priority: Major
>
> # Update README for migrated extensions.The newly migrated extensions modules
> have suffix -ext in the artifact name.Review and update extensions README
> docs to correct artifact name. An example for correct artifact name would be
> ignite-flink-ext
> # We need to update some sections (maven artifacts name, a paragraph about
> the extensions repository) in existing docs before the extension is released:
> https://github.com/apache/ignite/tree/master/docs/_docs/extensions-and-integrations
> #
> {quote}{{As for the extensions web page, I see its structure as follows. It
> goeswith a header introducing the extensions repository and covering types
> ofcontributions that are welcomed there. Then down below in the body we
> listall the available extensions - it can be a simple table with an
> extensionname, description, URL or a bit more advanced interface with a grid
> layoutlike on this page [1]. With the grid layout, we can add logos of
> theprojects Ignite is integrated with in addition to the
> name/description/URL.Let me know what you think.[1]
> [https://ignite.apache.org/screencasts.html]}}{quote}
>
> {{[http://apache-ignite-developers.2346864.n4.nabble.com/IGNITE-12358-Migrate-ZeroMQ-module-to-ignite-extensions-td45067.html#a46863]}}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13621) Remove dependency of spring-data modules on Ignite version
[ https://issues.apache.org/jira/browse/IGNITE-13621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17223884#comment-17223884 ] Saikat Maitra commented on IGNITE-13621: Hi [~agoncharuk], I am good with the proposal of setting provided scope. I just wanted to connect and get feedback about our path forward. cc [~nizhikov] [~PetrovMikhail] > Remove dependency of spring-data modules on Ignite version > -- > > Key: IGNITE-13621 > URL: https://issues.apache.org/jira/browse/IGNITE-13621 > Project: Ignite > Issue Type: Sub-task >Reporter: Mikhail Petrov >Assignee: Mikhail Petrov >Priority: Minor > > It's needed to remove dependency of spring-data modules on Ignite version. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13621) Remove dependency of spring-data modules on Ignite version
[ https://issues.apache.org/jira/browse/IGNITE-13621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17221891#comment-17221891 ] Saikat Maitra commented on IGNITE-13621: Hi [~PetrovMikhail] My thoughts are if we specify the version of latest release ignite version then it make it easier for user to start using the spring-data modules right out of the box. I agree that it ties the extensions version to a specific release of Ignite but I have seen that unless there are changes in Ignite core apis the different version of Ignite continue to work. In other words Ignite 2.10 server will still work with spring-data-ext which has ignite 2.9 ignite-core unless there are major changes in core apis. I looked into build results and I see it is passing since ignite 2.10.0-SNAPSHOT is present in the classpath but if user do not have any ignite-core binaries then their implementation will fail. [https://ci.ignite.apache.org/buildConfiguration/Tests_IgniteExtensions_Build/5692527] Also please feel free to start a [DISCUSS] thread in dev/user mailing list and we can discuss and get feedback from other users and Ignite contributors. Regards, Saikat > Remove dependency of spring-data modules on Ignite version > -- > > Key: IGNITE-13621 > URL: https://issues.apache.org/jira/browse/IGNITE-13621 > Project: Ignite > Issue Type: Sub-task >Reporter: Mikhail Petrov >Assignee: Mikhail Petrov >Priority: Minor > > It's needed to remove dependency of spring-data modules on Ignite version. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13621) Remove dependency of spring-data modules on Ignite version
[ https://issues.apache.org/jira/browse/IGNITE-13621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17221035#comment-17221035 ] Saikat Maitra commented on IGNITE-13621: Hi [~PetrovMikhail], My understanding is we will always depend on latest snapshot of master from Ignite Nightly build in Apache Ignite Extensions project. Here is the discussion thread on the same [http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-dependencies-and-release-process-for-Ignite-Extensions-td44478.html] When we release specific extension like spring-data module then during release we will set latest release of Ignite version in the release branch for release. In this case it would be 2.9.0 version. > Remove dependency of spring-data modules on Ignite version > -- > > Key: IGNITE-13621 > URL: https://issues.apache.org/jira/browse/IGNITE-13621 > Project: Ignite > Issue Type: Sub-task >Reporter: Mikhail Petrov >Assignee: Mikhail Petrov >Priority: Minor > > It's needed to remove dependency of spring-data modules on Ignite version. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-13517) Disable travis build until Ignite nightly snapshots packages are published
[ https://issues.apache.org/jira/browse/IGNITE-13517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saikat Maitra closed IGNITE-13517. -- > Disable travis build until Ignite nightly snapshots packages are published > -- > > Key: IGNITE-13517 > URL: https://issues.apache.org/jira/browse/IGNITE-13517 > Project: Ignite > Issue Type: Sub-task >Reporter: Saikat Maitra >Assignee: Saikat Maitra >Priority: Minor > > Disable travis build until ignite nightly snapshots packages are published. > This is causing build failure for travis CI since travis is unable to pull > the required dependencies. > > We used to publish nightly packages earlier in the apache snapshot repository > but we are no longer publishing the packages. > > [https://repository.apache.org/content/repositories/snapshots/org/apache/ignite/ignite-core/] > > I have created following Jira story for the same > https://issues.apache.org/jira/browse/IGNITE-13412 > > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-12364) Migrate JMS module to ignite-extensions
[ https://issues.apache.org/jira/browse/IGNITE-12364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saikat Maitra closed IGNITE-12364. -- > Migrate JMS module to ignite-extensions > --- > > Key: IGNITE-12364 > URL: https://issues.apache.org/jira/browse/IGNITE-12364 > Project: Ignite > Issue Type: Sub-task > Components: streaming >Reporter: Saikat Maitra >Assignee: Saikat Maitra >Priority: Major > Time Spent: 40m > Remaining Estimate: 0h > > Migrate JMS module to ignite-extensions > [https://github.com/apache/ignite-extensions] > Details: > [https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization#IEP-36:Modularization-IndependentIntegrations] > Discussion : > [http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Proposal-for-Ignite-Extensions-as-a-separate-Bahir-module-or-Incubator-project-td44064.html#a44107] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12364) Migrate JMS module to ignite-extensions
[ https://issues.apache.org/jira/browse/IGNITE-12364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17211575#comment-17211575 ] Saikat Maitra commented on IGNITE-12364: I am tracking the changes for assembly files and osgi-karaf files in this Jira issue https://issues.apache.org/jira/browse/IGNITE-13539 > Migrate JMS module to ignite-extensions > --- > > Key: IGNITE-12364 > URL: https://issues.apache.org/jira/browse/IGNITE-12364 > Project: Ignite > Issue Type: Sub-task > Components: streaming >Reporter: Saikat Maitra >Assignee: Saikat Maitra >Priority: Major > Time Spent: 40m > Remaining Estimate: 0h > > Migrate JMS module to ignite-extensions > [https://github.com/apache/ignite-extensions] > Details: > [https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization#IEP-36:Modularization-IndependentIntegrations] > Discussion : > [http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Proposal-for-Ignite-Extensions-as-a-separate-Bahir-module-or-Incubator-project-td44064.html#a44107] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-13394) Migrate Kafka module to ignite-extensions
[ https://issues.apache.org/jira/browse/IGNITE-13394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saikat Maitra closed IGNITE-13394. -- > Migrate Kafka module to ignite-extensions > - > > Key: IGNITE-13394 > URL: https://issues.apache.org/jira/browse/IGNITE-13394 > Project: Ignite > Issue Type: Sub-task > Components: streaming >Reporter: Saikat Maitra >Assignee: Saikat Maitra >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > Migrate Kafka module to ignite-extensions > [https://github.com/apache/ignite-extensions] > Details: > [https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization#IEP-36:Modularization-IndependentIntegrations] > Discussion : > [http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Proposal-for-Ignite-Extensions-as-a-separate-Bahir-module-or-Incubator-project-td44064.html#a44107] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13394) Migrate Kafka module to ignite-extensions
[ https://issues.apache.org/jira/browse/IGNITE-13394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17209266#comment-17209266 ] Saikat Maitra commented on IGNITE-13394: [~ilyak] Here is the new issue I have created for the changes https://issues.apache.org/jira/browse/IGNITE-13539 > Migrate Kafka module to ignite-extensions > - > > Key: IGNITE-13394 > URL: https://issues.apache.org/jira/browse/IGNITE-13394 > Project: Ignite > Issue Type: Sub-task > Components: streaming >Reporter: Saikat Maitra >Assignee: Saikat Maitra >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > Migrate Kafka module to ignite-extensions > [https://github.com/apache/ignite-extensions] > Details: > [https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization#IEP-36:Modularization-IndependentIntegrations] > Discussion : > [http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Proposal-for-Ignite-Extensions-as-a-separate-Bahir-module-or-Incubator-project-td44064.html#a44107] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13539) Remove references for migrated Ignite Extensions modules from the assembly and osgi-karaf
Saikat Maitra created IGNITE-13539: -- Summary: Remove references for migrated Ignite Extensions modules from the assembly and osgi-karaf Key: IGNITE-13539 URL: https://issues.apache.org/jira/browse/IGNITE-13539 Project: Ignite Issue Type: Sub-task Reporter: Saikat Maitra Remove references for migrated Ignite Extensions modules from the assembly/dependencies-apache-ignite-slim.xml and assembly/lib/Readme.txt Also, for migrated Ignite Extensions modules the modules/osgi-karaf/src/main/resources/features.xml should refer to ignite-ext now. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13394) Migrate Kafka module to ignite-extensions
[ https://issues.apache.org/jira/browse/IGNITE-13394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17209263#comment-17209263 ] Saikat Maitra commented on IGNITE-13394: [~ilyak] Yes, I confirm I will create a separate issue and make the changes for assembly files for rest of the migrated modules. > Migrate Kafka module to ignite-extensions > - > > Key: IGNITE-13394 > URL: https://issues.apache.org/jira/browse/IGNITE-13394 > Project: Ignite > Issue Type: Sub-task > Components: streaming >Reporter: Saikat Maitra >Assignee: Saikat Maitra >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > Migrate Kafka module to ignite-extensions > [https://github.com/apache/ignite-extensions] > Details: > [https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization#IEP-36:Modularization-IndependentIntegrations] > Discussion : > [http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Proposal-for-Ignite-Extensions-as-a-separate-Bahir-module-or-Incubator-project-td44064.html#a44107] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13517) Disable travis build until Ignite nightly snapshots packages are published
[ https://issues.apache.org/jira/browse/IGNITE-13517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saikat Maitra updated IGNITE-13517: --- Summary: Disable travis build until Ignite nightly snapshots packages are published (was: Disable travis build until ignite nightly snapshots packages are published) > Disable travis build until Ignite nightly snapshots packages are published > -- > > Key: IGNITE-13517 > URL: https://issues.apache.org/jira/browse/IGNITE-13517 > Project: Ignite > Issue Type: Sub-task >Reporter: Saikat Maitra >Assignee: Saikat Maitra >Priority: Minor > > Disable travis build until ignite nightly snapshots packages are published. > This is causing build failure for travis CI since travis is unable to pull > the required dependencies. > > We used to publish nightly packages earlier in the apache snapshot repository > but we are no longer publishing the packages. > > [https://repository.apache.org/content/repositories/snapshots/org/apache/ignite/ignite-core/] > > I have created following Jira story for the same > https://issues.apache.org/jira/browse/IGNITE-13412 > > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-13517) Disable travis build until ignite nightly snapshots packages are published
[ https://issues.apache.org/jira/browse/IGNITE-13517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saikat Maitra reassigned IGNITE-13517: -- Assignee: Saikat Maitra > Disable travis build until ignite nightly snapshots packages are published > -- > > Key: IGNITE-13517 > URL: https://issues.apache.org/jira/browse/IGNITE-13517 > Project: Ignite > Issue Type: Sub-task >Reporter: Saikat Maitra >Assignee: Saikat Maitra >Priority: Minor > > Disable travis build until ignite nightly snapshots packages are published. > This is causing build failure for travis CI since travis is unable to pull > the required dependencies. > > We used to publish nightly packages earlier in the apache snapshot repository > but we are no longer publishing the packages. > > [https://repository.apache.org/content/repositories/snapshots/org/apache/ignite/ignite-core/] > > I have created following Jira story for the same > https://issues.apache.org/jira/browse/IGNITE-13412 > > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13517) Disable travis build until ignite nightly snapshots packages are published
Saikat Maitra created IGNITE-13517: -- Summary: Disable travis build until ignite nightly snapshots packages are published Key: IGNITE-13517 URL: https://issues.apache.org/jira/browse/IGNITE-13517 Project: Ignite Issue Type: Sub-task Reporter: Saikat Maitra Disable travis build until ignite nightly snapshots packages are published. This is causing build failure for travis CI since travis is unable to pull the required dependencies. We used to publish nightly packages earlier in the apache snapshot repository but we are no longer publishing the packages. [https://repository.apache.org/content/repositories/snapshots/org/apache/ignite/ignite-core/] I have created following Jira story for the same https://issues.apache.org/jira/browse/IGNITE-13412 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12952) Enable travis ci for ignite-extensions
[ https://issues.apache.org/jira/browse/IGNITE-12952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17206898#comment-17206898 ] Saikat Maitra commented on IGNITE-12952: This issue is blocked by IGNITE-13412 > Enable travis ci for ignite-extensions > -- > > Key: IGNITE-12952 > URL: https://issues.apache.org/jira/browse/IGNITE-12952 > Project: Ignite > Issue Type: Sub-task > Components: streaming >Reporter: Saikat Maitra >Priority: Minor > > Enable travis ci for ignite-extensions. > We have recently enabled travis ci in ignite repo and checking for build > results for PR and merge to master process. > This subtask is to enable travis ci in ignite-extensions repo. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-12952) Enable travis ci for ignite-extensions
[ https://issues.apache.org/jira/browse/IGNITE-12952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saikat Maitra reassigned IGNITE-12952: -- Assignee: (was: Saikat Maitra) > Enable travis ci for ignite-extensions > -- > > Key: IGNITE-12952 > URL: https://issues.apache.org/jira/browse/IGNITE-12952 > Project: Ignite > Issue Type: Sub-task > Components: streaming >Reporter: Saikat Maitra >Priority: Minor > > Enable travis ci for ignite-extensions. > We have recently enabled travis ci in ignite repo and checking for build > results for PR and merge to master process. > This subtask is to enable travis ci in ignite-extensions repo. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13394) Migrate Kafka module to ignite-extensions
[ https://issues.apache.org/jira/browse/IGNITE-13394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17206891#comment-17206891 ] Saikat Maitra commented on IGNITE-13394: [~ilyak] I have updated the PR [https://github.com/apache/ignite/pull/8222] Can you please review and share if it is good to merge? Regards, Saikat > Migrate Kafka module to ignite-extensions > - > > Key: IGNITE-13394 > URL: https://issues.apache.org/jira/browse/IGNITE-13394 > Project: Ignite > Issue Type: Sub-task > Components: streaming >Reporter: Saikat Maitra >Assignee: Saikat Maitra >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > Migrate Kafka module to ignite-extensions > [https://github.com/apache/ignite-extensions] > Details: > [https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization#IEP-36:Modularization-IndependentIntegrations] > Discussion : > [http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Proposal-for-Ignite-Extensions-as-a-separate-Bahir-module-or-Incubator-project-td44064.html#a44107] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13412) Publish nightly snapshot in apache repository
Saikat Maitra created IGNITE-13412: -- Summary: Publish nightly snapshot in apache repository Key: IGNITE-13412 URL: https://issues.apache.org/jira/browse/IGNITE-13412 Project: Ignite Issue Type: Improvement Components: streaming Reporter: Saikat Maitra We used to publish nightly packages earlier in the apache snapshot repository but we are no longer publishing the packages. [https://repository.apache.org/content/repositories/snapshots/org/apache/ignite/ignite-core/] The last published package was [2.2.2-SNAPSHOT/|https://repository.apache.org/content/repositories/snapshots/org/apache/ignite/ignite-core/2.2.2-SNAPSHOT/] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12364) Migrate JMS module to ignite-extensions
[ https://issues.apache.org/jira/browse/IGNITE-12364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17191778#comment-17191778 ] Saikat Maitra commented on IGNITE-12364: [~ilyak] Thank you for sharing the feedback. I will update the below files jms11 exclusion from assembly/dependencies-apache-ignite-slim.xml modules/osgi-karaf/src/main/resources/features.xml to use ignite-ext > Migrate JMS module to ignite-extensions > --- > > Key: IGNITE-12364 > URL: https://issues.apache.org/jira/browse/IGNITE-12364 > Project: Ignite > Issue Type: Sub-task > Components: streaming >Reporter: Saikat Maitra >Assignee: Saikat Maitra >Priority: Major > Time Spent: 40m > Remaining Estimate: 0h > > Migrate JMS module to ignite-extensions > [https://github.com/apache/ignite-extensions] > Details: > [https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization#IEP-36:Modularization-IndependentIntegrations] > Discussion : > [http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Proposal-for-Ignite-Extensions-as-a-separate-Bahir-module-or-Incubator-project-td44064.html#a44107] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13406) support for Apache Camel 3.x
[
https://issues.apache.org/jira/browse/IGNITE-13406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17191360#comment-17191360
]
Saikat Maitra commented on IGNITE-13406:
Hi [~scottmf] Thank you for making the changes. I observed that the build for
the PR failed
(https://ci.ignite.apache.org/buildConfiguration/Tests_IgniteExtensions_Build/5587084?buildTab=log=3=2010)
due to missing dependencies in artifactory.
I have made a separate PR for fix the dependencies error.
https://github.com/apache/ignite-extensions/pull/22
> support for Apache Camel 3.x
>
>
> Key: IGNITE-13406
> URL: https://issues.apache.org/jira/browse/IGNITE-13406
> Project: Ignite
> Issue Type: Improvement
> Components: streaming
>Reporter: Scott Feldstein
>Priority: Major
>
> Currently the stream libs only support camel 2.x. When camel 3.x is used
> errors come up.
> Here is an example:
> {code:java}
> Caused by: java.lang.NoClassDefFoundError:
> org/apache/camel/util/CamelContextHelper
> at
> org.apache.ignite.stream.camel.CamelStreamer.start(CamelStreamer.java:95)
> at
> com.example.ignite.CamelKafkaIgniteApplicationTest$Config.camelStreamer(CamelKafkaIgniteApplicationTest.java:158)
> at
> com.example.ignite.CamelKafkaIgniteApplicationTest$Config$$EnhancerBySpringCGLIB$$dd8ac36c.CGLIB$camelStreamer$2()
> at
> com.example.ignite.CamelKafkaIgniteApplicationTest$Config$$EnhancerBySpringCGLIB$$dd8ac36c$$FastClassBySpringCGLIB$$5a773dea.invoke()
> at
> org.springframework.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:244)
> at
> org.springframework.context.annotation.ConfigurationClassEnhancer$BeanMethodInterceptor.intercept(ConfigurationClassEnhancer.java:331)
> at
> com.example.ignite.CamelKafkaIgniteApplicationTest$Config$$EnhancerBySpringCGLIB$$dd8ac36c.camelStreamer()
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:154)
> ... 108 more
> Caused by: java.lang.ClassNotFoundException:
> org.apache.camel.util.CamelContextHelper
> at java.net.URLClassLoader.findClass(URLClassLoader.java:382)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:352)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
> ... 120 more
> {code}
> The {{org/apache/camel/util/CamelContextHelper}} class has been moved in
> camel 3.x per the [camel 3.x migration
> doc|https://camel.apache.org/manual/latest/camel-3-migration-guide.html]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-13407) Upgrade ignite.version to 2.10.0-SNAPSHOT in Ignite Extensions
[ https://issues.apache.org/jira/browse/IGNITE-13407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saikat Maitra reassigned IGNITE-13407: -- Assignee: Saikat Maitra > Upgrade ignite.version to 2.10.0-SNAPSHOT in Ignite Extensions > -- > > Key: IGNITE-13407 > URL: https://issues.apache.org/jira/browse/IGNITE-13407 > Project: Ignite > Issue Type: Sub-task > Components: streaming >Reporter: Saikat Maitra >Assignee: Saikat Maitra >Priority: Major > > Upgrade ignite.version to 2.10.0-SNAPSHOT in Ignite Extensions -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13407) Upgrade ignite.version to 2.10.0-SNAPSHOT in Ignite Extensions
Saikat Maitra created IGNITE-13407: -- Summary: Upgrade ignite.version to 2.10.0-SNAPSHOT in Ignite Extensions Key: IGNITE-13407 URL: https://issues.apache.org/jira/browse/IGNITE-13407 Project: Ignite Issue Type: Sub-task Components: streaming Reporter: Saikat Maitra Upgrade ignite.version to 2.10.0-SNAPSHOT in Ignite Extensions -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-12364) Migrate JMS module to ignite-extensions
[ https://issues.apache.org/jira/browse/IGNITE-12364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saikat Maitra closed IGNITE-12364. -- > Migrate JMS module to ignite-extensions > --- > > Key: IGNITE-12364 > URL: https://issues.apache.org/jira/browse/IGNITE-12364 > Project: Ignite > Issue Type: Sub-task > Components: streaming >Reporter: Saikat Maitra >Assignee: Saikat Maitra >Priority: Major > Time Spent: 40m > Remaining Estimate: 0h > > Migrate JMS module to ignite-extensions > [https://github.com/apache/ignite-extensions] > Details: > [https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization#IEP-36:Modularization-IndependentIntegrations] > Discussion : > [http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Proposal-for-Ignite-Extensions-as-a-separate-Bahir-module-or-Incubator-project-td44064.html#a44107] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-13394) Migrate Kafka module to ignite-extensions
[ https://issues.apache.org/jira/browse/IGNITE-13394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saikat Maitra reassigned IGNITE-13394: -- Assignee: Saikat Maitra > Migrate Kafka module to ignite-extensions > - > > Key: IGNITE-13394 > URL: https://issues.apache.org/jira/browse/IGNITE-13394 > Project: Ignite > Issue Type: Sub-task > Components: streaming >Reporter: Saikat Maitra >Assignee: Saikat Maitra >Priority: Major > > Migrate Kafka module to ignite-extensions > [https://github.com/apache/ignite-extensions] > Details: > [https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization#IEP-36:Modularization-IndependentIntegrations] > Discussion : > [http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Proposal-for-Ignite-Extensions-as-a-separate-Bahir-module-or-Incubator-project-td44064.html#a44107] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-12355) IEP-36: Modularization
[ https://issues.apache.org/jira/browse/IGNITE-12355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saikat Maitra reassigned IGNITE-12355: -- Assignee: Saikat Maitra > IEP-36: Modularization > -- > > Key: IGNITE-12355 > URL: https://issues.apache.org/jira/browse/IGNITE-12355 > Project: Ignite > Issue Type: Improvement > Components: streaming >Affects Versions: 2.8 >Reporter: Saikat Maitra >Assignee: Saikat Maitra >Priority: Major > > Migrate streaming modules in ignite-extensions repo > > [https://github.com/apache/ignite-extensions] > > Details: > [https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization#IEP-36:Modularization-IndependentIntegrations] > Discussion : > [http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Proposal-for-Ignite-Extensions-as-a-separate-Bahir-module-or-Incubator-project-td44064.html#a44107] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-12364) Migrate JMS module to ignite-extensions
[ https://issues.apache.org/jira/browse/IGNITE-12364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saikat Maitra reassigned IGNITE-12364: -- Assignee: Saikat Maitra > Migrate JMS module to ignite-extensions > --- > > Key: IGNITE-12364 > URL: https://issues.apache.org/jira/browse/IGNITE-12364 > Project: Ignite > Issue Type: Sub-task > Components: streaming >Reporter: Saikat Maitra >Assignee: Saikat Maitra >Priority: Major > > Migrate JMS module to ignite-extensions > [https://github.com/apache/ignite-extensions] > Details: > [https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization#IEP-36:Modularization-IndependentIntegrations] > Discussion : > [http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Proposal-for-Ignite-Extensions-as-a-separate-Bahir-module-or-Incubator-project-td44064.html#a44107] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13394) Migrate Kafka module to ignite-extensions
[ https://issues.apache.org/jira/browse/IGNITE-13394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saikat Maitra updated IGNITE-13394: --- Description: Migrate Kafka module to ignite-extensions [https://github.com/apache/ignite-extensions] Details: [https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization#IEP-36:Modularization-IndependentIntegrations] Discussion : [http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Proposal-for-Ignite-Extensions-as-a-separate-Bahir-module-or-Incubator-project-td44064.html#a44107] was: Migrate JMS module to ignite-extensions [https://github.com/apache/ignite-extensions] Details: [https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization#IEP-36:Modularization-IndependentIntegrations] Discussion : [http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Proposal-for-Ignite-Extensions-as-a-separate-Bahir-module-or-Incubator-project-td44064.html#a44107] > Migrate Kafka module to ignite-extensions > - > > Key: IGNITE-13394 > URL: https://issues.apache.org/jira/browse/IGNITE-13394 > Project: Ignite > Issue Type: Sub-task > Components: streaming >Reporter: Saikat Maitra >Priority: Major > > Migrate Kafka module to ignite-extensions > [https://github.com/apache/ignite-extensions] > Details: > [https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization#IEP-36:Modularization-IndependentIntegrations] > Discussion : > [http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Proposal-for-Ignite-Extensions-as-a-separate-Bahir-module-or-Incubator-project-td44064.html#a44107] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13394) Migrate Kafka module to ignite-extensions
Saikat Maitra created IGNITE-13394: -- Summary: Migrate Kafka module to ignite-extensions Key: IGNITE-13394 URL: https://issues.apache.org/jira/browse/IGNITE-13394 Project: Ignite Issue Type: Sub-task Components: streaming Reporter: Saikat Maitra Migrate JMS module to ignite-extensions [https://github.com/apache/ignite-extensions] Details: [https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization#IEP-36:Modularization-IndependentIntegrations] Discussion : [http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Proposal-for-Ignite-Extensions-as-a-separate-Bahir-module-or-Incubator-project-td44064.html#a44107] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-12363) Migrate Camel module to ignite-extensions
[ https://issues.apache.org/jira/browse/IGNITE-12363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saikat Maitra closed IGNITE-12363. -- > Migrate Camel module to ignite-extensions > - > > Key: IGNITE-12363 > URL: https://issues.apache.org/jira/browse/IGNITE-12363 > Project: Ignite > Issue Type: Sub-task > Components: streaming >Reporter: Saikat Maitra >Assignee: Saikat Maitra >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > Migrate Camel module to ignite-extensions > [https://github.com/apache/ignite-extensions] > Details: > [https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization#IEP-36:Modularization-IndependentIntegrations] > Discussion : > [http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Proposal-for-Ignite-Extensions-as-a-separate-Bahir-module-or-Incubator-project-td44064.html#a44107] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12228) Implement an Apache Beam runner on top of Ignite compute grid?
[ https://issues.apache.org/jira/browse/IGNITE-12228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17178374#comment-17178374 ] Saikat Maitra commented on IGNITE-12228: I have raised a PR for early feedback. [https://github.com/apache/beam/pull/12593/files] I have created IgniteRunner and IgnitePipelineOptions. I have implemented normalize pipeline method and currently working on run method implementation for Pipeline and IgnitePipelineTranslator > Implement an Apache Beam runner on top of Ignite compute grid? > -- > > Key: IGNITE-12228 > URL: https://issues.apache.org/jira/browse/IGNITE-12228 > Project: Ignite > Issue Type: Wish >Reporter: Romain Manni-Bucau >Assignee: Saikat Maitra >Priority: Major > > Apache Ignite provides a compute grid. > It is therefore feasible to use that to execute a DAG pipeline. > Therefore implementing a Apache Beam runner executing a DAG on an ignite > cluster would be very valuable for users and would provide a very interesting > alternative to Spark, Dataflow etc...which would be very valuable when using > data from ignite itself. > Hoping it can help, here is Hazelcast Jet implementation which is not that > far even if Jet is a bit more advanced in term of DAG support: > [https://github.com/apache/beam/tree/master/runners/jet-experimental/src/main/java/org/apache/beam/runners/jet] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-12363) Migrate Camel module to ignite-extensions
[ https://issues.apache.org/jira/browse/IGNITE-12363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saikat Maitra reassigned IGNITE-12363: -- Assignee: Saikat Maitra > Migrate Camel module to ignite-extensions > - > > Key: IGNITE-12363 > URL: https://issues.apache.org/jira/browse/IGNITE-12363 > Project: Ignite > Issue Type: Sub-task > Components: streaming >Reporter: Saikat Maitra >Assignee: Saikat Maitra >Priority: Major > > Migrate Camel module to ignite-extensions > [https://github.com/apache/ignite-extensions] > Details: > [https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization#IEP-36:Modularization-IndependentIntegrations] > Discussion : > [http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Proposal-for-Ignite-Extensions-as-a-separate-Bahir-module-or-Incubator-project-td44064.html#a44107] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-12360) Migrate Storm module to ignite-extensions
[ https://issues.apache.org/jira/browse/IGNITE-12360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saikat Maitra closed IGNITE-12360. -- > Migrate Storm module to ignite-extensions > - > > Key: IGNITE-12360 > URL: https://issues.apache.org/jira/browse/IGNITE-12360 > Project: Ignite > Issue Type: Sub-task > Components: streaming >Affects Versions: 2.8 >Reporter: Saikat Maitra >Assignee: Saikat Maitra >Priority: Major > Time Spent: 40m > Remaining Estimate: 0h > > Migrate Storm module to ignite-extensions > [https://github.com/apache/ignite-extensions] > Details: > [https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization#IEP-36:Modularization-IndependentIntegrations] > Discussion : > [http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Proposal-for-Ignite-Extensions-as-a-separate-Bahir-module-or-Incubator-project-td44064.html#a44107] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-12360) Migrate Storm module to ignite-extensions
[ https://issues.apache.org/jira/browse/IGNITE-12360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saikat Maitra reassigned IGNITE-12360: -- Assignee: Saikat Maitra > Migrate Storm module to ignite-extensions > - > > Key: IGNITE-12360 > URL: https://issues.apache.org/jira/browse/IGNITE-12360 > Project: Ignite > Issue Type: Sub-task > Components: streaming >Affects Versions: 2.8 >Reporter: Saikat Maitra >Assignee: Saikat Maitra >Priority: Major > > Migrate Storm module to ignite-extensions > [https://github.com/apache/ignite-extensions] > Details: > [https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization#IEP-36:Modularization-IndependentIntegrations] > Discussion : > [http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Proposal-for-Ignite-Extensions-as-a-separate-Bahir-module-or-Incubator-project-td44064.html#a44107] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12362) Migrate MQTT module to ignite-extensions
[ https://issues.apache.org/jira/browse/IGNITE-12362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17156845#comment-17156845 ] Saikat Maitra commented on IGNITE-12362: [~ibessonov] Yes Sure, I have updated the Streamers testsuite. [https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_Streamers/5459379?buildTab=overview] > Migrate MQTT module to ignite-extensions > > > Key: IGNITE-12362 > URL: https://issues.apache.org/jira/browse/IGNITE-12362 > Project: Ignite > Issue Type: Sub-task > Components: streaming >Affects Versions: 2.8 >Reporter: Saikat Maitra >Assignee: Saikat Maitra >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > Migrate MQTT module to ignite-extensions > [https://github.com/apache/ignite-extensions] > Details: > [https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization#IEP-36:Modularization-IndependentIntegrations] > Discussion : > [http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Proposal-for-Ignite-Extensions-as-a-separate-Bahir-module-or-Incubator-project-td44064.html#a44107] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-12362) Migrate MQTT module to ignite-extensions
[ https://issues.apache.org/jira/browse/IGNITE-12362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saikat Maitra closed IGNITE-12362. -- > Migrate MQTT module to ignite-extensions > > > Key: IGNITE-12362 > URL: https://issues.apache.org/jira/browse/IGNITE-12362 > Project: Ignite > Issue Type: Sub-task > Components: streaming >Affects Versions: 2.8 >Reporter: Saikat Maitra >Assignee: Saikat Maitra >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > Migrate MQTT module to ignite-extensions > [https://github.com/apache/ignite-extensions] > Details: > [https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization#IEP-36:Modularization-IndependentIntegrations] > Discussion : > [http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Proposal-for-Ignite-Extensions-as-a-separate-Bahir-module-or-Incubator-project-td44064.html#a44107] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-12362) Migrate MQTT module to ignite-extensions
[ https://issues.apache.org/jira/browse/IGNITE-12362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saikat Maitra reassigned IGNITE-12362: -- Assignee: Saikat Maitra > Migrate MQTT module to ignite-extensions > > > Key: IGNITE-12362 > URL: https://issues.apache.org/jira/browse/IGNITE-12362 > Project: Ignite > Issue Type: Sub-task > Components: streaming >Affects Versions: 2.8 >Reporter: Saikat Maitra >Assignee: Saikat Maitra >Priority: Major > > Migrate MQTT module to ignite-extensions > [https://github.com/apache/ignite-extensions] > Details: > [https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization#IEP-36:Modularization-IndependentIntegrations] > Discussion : > [http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Proposal-for-Ignite-Extensions-as-a-separate-Bahir-module-or-Incubator-project-td44064.html#a44107] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12952) Enable travis ci for ignite-extensions
[ https://issues.apache.org/jira/browse/IGNITE-12952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17141170#comment-17141170 ] Saikat Maitra commented on IGNITE-12952: We have enabled the travis build for ignite-extensions ([https://travis-ci.org/github/apache/ignite-extensions]) but it has dependency on ignite-core 2.9.0-snapshot jars. I was looking into our nightly snapshots repository paths and could not find the latest snapshots build. [https://repository.apache.org/content/repositories/snapshots/org/apache/ignite/ignite-core/] In teamcity we have been able to resolve this dependency since ignite-extensions teamcity build agent was able to pull nightly snapshots from main ignite build. As discussed with Petr Ivanov we currently do not publish the nightly artifacts to maven staging repository. > Enable travis ci for ignite-extensions > -- > > Key: IGNITE-12952 > URL: https://issues.apache.org/jira/browse/IGNITE-12952 > Project: Ignite > Issue Type: Sub-task > Components: streaming >Reporter: Saikat Maitra >Assignee: Saikat Maitra >Priority: Minor > > Enable travis ci for ignite-extensions. > We have recently enabled travis ci in ignite repo and checking for build > results for PR and merge to master process. > This subtask is to enable travis ci in ignite-extensions repo. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-12952) Enable travis ci for ignite-extensions
[ https://issues.apache.org/jira/browse/IGNITE-12952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saikat Maitra reassigned IGNITE-12952: -- Assignee: Saikat Maitra > Enable travis ci for ignite-extensions > -- > > Key: IGNITE-12952 > URL: https://issues.apache.org/jira/browse/IGNITE-12952 > Project: Ignite > Issue Type: Sub-task > Components: streaming >Reporter: Saikat Maitra >Assignee: Saikat Maitra >Priority: Minor > > Enable travis ci for ignite-extensions. > We have recently enabled travis ci in ignite repo and checking for build > results for PR and merge to master process. > This subtask is to enable travis ci in ignite-extensions repo. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-12359) Migrate RocketMQ module to ignite-extensions
[ https://issues.apache.org/jira/browse/IGNITE-12359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saikat Maitra closed IGNITE-12359. -- > Migrate RocketMQ module to ignite-extensions > > > Key: IGNITE-12359 > URL: https://issues.apache.org/jira/browse/IGNITE-12359 > Project: Ignite > Issue Type: Sub-task > Components: streaming >Affects Versions: 2.8 >Reporter: Saikat Maitra >Assignee: Saikat Maitra >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > Migrate RocketMQ module to ignite-extensions > [https://github.com/apache/ignite-extensions] > Details: > [https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization#IEP-36:Modularization-IndependentIntegrations] > Discussion : > [http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Proposal-for-Ignite-Extensions-as-a-separate-Bahir-module-or-Incubator-project-td44064.html#a44107] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12359) Migrate RocketMQ module to ignite-extensions
[ https://issues.apache.org/jira/browse/IGNITE-12359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17120637#comment-17120637 ] Saikat Maitra commented on IGNITE-12359: [~ilyak] Thank you for reviewing the changes. I have updated the PR and merged the changes. > Migrate RocketMQ module to ignite-extensions > > > Key: IGNITE-12359 > URL: https://issues.apache.org/jira/browse/IGNITE-12359 > Project: Ignite > Issue Type: Sub-task > Components: streaming >Affects Versions: 2.8 >Reporter: Saikat Maitra >Assignee: Saikat Maitra >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > Migrate RocketMQ module to ignite-extensions > [https://github.com/apache/ignite-extensions] > Details: > [https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization#IEP-36:Modularization-IndependentIntegrations] > Discussion : > [http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Proposal-for-Ignite-Extensions-as-a-separate-Bahir-module-or-Incubator-project-td44064.html#a44107] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-12359) Migrate RocketMQ module to ignite-extensions
[ https://issues.apache.org/jira/browse/IGNITE-12359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saikat Maitra reassigned IGNITE-12359: -- Assignee: Saikat Maitra > Migrate RocketMQ module to ignite-extensions > > > Key: IGNITE-12359 > URL: https://issues.apache.org/jira/browse/IGNITE-12359 > Project: Ignite > Issue Type: Sub-task > Components: streaming >Affects Versions: 2.8 >Reporter: Saikat Maitra >Assignee: Saikat Maitra >Priority: Major > > Migrate RocketMQ module to ignite-extensions > [https://github.com/apache/ignite-extensions] > Details: > [https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization#IEP-36:Modularization-IndependentIntegrations] > Discussion : > [http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Proposal-for-Ignite-Extensions-as-a-separate-Bahir-module-or-Incubator-project-td44064.html#a44107] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-12997) Rename pub-sub module to pub-sub-ext
[ https://issues.apache.org/jira/browse/IGNITE-12997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saikat Maitra closed IGNITE-12997. -- > Rename pub-sub module to pub-sub-ext > > > Key: IGNITE-12997 > URL: https://issues.apache.org/jira/browse/IGNITE-12997 > Project: Ignite > Issue Type: Sub-task > Components: streaming >Reporter: Saikat Maitra >Assignee: Saikat Maitra >Priority: Trivial > > Rename pub-sub module to pub-sub-ext. All the modules in ignite-extensions > project are named with suffix "-ext". This will make pub-sub module name to > be consistent with other modules. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12997) Rename pub-sub module to pub-sub-ext
Saikat Maitra created IGNITE-12997: -- Summary: Rename pub-sub module to pub-sub-ext Key: IGNITE-12997 URL: https://issues.apache.org/jira/browse/IGNITE-12997 Project: Ignite Issue Type: Sub-task Components: streaming Reporter: Saikat Maitra Assignee: Saikat Maitra Rename pub-sub module to pub-sub-ext. All the modules in ignite-extensions project are named with suffix "-ext". This will make pub-sub module name to be consistent with other modules. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12960) Remove twitter module tests from Teamcity Streamers TestSuite
[ https://issues.apache.org/jira/browse/IGNITE-12960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17097782#comment-17097782 ] Saikat Maitra commented on IGNITE-12960: I have removed twitter module and twitter streamer testsuite from teamcity Streamers build configurations. > Remove twitter module tests from Teamcity Streamers TestSuite > - > > Key: IGNITE-12960 > URL: https://issues.apache.org/jira/browse/IGNITE-12960 > Project: Ignite > Issue Type: Sub-task > Components: streaming >Reporter: Saikat Maitra >Assignee: Saikat Maitra >Priority: Major > > Remove twitter module tests from Teamcity Streamers TestSuite > This issue is related to https://issues.apache.org/jira/browse/IGNITE-12357 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-12960) Remove twitter module tests from Teamcity Streamers TestSuite
[ https://issues.apache.org/jira/browse/IGNITE-12960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saikat Maitra closed IGNITE-12960. -- > Remove twitter module tests from Teamcity Streamers TestSuite > - > > Key: IGNITE-12960 > URL: https://issues.apache.org/jira/browse/IGNITE-12960 > Project: Ignite > Issue Type: Sub-task > Components: streaming >Reporter: Saikat Maitra >Assignee: Saikat Maitra >Priority: Major > > Remove twitter module tests from Teamcity Streamers TestSuite > This issue is related to https://issues.apache.org/jira/browse/IGNITE-12357 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-12960) Remove twitter module tests from Teamcity Streamers TestSuite
[ https://issues.apache.org/jira/browse/IGNITE-12960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saikat Maitra resolved IGNITE-12960. Resolution: Fixed > Remove twitter module tests from Teamcity Streamers TestSuite > - > > Key: IGNITE-12960 > URL: https://issues.apache.org/jira/browse/IGNITE-12960 > Project: Ignite > Issue Type: Sub-task > Components: streaming >Reporter: Saikat Maitra >Assignee: Saikat Maitra >Priority: Major > > Remove twitter module tests from Teamcity Streamers TestSuite > This issue is related to https://issues.apache.org/jira/browse/IGNITE-12357 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-12357) Migrate Twitter module to ignite-extensions
[ https://issues.apache.org/jira/browse/IGNITE-12357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saikat Maitra closed IGNITE-12357. -- > Migrate Twitter module to ignite-extensions > --- > > Key: IGNITE-12357 > URL: https://issues.apache.org/jira/browse/IGNITE-12357 > Project: Ignite > Issue Type: Sub-task > Components: streaming >Affects Versions: 2.8 >Reporter: Saikat Maitra >Assignee: Saikat Maitra >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Migrate Twitter module to ignite-extensions. > [https://github.com/apache/ignite-extensions] > Details: > [https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization#IEP-36:Modularization-IndependentIntegrations] > Discussion : > [http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Proposal-for-Ignite-Extensions-as-a-separate-Bahir-module-or-Incubator-project-td44064.html#a44107] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-12960) Remove twitter module tests from Teamcity Streamers TestSuite
[ https://issues.apache.org/jira/browse/IGNITE-12960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saikat Maitra reassigned IGNITE-12960: -- Assignee: Saikat Maitra > Remove twitter module tests from Teamcity Streamers TestSuite > - > > Key: IGNITE-12960 > URL: https://issues.apache.org/jira/browse/IGNITE-12960 > Project: Ignite > Issue Type: Sub-task > Components: streaming >Reporter: Saikat Maitra >Assignee: Saikat Maitra >Priority: Major > > Remove twitter module tests from Teamcity Streamers TestSuite > This issue is related to https://issues.apache.org/jira/browse/IGNITE-12357 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12357) Migrate Twitter module to ignite-extensions
[ https://issues.apache.org/jira/browse/IGNITE-12357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17097757#comment-17097757 ] Saikat Maitra commented on IGNITE-12357: [~dmagda] Hi Denis, Thank you for reviewing the changes. I'm tracking the changes required for docs in this Jira story https://issues.apache.org/jira/browse/IGNITE-12951 I have added 3 set of changes including README, Technical docs and Ignite website changes. Please let me know if any additional changes need to be added. Regards, Saikat > Migrate Twitter module to ignite-extensions > --- > > Key: IGNITE-12357 > URL: https://issues.apache.org/jira/browse/IGNITE-12357 > Project: Ignite > Issue Type: Sub-task > Components: streaming >Affects Versions: 2.8 >Reporter: Saikat Maitra >Assignee: Saikat Maitra >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Migrate Twitter module to ignite-extensions. > [https://github.com/apache/ignite-extensions] > Details: > [https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization#IEP-36:Modularization-IndependentIntegrations] > Discussion : > [http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Proposal-for-Ignite-Extensions-as-a-separate-Bahir-module-or-Incubator-project-td44064.html#a44107] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12951) Update documents for migrated extensions
[
https://issues.apache.org/jira/browse/IGNITE-12951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Saikat Maitra updated IGNITE-12951:
---
Description:
# Update README for migrated extensions.The newly migrated extensions modules
have suffix -ext in the artifact name.Review and update extensions README docs
to correct artifact name. An example for correct artifact name would be
ignite-flink-ext
# We need to update some sections (maven artifacts name, a paragraph about
the extensions repository) in existing docs before the extension is released:
[https://apacheignite-mix.readme.io/docs/twitter-streamer]
#
{quote}{{As for the extensions web page, I see its structure as follows. It
goeswith a header introducing the extensions repository and covering types
ofcontributions that are welcomed there. Then down below in the body we listall
the available extensions - it can be a simple table with an extensionname,
description, URL or a bit more advanced interface with a grid layoutlike on
this page [1]. With the grid layout, we can add logos of theprojects Ignite is
integrated with in addition to the name/description/URL.Let me know what you
think.[1] [https://ignite.apache.org/screencasts.html]}}{quote}
{{[http://apache-ignite-developers.2346864.n4.nabble.com/IGNITE-12358-Migrate-ZeroMQ-module-to-ignite-extensions-td45067.html#a46863]}}
was:
Update README for migrated extensions.
The newly migrated extensions modules have suffix -ext in the artifact name.
Review and update extensions README docs to correct artifact name.
An example for correct artifact name would be ignite-flink-ext
> Update documents for migrated extensions
>
>
> Key: IGNITE-12951
> URL: https://issues.apache.org/jira/browse/IGNITE-12951
> Project: Ignite
> Issue Type: Sub-task
> Components: streaming
>Reporter: Saikat Maitra
>Priority: Major
>
> # Update README for migrated extensions.The newly migrated extensions modules
> have suffix -ext in the artifact name.Review and update extensions README
> docs to correct artifact name. An example for correct artifact name would be
> ignite-flink-ext
> # We need to update some sections (maven artifacts name, a paragraph about
> the extensions repository) in existing docs before the extension is released:
> [https://apacheignite-mix.readme.io/docs/twitter-streamer]
> #
> {quote}{{As for the extensions web page, I see its structure as follows. It
> goeswith a header introducing the extensions repository and covering types
> ofcontributions that are welcomed there. Then down below in the body we
> listall the available extensions - it can be a simple table with an
> extensionname, description, URL or a bit more advanced interface with a grid
> layoutlike on this page [1]. With the grid layout, we can add logos of
> theprojects Ignite is integrated with in addition to the
> name/description/URL.Let me know what you think.[1]
> [https://ignite.apache.org/screencasts.html]}}{quote}
>
> {{[http://apache-ignite-developers.2346864.n4.nabble.com/IGNITE-12358-Migrate-ZeroMQ-module-to-ignite-extensions-td45067.html#a46863]}}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12951) Update documents for migrated extensions
[ https://issues.apache.org/jira/browse/IGNITE-12951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saikat Maitra updated IGNITE-12951: --- Summary: Update documents for migrated extensions (was: Update README for migrated extensions) > Update documents for migrated extensions > > > Key: IGNITE-12951 > URL: https://issues.apache.org/jira/browse/IGNITE-12951 > Project: Ignite > Issue Type: Sub-task > Components: streaming >Reporter: Saikat Maitra >Priority: Major > > Update README for migrated extensions. > The newly migrated extensions modules have suffix -ext in the artifact name. > Review and update extensions README docs to correct artifact name. > An example for correct artifact name would be ignite-flink-ext -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12960) Remove twitter module tests from Teamcity Streamers TestSuite
Saikat Maitra created IGNITE-12960: -- Summary: Remove twitter module tests from Teamcity Streamers TestSuite Key: IGNITE-12960 URL: https://issues.apache.org/jira/browse/IGNITE-12960 Project: Ignite Issue Type: Sub-task Components: streaming Reporter: Saikat Maitra Remove twitter module tests from Teamcity Streamers TestSuite This issue is related to https://issues.apache.org/jira/browse/IGNITE-12357 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12952) Enable travis ci for ignite-extensions
Saikat Maitra created IGNITE-12952: -- Summary: Enable travis ci for ignite-extensions Key: IGNITE-12952 URL: https://issues.apache.org/jira/browse/IGNITE-12952 Project: Ignite Issue Type: Sub-task Components: streaming Reporter: Saikat Maitra Enable travis ci for ignite-extensions. We have recently enabled travis ci in ignite repo and checking for build results for PR and merge to master process. This subtask is to enable travis ci in ignite-extensions repo. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12951) Update README for migrated extensions
Saikat Maitra created IGNITE-12951: -- Summary: Update README for migrated extensions Key: IGNITE-12951 URL: https://issues.apache.org/jira/browse/IGNITE-12951 Project: Ignite Issue Type: Sub-task Components: streaming Reporter: Saikat Maitra Update README for migrated extensions. The newly migrated extensions modules have suffix -ext in the artifact name. Review and update extensions README docs to correct artifact name. An example for correct artifact name would be ignite-flink-ext -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-12357) Migrate Twitter module to ignite-extensions
[ https://issues.apache.org/jira/browse/IGNITE-12357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saikat Maitra reassigned IGNITE-12357: -- Assignee: Saikat Maitra > Migrate Twitter module to ignite-extensions > --- > > Key: IGNITE-12357 > URL: https://issues.apache.org/jira/browse/IGNITE-12357 > Project: Ignite > Issue Type: Sub-task > Components: streaming >Affects Versions: 2.8 >Reporter: Saikat Maitra >Assignee: Saikat Maitra >Priority: Major > > Migrate Twitter module to ignite-extensions. > [https://github.com/apache/ignite-extensions] > Details: > [https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization#IEP-36:Modularization-IndependentIntegrations] > Discussion : > [http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Proposal-for-Ignite-Extensions-as-a-separate-Bahir-module-or-Incubator-project-td44064.html#a44107] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12926) [ignite-extensions] build failed
[
https://issues.apache.org/jira/browse/IGNITE-12926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17089180#comment-17089180
]
Saikat Maitra commented on IGNITE-12926:
[~nizhikov]
I have reviewed the PR and the changes looks good.
Thank you,
Saikat
> [ignite-extensions] build failed
>
>
> Key: IGNITE-12926
> URL: https://issues.apache.org/jira/browse/IGNITE-12926
> Project: Ignite
> Issue Type: Test
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Blocker
>
> The current master in ignite-extension can't be built.
> The reason in parent pom.xml which contains
> org.apache.ignite:ignite-tools:1.0-SNAPSHOT dependency for Javadoc plugin.
> The version has taken from the project version.
> {noformat}
>
> org.apache.maven.plugins
> maven-javadoc-plugin
> ${maven.javadoc.plugin.version}
>
>
>
>
> org.apache.ignite.tools.javadoc.IgniteLinkTaglet
>
> org.apache.ignite
> ignite-tools
> ${project.version}
>
>
>
> Ignite ${project.version}
> Ignite ${project.version}
> true
> true
> protected
> true
> false
> false
> ${javadoc.opts}
> {noformat}
> {noformat}
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] ignite-flink-ext 1.0.0-SNAPSHOT FAILURE [ 5.227
> s]
> [INFO] ignite-flume-ext 1.0.0-SNAPSHOT SKIPPED
> [INFO] ignite-pub-sub 2.9.0-SNAPSHOT .. SKIPPED
> [INFO] ignite-spring-boot-autoconfigure 1.0.0-SNAPSHOT SKIPPED
> [INFO] ignite-client-spring-boot-autoconfigure 1.0.0-SNAPSHOT SKIPPED
> [INFO] ignite-zeromq-ext 1.0.0-SNAPSHOT ... SKIPPED
> [INFO] apache-ignite-extensions 1.0.0-SNAPSHOT SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 5.812 s
> [INFO] Finished at: 2020-04-21T13:56:20+03:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-javadoc-plugin:2.10.4:jar (module-javadoc) on
> project ignite-flink-ext: MavenReportException: Error while generating
> Javadoc: Unable to find artifact:groupId = 'org.apache.ignite'
> [ERROR] artifactId = 'ignite-tools'
> [ERROR] version = '1.0.0-SNAPSHOT': Failure to find
> org.apache.ignite:ignite-tools:pom:1.0.0-SNAPSHOT in
> https://h2database.com/m2-repo was cached in the local repository, resolution
> will not be reattempted until the update interval of h2database.com has
> elapsed or updates are forced
> [ERROR]
> [ERROR] org.apache.ignite:ignite-tools:pom:1.0.0-SNAPSHOT
> [ERROR]
> [ERROR] from the specified remote repositories:
> [ERROR] h2database.com (https://h2database.com/m2-repo, releases=false,
> snapshots=true),
> [ERROR] apache.snapshots (http://repository.apache.org/snapshots,
> releases=false, snapshots=true),
> [ERROR] central (https://repo.maven.apache.org/maven2, releases=true,
> snapshots=false)
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (IGNITE-12358) Migrate ZeroMQ module to ignite-extensions
[ https://issues.apache.org/jira/browse/IGNITE-12358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saikat Maitra closed IGNITE-12358. -- > Migrate ZeroMQ module to ignite-extensions > -- > > Key: IGNITE-12358 > URL: https://issues.apache.org/jira/browse/IGNITE-12358 > Project: Ignite > Issue Type: Sub-task > Components: streaming >Affects Versions: 2.8 >Reporter: Saikat Maitra >Assignee: Saikat Maitra >Priority: Major > Time Spent: 40m > Remaining Estimate: 0h > > Migrate ZeroMQ module to ignite-extensions > [https://github.com/apache/ignite-extensions] > Details: > [https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization#IEP-36:Modularization-IndependentIntegrations] > Discussion : > [http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Proposal-for-Ignite-Extensions-as-a-separate-Bahir-module-or-Incubator-project-td44064.html#a44107] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-12361) Migrate Flume module to ignite-extensions
[ https://issues.apache.org/jira/browse/IGNITE-12361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saikat Maitra closed IGNITE-12361. -- > Migrate Flume module to ignite-extensions > - > > Key: IGNITE-12361 > URL: https://issues.apache.org/jira/browse/IGNITE-12361 > Project: Ignite > Issue Type: Sub-task > Components: streaming >Reporter: Saikat Maitra >Assignee: Saikat Maitra >Priority: Major > Time Spent: 40m > Remaining Estimate: 0h > > Migrate Flume module to ignite-extensions > [https://github.com/apache/ignite-extensions] > Details: > [https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization#IEP-36:Modularization-IndependentIntegrations] > Discussion : > [http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Proposal-for-Ignite-Extensions-as-a-separate-Bahir-module-or-Incubator-project-td44064.html#a44107] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12786) Fix ignite sink startup
Saikat Maitra created IGNITE-12786:
--
Summary: Fix ignite sink startup
Key: IGNITE-12786
URL: https://issues.apache.org/jira/browse/IGNITE-12786
Project: Ignite
Issue Type: Bug
Components: streaming
Reporter: Saikat Maitra
Current implementation of {{open}} function in Ignite Sink does not work when
flink {{parallelism}} is set to value higher than one.
Flink quickly starts multiple instances of job and checking first if the
instance is already started and then starting new instance leads to
IgniteException {{Default instance is has already been started}} and job does
not connect to ignite at all. Example test scenario:
# Flink job with parallelism > 1 (higher is better to reproduce) starts
# Job instance 1 checks for ignite existence
# Job instance 2 checks for ignite existence
# Job instance 1 starts ignite -> success
# Job instance 2 starts ignite -> exception
# Flink stops all job instances because of exception on one of its job
instances
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (IGNITE-12645) Added acknowledgement to Pub/Sub streamer messages
[ https://issues.apache.org/jira/browse/IGNITE-12645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saikat Maitra resolved IGNITE-12645. Resolution: Fixed > Added acknowledgement to Pub/Sub streamer messages > --- > > Key: IGNITE-12645 > URL: https://issues.apache.org/jira/browse/IGNITE-12645 > Project: Ignite > Issue Type: Bug > Components: integrations >Reporter: Emmanouil Gkatziouras >Assignee: Emmanouil Gkatziouras >Priority: Major > > Pub/Sub messages received from the Pub/Sub streamer should acknowledge if the > message was received. > Acknowledging messages prevents messages to be delivered more than once. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-12358) Migrate ZeroMQ module to ignite-extensions
[ https://issues.apache.org/jira/browse/IGNITE-12358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saikat Maitra reassigned IGNITE-12358: -- Assignee: Saikat Maitra > Migrate ZeroMQ module to ignite-extensions > -- > > Key: IGNITE-12358 > URL: https://issues.apache.org/jira/browse/IGNITE-12358 > Project: Ignite > Issue Type: Sub-task > Components: streaming >Affects Versions: 2.8 >Reporter: Saikat Maitra >Assignee: Saikat Maitra >Priority: Major > > Migrate ZeroMQ module to ignite-extensions > [https://github.com/apache/ignite-extensions] > Details: > [https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization#IEP-36:Modularization-IndependentIntegrations] > Discussion : > [http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Proposal-for-Ignite-Extensions-as-a-separate-Bahir-module-or-Incubator-project-td44064.html#a44107] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-12356) Migrate Flink module to ignite-extensions
[ https://issues.apache.org/jira/browse/IGNITE-12356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saikat Maitra closed IGNITE-12356. -- > Migrate Flink module to ignite-extensions > - > > Key: IGNITE-12356 > URL: https://issues.apache.org/jira/browse/IGNITE-12356 > Project: Ignite > Issue Type: Sub-task > Components: streaming >Reporter: Saikat Maitra >Assignee: Saikat Maitra >Priority: Major > Time Spent: 40m > Remaining Estimate: 0h > > Migrate Flink module to ignite-extensions > [https://github.com/apache/ignite-extensions] > Details: > [https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization#IEP-36:Modularization-IndependentIntegrations] > Discussion : > [http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Proposal-for-Ignite-Extensions-as-a-separate-Bahir-module-or-Incubator-project-td44064.html#a44107] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-12361) Migrate Flume module to ignite-extensions
[ https://issues.apache.org/jira/browse/IGNITE-12361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saikat Maitra reassigned IGNITE-12361: -- Assignee: Saikat Maitra > Migrate Flume module to ignite-extensions > - > > Key: IGNITE-12361 > URL: https://issues.apache.org/jira/browse/IGNITE-12361 > Project: Ignite > Issue Type: Sub-task > Components: streaming >Reporter: Saikat Maitra >Assignee: Saikat Maitra >Priority: Major > > Migrate Flume module to ignite-extensions > [https://github.com/apache/ignite-extensions] > Details: > [https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization#IEP-36:Modularization-IndependentIntegrations] > Discussion : > [http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Proposal-for-Ignite-Extensions-as-a-separate-Bahir-module-or-Incubator-project-td44064.html#a44107] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-12517) Upgrade flink module version to 1.9.1 in ignite-extensions
[ https://issues.apache.org/jira/browse/IGNITE-12517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saikat Maitra closed IGNITE-12517. -- > Upgrade flink module version to 1.9.1 in ignite-extensions > -- > > Key: IGNITE-12517 > URL: https://issues.apache.org/jira/browse/IGNITE-12517 > Project: Ignite > Issue Type: Improvement > Components: streaming >Reporter: Saikat Maitra >Assignee: Saikat Maitra >Priority: Minor > Fix For: 2.8 > > Time Spent: 20m > Remaining Estimate: 0h > > Upgrade flink module version to 1.9.1 in ignite-extensions > [https://github.com/apache/ignite-extensions] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12517) Upgrade flink module version to 1.9.1 in ignite-extensions
[ https://issues.apache.org/jira/browse/IGNITE-12517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17006141#comment-17006141 ] Saikat Maitra commented on IGNITE-12517: Hi Ilya, Thank you for reviewing the changes. I have shared the teamcity build link below. https://ci.ignite.apache.org/viewLog.html?buildId=4894742=IgniteExtensions_Build=buildResultsDiv_IgniteExtensions=pull%2F3%2Fhead Regards, Saikat > Upgrade flink module version to 1.9.1 in ignite-extensions > -- > > Key: IGNITE-12517 > URL: https://issues.apache.org/jira/browse/IGNITE-12517 > Project: Ignite > Issue Type: Improvement > Components: streaming >Reporter: Saikat Maitra >Assignee: Saikat Maitra >Priority: Minor > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > Upgrade flink module version to 1.9.1 in ignite-extensions > [https://github.com/apache/ignite-extensions] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-12517) Upgrade flink module version to 1.9.1 in ignite-extensions
[ https://issues.apache.org/jira/browse/IGNITE-12517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saikat Maitra reassigned IGNITE-12517: -- Assignee: Saikat Maitra > Upgrade flink module version to 1.9.1 in ignite-extensions > -- > > Key: IGNITE-12517 > URL: https://issues.apache.org/jira/browse/IGNITE-12517 > Project: Ignite > Issue Type: Improvement > Components: streaming >Reporter: Saikat Maitra >Assignee: Saikat Maitra >Priority: Minor > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > Upgrade flink module version to 1.9.1 in ignite-extensions > [https://github.com/apache/ignite-extensions] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12517) Upgrade flink module version to 1.9.1 in ignite-extensions
Saikat Maitra created IGNITE-12517: -- Summary: Upgrade flink module version to 1.9.1 in ignite-extensions Key: IGNITE-12517 URL: https://issues.apache.org/jira/browse/IGNITE-12517 Project: Ignite Issue Type: Improvement Components: streaming Reporter: Saikat Maitra Fix For: 2.8 Upgrade flink module version to 1.9.1 in ignite-extensions [https://github.com/apache/ignite-extensions] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-12262) Implement a Pub/Sub Data Streamer
[ https://issues.apache.org/jira/browse/IGNITE-12262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saikat Maitra resolved IGNITE-12262. Resolution: Fixed > Implement a Pub/Sub Data Streamer > - > > Key: IGNITE-12262 > URL: https://issues.apache.org/jira/browse/IGNITE-12262 > Project: Ignite > Issue Type: New Feature > Components: streaming >Affects Versions: 2.7.6 >Reporter: Emmanouil Gkatziouras >Assignee: Emmanouil Gkatziouras >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > A Pub/Sub data streamer would assist GCP users to consume data and feed them > into an Ignite cache. > This data streamer will instantiate a Pub/Sub consumer endpoint, > The user will specify and apply a StreamTransformer to the incoming Exchange > which shall add the result to the data streamer. > The streamer will register as a subscriber and will listen to incoming > messages. > The same subscriber Id shall be used for all nodes. > Only one subscriber/node will process an incoming message, instead of every > subscriber receiving the same message -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-12262) Implement a Pub/Sub Data Streamer
[ https://issues.apache.org/jira/browse/IGNITE-12262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saikat Maitra closed IGNITE-12262. -- > Implement a Pub/Sub Data Streamer > - > > Key: IGNITE-12262 > URL: https://issues.apache.org/jira/browse/IGNITE-12262 > Project: Ignite > Issue Type: New Feature > Components: streaming >Affects Versions: 2.7.6 >Reporter: Emmanouil Gkatziouras >Assignee: Emmanouil Gkatziouras >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > A Pub/Sub data streamer would assist GCP users to consume data and feed them > into an Ignite cache. > This data streamer will instantiate a Pub/Sub consumer endpoint, > The user will specify and apply a StreamTransformer to the incoming Exchange > which shall add the result to the data streamer. > The streamer will register as a subscriber and will listen to incoming > messages. > The same subscriber Id shall be used for all nodes. > Only one subscriber/node will process an incoming message, instead of every > subscriber receiving the same message -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-12356) Migrate Flink module to ignite-extensions
[ https://issues.apache.org/jira/browse/IGNITE-12356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saikat Maitra closed IGNITE-12356. -- > Migrate Flink module to ignite-extensions > - > > Key: IGNITE-12356 > URL: https://issues.apache.org/jira/browse/IGNITE-12356 > Project: Ignite > Issue Type: Sub-task > Components: streaming >Reporter: Saikat Maitra >Assignee: Saikat Maitra >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > Migrate Flink module to ignite-extensions > [https://github.com/apache/ignite-extensions] > Details: > [https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization#IEP-36:Modularization-IndependentIntegrations] > Discussion : > [http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Proposal-for-Ignite-Extensions-as-a-separate-Bahir-module-or-Incubator-project-td44064.html#a44107] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12424) Fix default query timeout behavior for thin JDBC
[ https://issues.apache.org/jira/browse/IGNITE-12424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16997888#comment-16997888 ] Saikat Maitra commented on IGNITE-12424: [~Pavlukhin] Thank you, yes, the tests looks good. Regards, Saikat > Fix default query timeout behavior for thin JDBC > > > Key: IGNITE-12424 > URL: https://issues.apache.org/jira/browse/IGNITE-12424 > Project: Ignite > Issue Type: Bug > Components: sql >Reporter: Ivan Pavlukhin >Assignee: Ivan Pavlukhin >Priority: Blocker > Fix For: 2.8 > > > After IGNITE-7285 there appeared a buggy behavior for thin JDBC driver. > Thin JDBC handles explicit query timeout on a client side. Default query > timeout is tracked on a server side. As a server is not aware of explicit > client timeout it is not possible to override a default timeout with longer > explicit timeout (effectively a query will be cancelled after a default > timeout expiration). > The expected behavior is that an explicit query timeout always overrides a > default one. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12424) Fix default query timeout behavior for thin JDBC
[ https://issues.apache.org/jira/browse/IGNITE-12424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16995239#comment-16995239 ] Saikat Maitra commented on IGNITE-12424: [~Pavlukhin] Thank you for sharing the details. The changes in PR looks good. Regards, Saikat > Fix default query timeout behavior for thin JDBC > > > Key: IGNITE-12424 > URL: https://issues.apache.org/jira/browse/IGNITE-12424 > Project: Ignite > Issue Type: Bug > Components: sql >Reporter: Ivan Pavlukhin >Priority: Blocker > Fix For: 2.8 > > > After IGNITE-7285 there appeared a buggy behavior for thin JDBC driver. > Thin JDBC handles explicit query timeout on a client side. Default query > timeout is tracked on a server side. As a server is not aware of explicit > client timeout it is not possible to override a default timeout with longer > explicit timeout (effectively a query will be cancelled after a default > timeout expiration). > The expected behavior is that an explicit query timeout always overrides a > default one. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12424) Fix default query timeout behavior for thin JDBC
[ https://issues.apache.org/jira/browse/IGNITE-12424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16994156#comment-16994156 ] Saikat Maitra commented on IGNITE-12424: [~Pavlukhin] If we make default query timeout unsupported for thin JDBC client then will server side configured default query timeout value will still be available for Ignite servers? Let's say I started a cluster with server side configured default query timeout of 10s and then using a JDBC client with 30s client side query timeout then will my sql query will timeout in 10s or 30s? IMO, it is still OK to allow query timeout to be different for server and client for the purpose of few bad client queries with long timeout will still be protected by default query timeout at server side. Also, I had another question on SqlFieldsQuery.timeout, Is this also not available for JDBC client users? https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/cache/query/SqlFieldsQuery.java#L72 > Fix default query timeout behavior for thin JDBC > > > Key: IGNITE-12424 > URL: https://issues.apache.org/jira/browse/IGNITE-12424 > Project: Ignite > Issue Type: Bug > Components: sql >Reporter: Ivan Pavlukhin >Priority: Blocker > Fix For: 2.8 > > > After IGNITE-7285 there appeared a buggy behavior for thin JDBC driver. > Thin JDBC handles explicit query timeout on a client side. Default query > timeout is tracked on a server side. As a server is not aware of explicit > client timeout it is not possible to override a default timeout with longer > explicit timeout (effectively a query will be cancelled after a default > timeout expiration). > The expected behavior is that an explicit query timeout always overrides a > default one. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-7285) Add default query timeout
[
https://issues.apache.org/jira/browse/IGNITE-7285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16988366#comment-16988366
]
Saikat Maitra edited comment on IGNITE-7285 at 12/5/19 1:20 AM:
[~Pavlukhin]
I have created this follow up documentation issue:
https://issues.apache.org/jira/browse/IGNITE-12418
I have also updated this issue as RESOLVED and updated Fix Version to 2.8
Regards,
Saikat
was (Author: samaitra):
[~Pavlukhin]
I have created this follow up documentation issue:
**https://issues.apache.org/jira/browse/IGNITE-12418
I have also updated this issue as RESOLVED and updated Fix Version to 2.8
Regards,
Saikat
> Add default query timeout
> -
>
> Key: IGNITE-7285
> URL: https://issues.apache.org/jira/browse/IGNITE-7285
> Project: Ignite
> Issue Type: Improvement
> Components: cache, sql
>Affects Versions: 2.3
>Reporter: Valentin Kulichenko
>Assignee: Saikat Maitra
>Priority: Major
> Labels: sql-stability
> Fix For: 2.8
>
> Time Spent: 10h 40m
> Remaining Estimate: 0h
>
> Currently it's possible to provide timeout only on query level. It would be
> very useful to have default timeout value provided on cache startup. Let's
> add {{CacheConfiguration#defaultQueryTimeout}} configuration property.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-7285) Add default query timeout
[
https://issues.apache.org/jira/browse/IGNITE-7285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16988366#comment-16988366
]
Saikat Maitra commented on IGNITE-7285:
---
[~Pavlukhin]
I have created this follow up documentation issue:
**https://issues.apache.org/jira/browse/IGNITE-12418
I have also updated this issue as RESOLVED and updated Fix Version to 2.8
Regards,
Saikat
> Add default query timeout
> -
>
> Key: IGNITE-7285
> URL: https://issues.apache.org/jira/browse/IGNITE-7285
> Project: Ignite
> Issue Type: Improvement
> Components: cache, sql
>Affects Versions: 2.3
>Reporter: Valentin Kulichenko
>Assignee: Saikat Maitra
>Priority: Major
> Labels: sql-stability
> Fix For: 2.8
>
> Time Spent: 10h 40m
> Remaining Estimate: 0h
>
> Currently it's possible to provide timeout only on query level. It would be
> very useful to have default timeout value provided on cache startup. Let's
> add {{CacheConfiguration#defaultQueryTimeout}} configuration property.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12418) Add documentation for Sql default query timeout
Saikat Maitra created IGNITE-12418: -- Summary: Add documentation for Sql default query timeout Key: IGNITE-12418 URL: https://issues.apache.org/jira/browse/IGNITE-12418 Project: Ignite Issue Type: Task Components: cache, sql Reporter: Saikat Maitra -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-7285) Add default query timeout
[
https://issues.apache.org/jira/browse/IGNITE-7285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16975505#comment-16975505
]
Saikat Maitra commented on IGNITE-7285:
---
[~Pavlukhin] Thank you so much for your help with review and your guidance. I
really appreciate it.
Sorry, I am responding late. I was in In-Memory Computing Summit NA 2019 for
last 2 days and just got back.
I have merged the changes.
Regards,
Saikat
> Add default query timeout
> -
>
> Key: IGNITE-7285
> URL: https://issues.apache.org/jira/browse/IGNITE-7285
> Project: Ignite
> Issue Type: Improvement
> Components: cache, sql
>Affects Versions: 2.3
>Reporter: Valentin Kulichenko
>Assignee: Saikat Maitra
>Priority: Major
> Labels: sql-stability
> Fix For: 2.8
>
> Time Spent: 10h 40m
> Remaining Estimate: 0h
>
> Currently it's possible to provide timeout only on query level. It would be
> very useful to have default timeout value provided on cache startup. Let's
> add {{CacheConfiguration#defaultQueryTimeout}} configuration property.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-7285) Add default query timeout
[
https://issues.apache.org/jira/browse/IGNITE-7285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16972615#comment-16972615
]
Saikat Maitra commented on IGNITE-7285:
---
[~ipavlukhin] The initial build failed as I had 3 unused import statements. I
fixed that issue and ran the Queries2 build.
Your understanding about included change in this PR is correct, this PR add
support for default query timeout for java.
> Add default query timeout
> -
>
> Key: IGNITE-7285
> URL: https://issues.apache.org/jira/browse/IGNITE-7285
> Project: Ignite
> Issue Type: Improvement
> Components: cache, sql
>Affects Versions: 2.3
>Reporter: Valentin Kulichenko
>Assignee: Saikat Maitra
>Priority: Major
> Labels: sql-stability
> Fix For: 2.8
>
> Time Spent: 10.5h
> Remaining Estimate: 0h
>
> Currently it's possible to provide timeout only on query level. It would be
> very useful to have default timeout value provided on cache startup. Let's
> add {{CacheConfiguration#defaultQueryTimeout}} configuration property.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-7285) Add default query timeout
[
https://issues.apache.org/jira/browse/IGNITE-7285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16971236#comment-16971236
]
Saikat Maitra commented on IGNITE-7285:
---
[~Pavlukhin]
The teamcity build has passed :)
Regards,
Saikat
> Add default query timeout
> -
>
> Key: IGNITE-7285
> URL: https://issues.apache.org/jira/browse/IGNITE-7285
> Project: Ignite
> Issue Type: Improvement
> Components: cache, sql
>Affects Versions: 2.3
>Reporter: Valentin Kulichenko
>Assignee: Saikat Maitra
>Priority: Major
> Labels: sql-stability
> Fix For: 2.8
>
> Time Spent: 10.5h
> Remaining Estimate: 0h
>
> Currently it's possible to provide timeout only on query level. It would be
> very useful to have default timeout value provided on cache startup. Let's
> add {{CacheConfiguration#defaultQueryTimeout}} configuration property.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-12356) Migrate Flink module to ignite-extensions
[ https://issues.apache.org/jira/browse/IGNITE-12356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saikat Maitra reassigned IGNITE-12356: -- Assignee: Saikat Maitra > Migrate Flink module to ignite-extensions > - > > Key: IGNITE-12356 > URL: https://issues.apache.org/jira/browse/IGNITE-12356 > Project: Ignite > Issue Type: Sub-task > Components: streaming >Reporter: Saikat Maitra >Assignee: Saikat Maitra >Priority: Major > > Migrate Flink module to ignite-extensions > [https://github.com/apache/ignite-extensions] > Details: > [https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization#IEP-36:Modularization-IndependentIntegrations] > Discussion : > [http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Proposal-for-Ignite-Extensions-as-a-separate-Bahir-module-or-Incubator-project-td44064.html#a44107] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12356) Migrate Flink module to ignite-extensions
[ https://issues.apache.org/jira/browse/IGNITE-12356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saikat Maitra updated IGNITE-12356: --- Summary: Migrate Flink module to ignite-extensions (was: Migrate flink module to ignite-extensions) > Migrate Flink module to ignite-extensions > - > > Key: IGNITE-12356 > URL: https://issues.apache.org/jira/browse/IGNITE-12356 > Project: Ignite > Issue Type: Sub-task > Components: streaming >Reporter: Saikat Maitra >Priority: Major > > Migrate flink module to ignite-extensions > [https://github.com/apache/ignite-extensions] > Details: > [https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization#IEP-36:Modularization-IndependentIntegrations] > Discussion : > [http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Proposal-for-Ignite-Extensions-as-a-separate-Bahir-module-or-Incubator-project-td44064.html#a44107] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12356) Migrate Flink module to ignite-extensions
[ https://issues.apache.org/jira/browse/IGNITE-12356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saikat Maitra updated IGNITE-12356: --- Description: Migrate Flink module to ignite-extensions [https://github.com/apache/ignite-extensions] Details: [https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization#IEP-36:Modularization-IndependentIntegrations] Discussion : [http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Proposal-for-Ignite-Extensions-as-a-separate-Bahir-module-or-Incubator-project-td44064.html#a44107] was: Migrate flink module to ignite-extensions [https://github.com/apache/ignite-extensions] Details: [https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization#IEP-36:Modularization-IndependentIntegrations] Discussion : [http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Proposal-for-Ignite-Extensions-as-a-separate-Bahir-module-or-Incubator-project-td44064.html#a44107] > Migrate Flink module to ignite-extensions > - > > Key: IGNITE-12356 > URL: https://issues.apache.org/jira/browse/IGNITE-12356 > Project: Ignite > Issue Type: Sub-task > Components: streaming >Reporter: Saikat Maitra >Priority: Major > > Migrate Flink module to ignite-extensions > [https://github.com/apache/ignite-extensions] > Details: > [https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization#IEP-36:Modularization-IndependentIntegrations] > Discussion : > [http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Proposal-for-Ignite-Extensions-as-a-separate-Bahir-module-or-Incubator-project-td44064.html#a44107] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12364) Migrate JMS module to ignite-extensions
Saikat Maitra created IGNITE-12364: -- Summary: Migrate JMS module to ignite-extensions Key: IGNITE-12364 URL: https://issues.apache.org/jira/browse/IGNITE-12364 Project: Ignite Issue Type: Sub-task Components: streaming Reporter: Saikat Maitra Migrate JMS module to ignite-extensions [https://github.com/apache/ignite-extensions] Details: [https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization#IEP-36:Modularization-IndependentIntegrations] Discussion : [http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Proposal-for-Ignite-Extensions-as-a-separate-Bahir-module-or-Incubator-project-td44064.html#a44107] -- This message was sent by Atlassian Jira (v8.3.4#803005)
