Web Console updated

Hello everyone. I would like to announce that we updated Web Console ( https://console.gridgain.com) to new version. What's new: 1. Added a lot of properties to cluster and caches configuration wizards. 2. Redesigned Queries screen: spitted SQL and Scan queries into different blocks. 3. Improved

[jira] [Created] (IGNITE-4472) Web Console: Implement usage tracing

Dmitriy Shabalin created IGNITE-4472: Summary: Web Console: Implement usage tracing Key: IGNITE-4472 URL: https://issues.apache.org/jira/browse/IGNITE-4472 Project: Ignite Issue Type:

Re: Capacity Planning - Calculating Memory Usage

Hi Val, the understanding is simple. When you enables the single index on entry class you get "First index overhead" per entry. When you enables two indices on entry class you get "First index overhead" + "Next index overhead" per entry. With three indices you get "First index overhead" + 2 *

Re: Google Summer Of Code 2017

I can take over DataFrames integration as I already did some investigation in this area. Spark also has GraphX and GraphFrames for graph processing, we can think about integration with them as well. Machine learning also sounds very interesting. -Val On Wed, Dec 21, 2016 at 4:22 PM, Dmitriy

Re: Google Summer Of Code 2017

I can also do mentoring for any of the listed features. On Wed, Dec 21, 2016 at 2:50 PM, Denis Magda wrote: > Alex, thanks for bringing this out! > > This is a great opportunity for our community to find talented students > who are capable of adding new features to Ignite. I

Re: Google Summer Of Code 2017

Alex, thanks for bringing this out! This is a great opportunity for our community to find talented students who are capable of adding new features to Ignite. I can take care of all the paperwork. The features list won’t be a big deal as well. But we need mentors who will voluntarily dedicate

Re: Ignite Shutdown Hook

Please share the thread dumps with us. — Denis > On Dec 21, 2016, at 6:35 AM, hemanta wrote: > > Thank you for your reply. It is stuck at Ignite. > If in last line of public static void main() I add code to stop Ignite then > everything works fine. But I have so many

Re: Hello

Alexander, Thanks for the details. Now I see what you’re talking about. Agree, it makes sense to support this. Could you initiate a dedicated discussion on the dev list proposing this to the community and sharing design/implementations details if any? This discussion named “Hello” is not the

Re: Diagram for RDBMS Schema Import with Web Console

Thanks guys, I’ve sent an updated version to the designer. — Denis > On Dec 20, 2016, at 7:21 PM, Alexey Kuznetsov wrote: > > Denis, > > I attached slightly corrected diagram: > https://issues.apache.org/jira/secure/attachment/12844178/SchemaImport-2.png > > On Wed,

[jira] [Created] (IGNITE-4471) ODBC: Can not retrieve table metadata.

Igor Sapego created IGNITE-4471: --- Summary: ODBC: Can not retrieve table metadata. Key: IGNITE-4471 URL: https://issues.apache.org/jira/browse/IGNITE-4471 Project: Ignite Issue Type: Bug

Re: Why our functional interfaces are serializable?

I would agree only for internal Ignite classes. If we touch public classes, we risk breaking backward compatibility. On Wed, Dec 21, 2016 at 1:21 AM, Sergi Vladykin wrote: > Agree, but we use some of them on public API for distributed operations and > they have to be

Re: Ignite Shutdown Hook

Thank you for your reply. It is stuck at Ignite. If in last line of public static void main() I add code to stop Ignite then everything works fine. But I have so many stand alone classes (public static void main) that run as a part of upgrade that I can not add Ignition.stop() in all of them. So,

[GitHub] ignite pull request #1224: Ignite-2795

Github user AMashenkov closed the pull request at: https://github.com/apache/ignite/pull/1224 --- 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 feature

[GitHub] ignite pull request #976: Ignite 2560 2

Github user AMashenkov closed the pull request at: https://github.com/apache/ignite/pull/976 --- 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 feature is

[GitHub] ignite pull request #980: Ignite 3597

Github user AMashenkov closed the pull request at: https://github.com/apache/ignite/pull/980 --- 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 feature is

[GitHub] ignite pull request #1016: IGNITE-2881 : SPI queries not working

Github user AMashenkov closed the pull request at: https://github.com/apache/ignite/pull/1016 --- 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 feature

[GitHub] ignite pull request #1031: IGNITE-2833 : GridCacheTtlManager pending queue r...

Github user AMashenkov closed the pull request at: https://github.com/apache/ignite/pull/1031 --- 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 feature

[GitHub] ignite pull request #1370: IGNITE-4142: Assertion in ClientImpl.updateMetric...

Github user AMashenkov closed the pull request at: https://github.com/apache/ignite/pull/1370 --- 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 feature

[GitHub] ignite pull request #1372: IGNITE-4142: Assertion in ClientImpl.updateMetric...

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/1372 IGNITE-4142: Assertion in ClientImpl.updateMetrics() You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4142-1

[GitHub] ignite pull request #1371: IGNITE-2793 Added support for byte arrays to ODBC

GitHub user skalashnikov opened a pull request: https://github.com/apache/ignite/pull/1371 IGNITE-2793 Added support for byte arrays to ODBC You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2793

[GitHub] ignite pull request #1298: IGNITE-3886 .NET: Build script

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1298 --- 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 feature is

[jira] [Created] (IGNITE-4470) ODBC: Add support for logger configuration

Sergey Kalashnikov created IGNITE-4470: -- Summary: ODBC: Add support for logger configuration Key: IGNITE-4470 URL: https://issues.apache.org/jira/browse/IGNITE-4470 Project: Ignite

[jira] [Created] (IGNITE-4469) Hadoop: better defaults to memory page size and message size.

Vladimir Ozerov created IGNITE-4469: --- Summary: Hadoop: better defaults to memory page size and message size. Key: IGNITE-4469 URL: https://issues.apache.org/jira/browse/IGNITE-4469 Project: Ignite

Re: Hello

Denis, Thanks for your reply. My question is not about data locality. As far as I know nodes are connected in a ring. For example if i have 6 nodes, with names A, B, C, D, E, and F they can connect in ring any possible way: A-B-C-D-E-F-A, or A-F-B-E-C-D-A, etc. And if some node falls out of

Re: Why our functional interfaces are serializable?

Agree, but we use some of them on public API for distributed operations and they have to be Serializable. Sergi 2016-12-21 12:06 GMT+03:00 Vladimir Ozerov : > Folks, > > We have more than 1500 classes (mostly anonymous) implementing functional > interfaces. Most common are

Why our functional interfaces are serializable?

Folks, We have more than 1500 classes (mostly anonymous) implementing functional interfaces. Most common are *IgnitePredicate*, *IgniteClosure*, etc.. Question: why these interfaces are Serializable? A lot of classes which implement these interfaces are never meant to be serialized. I propose

[jira] [Created] (IGNITE-4468) RoundRobinLoadBalancingSpi‘s documentation and Javadoc description incorrectly

Yujue Li created IGNITE-4468: Summary: RoundRobinLoadBalancingSpi‘s documentation and Javadoc description incorrectly Key: IGNITE-4468 URL: https://issues.apache.org/jira/browse/IGNITE-4468 Project: