Re: Null cache names

Hi Igor, The current implementation supports only STRING data type of Redis. In addition, AFAIK, scaling Redis per dataset is normally done via running separate instances of Redis for each dataset. Therefore my choice was storing to the default cache. It looks fine from Redis' perspective, but

Re: Windows XP support

+1 for the discontinuation. Igor, please update C++ readme doc once this feature is implemented. I think it’s still fine to claim that Windows XP, Vista are supported for Ignite Java lib. Pasha, what’s about .NET? Do we still support these ancient Windows versions or the doc has to be altered

Re: Usage of Enums in SQL (Ignite 2.0)

Sergi, That makes total sense. Thanks for adding the feature! — Denis > On Apr 21, 2017, at 12:21 AM, Sergi Vladykin wrote: > > This ticket is about being able to use enums as INT and VARCHAR literals in > SQL like this: > > SELECT name FROM person WHERE job =

Re: Expiration Policy and Page Memory (Ignite 2.0)

Excellent, thanks! Then that documentation page will be left unchanged. — Denis > On Apr 21, 2017, at 8:53 AM, Alexey Goncharuk > wrote: > > Denis, > > Semantically nothing changed for expiry policies, it applies for all local > entries. > > 2017-04-21 2:17

Re: Null cache names

Copying Roman S. in the discussion. — Denis > On Apr 21, 2017, at 4:17 AM, Seliverstov Igor wrote: > > Hi Roman, > > As far as I inderstand you're the author of the Redis protocol > implementation. > > Currently I'm working on a task to prohibit null names for caches

Re: Apache Ignite 2.0 Release

Guys, How close are we for the voting? What exactly are we waiting for to initiate it (H2 release, TC tests, CREATE INDEX)? — Denis > On Apr 19, 2017, at 4:03 PM, Denis Magda wrote: > > Roman, > > If we squeeze your contribution into 2.0 please add a documentation. You

Re: Renaming TcpDiscoverySpi.heartbeatsFrequency to TcpDiscoverySpi.metricsUpdateFrequency

Yakov, Sasha, Are you ready to merge all the changes and close the ticket? As far as I understand, we plan to freeze 2.0 branch the next week. — Denis > On Apr 11, 2017, at 8:59 AM, Denis Magda wrote: > > Yasha, > > I’ve updated the javadoc for

Re: Optimizations on titles and h1

Hi Mauricio, I’ll review your improvements the next week, thanks! — Denis > On Apr 20, 2017, at 8:55 PM, Mauricio Stekl wrote: > > Hi Igniters, > I am attaching a patch with keyword optimizations on several page titles and > H1 across the website. > > I would

Re: Ignite ML, next steps (IGNITE-5029)

Sounds like a good plan to tackle for 1.0 GA release sometime in the future. -- Nikita Ivanov On Fri, Apr 21, 2017 at 9:43 AM, Yury Babak wrote: > Guys, > > Since the first version of Ignite ML module was merged into ignite 2.0 we > want to discuss our next steps. > >

Re: Windows XP support

Agree, let's drop XP support. D. On Fri, Apr 21, 2017 at 8:03 AM, Pavel Tupitsyn wrote: > I don't think we should bother with supporting 16 year old discontinued OS. > Vista support has also ended (just 10 days ago). > > We should put Windows 7 there as the oldest

Re: Page Memory behavior with default memory policy

Thanks, Alexey! Sounds good. On Fri, Apr 21, 2017 at 8:34 AM, Alexey Goncharuk < alexey.goncha...@gmail.com> wrote: > Dmitriy, > > I have implemented expandable page memory and now I need to merge with the > changes that Sergey made to make max be 80% of physical memory. Once TC > passes, I will

Ignite ML, next steps (IGNITE-5029)

Guys, Since the first version of Ignite ML module was merged into ignite 2.0 we want to discuss our next steps. Currently we think about 3 big areas to explore: 1) Regression and clustering algorithms. 2) Deep Learning/Neural Networks stuff. 3) DSL/scripting support. Suggestions/thoughts about

[GitHub] ignite pull request #1859: Replaced AssertionError with IgniteCheckedExcepti...

GitHub user ilantukh opened a pull request: https://github.com/apache/ignite/pull/1859 Replaced AssertionError with IgniteCheckedException when DHT TX adds entry to invalid partition You can merge this pull request into a Git repository by running: $ git pull

Re: Expiration Policy and Page Memory (Ignite 2.0)

Denis, Semantically nothing changed for expiry policies, it applies for all local entries. 2017-04-21 2:17 GMT+03:00 Denis Magda : > Alex G., Igniters, > > What’s a scope of expiration policy applicability in Ignite 2.0? Does it > work for all the entries in the page memory

[GitHub] ignite pull request #1858: IGNITE-4523

GitHub user ascherbakoff opened a pull request: https://github.com/apache/ignite/pull/1858 IGNITE-4523 Allow distributed SQL query execution over explicit set of partitions. You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-5057) .NET: build.ps1 fails for Any CPU config on PowerShell 4.0 and lower

Pavel Tupitsyn created IGNITE-5057: -- Summary: .NET: build.ps1 fails for Any CPU config on PowerShell 4.0 and lower Key: IGNITE-5057 URL: https://issues.apache.org/jira/browse/IGNITE-5057 Project:

[GitHub] ignite pull request #1857: issue fixed: IGNITE-4220

GitHub user rfqu opened a pull request: https://github.com/apache/ignite/pull/1857 issue fixed: IGNITE-4220 new functionality is demonstrated in methods: org.apache.ignite.cassandra.IgnitePersistentStoreTest#loadCacheByStatement

Re: Page Memory behavior with default memory policy

Dmitriy, I have implemented expandable page memory and now I need to merge with the changes that Sergey made to make max be 80% of physical memory. Once TC passes, I will merge the changes, should not take too long, so hopefully, the change will make it to the release. 2017-04-20 20:40 GMT+03:00

[GitHub] ignite pull request #1855: Merge branch 'ignite-2.0' of https://github.com/a...

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

Re: Windows XP support

I don't think we should bother with supporting 16 year old discontinued OS. Vista support has also ended (just 10 days ago). We should put Windows 7 there as the oldest supported version. On Fri, Apr 21, 2017 at 5:59 PM, Igor Sapego wrote: > Hello Igniters, > > So, I've

[GitHub] ignite pull request #1855: Merge branch 'ignite-2.0' of https://github.com/a...

GitHub user ascherbakoff opened a pull request: https://github.com/apache/ignite/pull/1855 Merge branch 'ignite-2.0' of https://github.com/apache/ignite into ignite-4523 Allow distributed SQL query execution over explicit set of partitions. You can merge this pull request into a

Windows XP support

Hello Igniters, So, I've been working on implementation of futures support for C++ [1] and It would be convenient for me to use condition variables on Windows [2] as well as on Linux. The problem here is that they are not supported on Windows XP. So I've checked documentation [3] and found out

[jira] [Created] (IGNITE-5056) Implement communication backpressure control

Yakov Zhdanov created IGNITE-5056: - Summary: Implement communication backpressure control Key: IGNITE-5056 URL: https://issues.apache.org/jira/browse/IGNITE-5056 Project: Ignite Issue Type:

[GitHub] ignite pull request #1846: ignite-4523

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

[jira] [Created] (IGNITE-5055) Optimize GridDhtPartitionTopologyImpl: do not store backup mappings for replicated cache

Konstantin Dudkov created IGNITE-5055: - Summary: Optimize GridDhtPartitionTopologyImpl: do not store backup mappings for replicated cache Key: IGNITE-5055 URL:

[GitHub] ignite pull request #1854: IGNITE-3521 IGFS: Remove "max space" notion

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/1854 IGNITE-3521 IGFS: Remove "max space" notion You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-3521

[jira] [Created] (IGNITE-5054) Support SQL schema sharing between different caches

Vladimir Ozerov created IGNITE-5054: --- Summary: Support SQL schema sharing between different caches Key: IGNITE-5054 URL: https://issues.apache.org/jira/browse/IGNITE-5054 Project: Ignite

[GitHub] ignite pull request #1853: GridCachePartitionedTxSalvageSelfTest fix (remove...

Github user kdudkov closed the pull request at: https://github.com/apache/ignite/pull/1853 --- 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 #1807: GridCacheContext preloader() npe fix

Github user kdudkov closed the pull request at: https://github.com/apache/ignite/pull/1807 --- 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-5053) Add missing features to H2 parser for CREATE/DROP TABLE

Vladimir Ozerov created IGNITE-5053: --- Summary: Add missing features to H2 parser for CREATE/DROP TABLE Key: IGNITE-5053 URL: https://issues.apache.org/jira/browse/IGNITE-5053 Project: Ignite

[GitHub] ignite pull request #1853: GridCachePartitionedTxSalvageSelfTest fix (remove...

GitHub user kdudkov opened a pull request: https://github.com/apache/ignite/pull/1853 GridCachePartitionedTxSalvageSelfTest fix (remove unnecessary topolog… remove unnecessary topology change wait You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #1753: IGNITE-4898: Added ODBC installers paths to READM...

Github user isapego closed the pull request at: https://github.com/apache/ignite/pull/1753 --- 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 #1852: IGNITE-5030

GitHub user daradurvs opened a pull request: https://github.com/apache/ignite/pull/1852 IGNITE-5030 You can merge this pull request into a Git repository by running: $ git pull https://github.com/daradurvs/ignite ignite-5030 Alternatively you can review and apply these

[GitHub] ignite pull request #1839: IgniteCacheAtomicProtocolTest fix

Github user kdudkov closed the pull request at: https://github.com/apache/ignite/pull/1839 --- 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 #1850: Ignite 4799

GitHub user abeliak opened a pull request: https://github.com/apache/ignite/pull/1850 Ignite 4799 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4799 Alternatively you can review and apply these

[GitHub] ignite pull request #1849: Ignite 4799

Github user abeliak closed the pull request at: https://github.com/apache/ignite/pull/1849 --- 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-5051) DDL: Make sure schema survives cluster restart if persistence is enabled

Vladimir Ozerov created IGNITE-5051: --- Summary: DDL: Make sure schema survives cluster restart if persistence is enabled Key: IGNITE-5051 URL: https://issues.apache.org/jira/browse/IGNITE-5051

[GitHub] ignite pull request #1845: IGNITE-4997

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

Re: "Apache Ignite University”

great idea пт, 21 апр. 2017 г. в 2:20, Denis Magda : > Sounds good to me. > > — > Denis > > > On Apr 20, 2017, at 1:35 PM, Tom Diederich > wrote: > > > > I’d also like to propose an enhancement to the community that I believe > would be helpful to

[jira] [Created] (IGNITE-5050) .NET: IIgnite.GetMemoryMetrics

Pavel Tupitsyn created IGNITE-5050: -- Summary: .NET: IIgnite.GetMemoryMetrics Key: IGNITE-5050 URL: https://issues.apache.org/jira/browse/IGNITE-5050 Project: Ignite Issue Type: New Feature

Re: need new ticket

thank you чт, 20 апр. 2017 г. в 20:39, Denis Magda : > Aleksey, > > Here are more tickets you can start working on: > https://issues.apache.org/jira/browse/IGNITE-2190 < > https://issues.apache.org/jira/browse/IGNITE-2190> > https://issues.apache.org/jira/browse/IGNITE-4181 <

Using long for configure network timeouts

Now in ignite configurations in many network related parameters (for example: IgniteConfiguration.netTimeout, TcpDiscoverySpi.socketTimeout, TcpDiscoverySpi.ackTimeout) used long. But network socket using int for socket timeout, so we do simple "(int)timeout" type casting and if timeout value >

[jira] [Created] (IGNITE-5049) Thread blocked on Object.wait() within IgniteUtils.forName

Cameron Braid created IGNITE-5049: - Summary: Thread blocked on Object.wait() within IgniteUtils.forName Key: IGNITE-5049 URL: https://issues.apache.org/jira/browse/IGNITE-5049 Project: Ignite

question: IgniteCache - lock an entry by a key in ATOMIC mode

Hi Igniters! Does IgniteCache provide any tools to set a lock to a key in ATOMIC atomicity mode? -- Best Regards, Vyacheslav

Re: SQL: Index hints

Exactly, this syntax was taken from MySQL. Sergi 2017-04-21 9:58 GMT+03:00 Denis Magda : > If multiple indexes are listed then H2 will pick only one of them like > MySql does, right? > > Denis > > On Thursday, April 20, 2017, Sergi Vladykin >

[jira] [Created] (IGNITE-5048) NPE in WebSessionFilter

Cameron Braid created IGNITE-5048: - Summary: NPE in WebSessionFilter Key: IGNITE-5048 URL: https://issues.apache.org/jira/browse/IGNITE-5048 Project: Ignite Issue Type: Bug

Re: SQL: Index hints

No, it must be USE INDEX without underscore. Also mention that multiple indexes can be listed. http://h2database.com/html/grammar.html#table_expression Sergi 2017-04-21 4:25 GMT+03:00 Denis Magda : > Sergi, I’ve documented this feature for 2.0. Please confirm that the text