[GitHub] incubator-zeppelin pull request: ZEPPELIN-596 Use default marshall...

2016-01-12 Thread c0s
Github user c0s commented on the pull request: https://github.com/apache/incubator-zeppelin/pull/624#issuecomment-171179270 Moon, could you merge it then? Looks like I don't have the permissions. --- If your project is set up for it, you can reply to this email and have your

[GitHub] incubator-zeppelin pull request: ZEPPELIN-596 Use default marshall...

2016-01-12 Thread c0s
Github user c0s commented on the pull request: https://github.com/apache/incubator-zeppelin/pull/624#issuecomment-171051605 Thanks, this is a way cleaner fix that the one I did in ZEPPELIN-545 - these Spring configs are in my blind spot, unfortunately. +1 Looking through

[GitHub] incubator-zeppelin pull request: ZEPPELIN-545. Include Ignite 1.5....

2016-01-04 Thread c0s
Github user c0s commented on the pull request: https://github.com/apache/incubator-zeppelin/pull/584#issuecomment-168900525 Looks like it is good to go. There might be a bigger issue with different default marshallers for different node modes, which I am discussing on dev@ignite

[GitHub] incubator-zeppelin pull request: ZEPPELIN-545. Include Ignite 1.5....

2016-01-04 Thread c0s
Github user c0s closed the pull request at: https://github.com/apache/incubator-zeppelin/pull/584 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the

[GitHub] incubator-zeppelin pull request: ZEPPELIN-545. Include Ignite 1.5....

2016-01-04 Thread c0s
GitHub user c0s reopened a pull request: https://github.com/apache/incubator-zeppelin/pull/584 ZEPPELIN-545. Include Ignite 1.5.0.final into next release of Zeppelin Ready for the review. The latest Ignite release will be published in the next day or so You can merge this pull

[GitHub] incubator-zeppelin pull request: ZEPPELIN-545. Include Ignite 1.5....

2016-01-04 Thread c0s
Github user c0s commented on the pull request: https://github.com/apache/incubator-zeppelin/pull/584#issuecomment-168894741 Looks like CI didn't pick up correct commit. Restarting once again. --- If your project is set up for it, you can reply to this email and have your reply a

[GitHub] incubator-zeppelin pull request: ZEPPELIN-545. Include Ignite 1.5....

2016-01-04 Thread c0s
GitHub user c0s reopened a pull request: https://github.com/apache/incubator-zeppelin/pull/584 ZEPPELIN-545. Include Ignite 1.5.0.final into next release of Zeppelin Ready for the review. The latest Ignite release will be published in the next day or so You can merge this pull

[GitHub] incubator-zeppelin pull request: ZEPPELIN-545. Include Ignite 1.5....

2016-01-04 Thread c0s
Github user c0s closed the pull request at: https://github.com/apache/incubator-zeppelin/pull/584 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the

[GitHub] incubator-zeppelin pull request: ZEPPELIN-545. Include Ignite 1.5....

2016-01-04 Thread c0s
Github user c0s commented on the pull request: https://github.com/apache/incubator-zeppelin/pull/584#issuecomment-168872438 Looks like it is cause by a missing configuration piece... ```Caused by: class org.apache.ignite.spi.IgniteSpiException: Local node's marshaller differs

[GitHub] incubator-zeppelin pull request: ZEPPELIN-545. Include Ignite 1.5....

2016-01-04 Thread c0s
Github user c0s closed the pull request at: https://github.com/apache/incubator-zeppelin/pull/584 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the

[GitHub] incubator-zeppelin pull request: ZEPPELIN-545. Include Ignite 1.5....

2016-01-04 Thread c0s
GitHub user c0s reopened a pull request: https://github.com/apache/incubator-zeppelin/pull/584 ZEPPELIN-545. Include Ignite 1.5.0.final into next release of Zeppelin Ready for the review. The latest Ignite release will be published in the next day or so You can merge this pull

[GitHub] incubator-zeppelin pull request: ZEPPELIN-545. Include Ignite 1.5....

2016-01-04 Thread c0s
Github user c0s commented on the pull request: https://github.com/apache/incubator-zeppelin/pull/584#issuecomment-168856099 Re-opening to trigger the CI --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project

[GitHub] incubator-zeppelin pull request: ZEPPELIN-545. Include Ignite 1.5....

2016-01-04 Thread c0s
Github user c0s commented on the pull request: https://github.com/apache/incubator-zeppelin/pull/584#issuecomment-168778042 The 1.5.0.final release has been published and this PR should be able to clear the CI. Thanks! --- If your project is set up for it, you can reply to this

[GitHub] incubator-zeppelin pull request: ZEPPELIN-545. Include Ignite 1.5....

2015-12-30 Thread c0s
Github user c0s commented on the pull request: https://github.com/apache/incubator-zeppelin/pull/584#issuecomment-168113568 That's what I've said - the bits will be available in a day or two once the vote is over. Don't pull this one in yet. I have validated it to w

[GitHub] incubator-zeppelin pull request: ZEPPELIN-545. Include Ignite 1.5....

2015-12-30 Thread c0s
GitHub user c0s opened a pull request: https://github.com/apache/incubator-zeppelin/pull/584 ZEPPELIN-545. Include Ignite 1.5.0.final into next release of Zeppelin Ready for the review. The latest Ignite release will be published in the next day or so You can merge this pull

[GitHub] incubator-zeppelin pull request: ZEPPELIN-404 Certain project depe...

2015-11-07 Thread c0s
Github user c0s commented on the pull request: https://github.com/apache/incubator-zeppelin/pull/404#issuecomment-154768947 Thanks for the explanation! Good to go with the fix +! --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as