Re: Optional modules without README and apache license

Igniters, it's really Important! It's impossible to release 1.5.0 without README.txt files inside modules. Please create them at modules made by you or/and at modules you reviewed. On Wed, Nov 25, 2015 at 5:50 PM, Vasilisa Sidorova wrote: > Dear Igniters, > we have

Binary "type ID" on public API.

Folks, We have several public methods which operate on "type ID" concept: - IgniteBinary.typeId(String typeName) - IgniteBinary.metadata(int typeId) - BinaryType.typeId() These methods came from initial GridGain portables implementation where it is possbile that there is no type

Re: Binary "type ID" on public API.

Vladimir, Can you describe the new APIs to get this information in Ignite? Thanks, D. On Thu, Nov 26, 2015 at 12:04 PM, Vladimir Ozerov wrote: > Folks, > > We have several public methods which operate on "type ID" concept: > >- IgniteBinary.typeId(String typeName) >

Re: Binary "type ID" on public API.

On Thu, Nov 26, 2015 at 12:15 PM, Vladimir Ozerov wrote: > Sure, > >1. IgniteBinary.typeId(String typeName) -> no replacement, we simply do >not need it. >2. IgniteBinary.metadata(int typeId) -> use IgniteBinary.metadata(String >typeName) instead >3.

Rename IgniteBinary to IgniteBinaries?

Folks, One more minor question about API. We use plural form when possbile in top-level API. E.g.: - IgniteTransactions transactions() - IgniteEvents events() Shouldn't we rename our API to IgniteBinar*ies* binar*ies*()? Vladimir.

[jira] [Created] (IGNITE-2008) Abandoned locks are not released when nodes leave the grid

Noam Liran created IGNITE-2008: -- Summary: Abandoned locks are not released when nodes leave the grid Key: IGNITE-2008 URL: https://issues.apache.org/jira/browse/IGNITE-2008 Project: Ignite

Re: Binary "type ID" on public API.

Yes, because I cannot imagine a use case when user will need type ID (except of ID mapper). This appears to be implementation detail. On Thu, Nov 26, 2015 at 12:17 PM, Dmitriy Setrakyan wrote: > On Thu, Nov 26, 2015 at 12:15 PM, Vladimir Ozerov >

Re: Rename IgniteBinary to IgniteBinaries?

I prefer IgniteBinary. The plural form sounds like a release archive. D. On Thu, Nov 26, 2015 at 12:20 PM, Vladimir Ozerov wrote: > Folks, > > One more minor question about API. We use plural form when possbile in > top-level API. E.g.: > >- IgniteTransactions

Re: Rename IgniteBinary to IgniteBinaries?

Imho, *IgniteBinaryProto *is also an option. Vladimir. On Thu, Nov 26, 2015 at 12:51 PM, Dmitriy Setrakyan wrote: > I prefer IgniteBinary. The plural form sounds like a release archive. > > D. > > On Thu, Nov 26, 2015 at 12:20 PM, Vladimir Ozerov

Re: Binary "type ID" on public API.

On Thu, Nov 26, 2015 at 12:22 PM, Vladimir Ozerov wrote: > Yes, because I cannot imagine a use case when user will need type ID > (except of ID mapper). This appears to be implementation detail. > I actually would prefer a reverse approach. Instead of removing typeId, I

The ability to execute cache modifications during recovery.

Hi Folks! Assume case, when some cache partitions with data are lost from the grid, and thus EVT_CACHE_REBALANCE_PART_DATA_LOST event happen. Do we need the ability to execute cache modifications somehow, maybe like recover(Map<,> missingKeysAndValues) as part of GridDhtPartitionTopology API?

Re: Igfs PURGE events: do we need them?

Cos, I agree with Ivan that there should be no architectural problems with our "trash" concept. Essentialy, when delete is performed in DUAL mode, we do two things: 1) Propagate removal to secondary file system; 2) Logically move affected path to "trash" in IGFS. Once item is in trash, no one

[GitHub] ignite pull request: ignite-1544 Make sure objects number stored i...

Github user agura closed the pull request at: https://github.com/apache/ignite/pull/252 --- 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: ignite-1992 CacheStopAndDestroySelfTest.testL...

Github user agura closed the pull request at: https://github.com/apache/ignite/pull/261 --- 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: ignite-2005 Java client tests fixed

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

ignite is not listed among Apache projects

Anyone knows how do we get a mention on this page? http://projects-old.apache.org/indexes/quick.html D.

[jira] [Created] (IGNITE-2009) Cached prepared SQL statement causes IgniteKernal leak.

Vladimir Ozerov created IGNITE-2009: --- Summary: Cached prepared SQL statement causes IgniteKernal leak. Key: IGNITE-2009 URL: https://issues.apache.org/jira/browse/IGNITE-2009 Project: Ignite

Re: [jira] [Created] (IGNITE-2009) Cached prepared SQL statement causes IgniteKernal leak.

Hi, Why then thread couldn't clear this threadLocal query at the end of the task execution? On Thu, Nov 26, 2015 at 5:06 PM, Vladimir Ozerov (JIRA) wrote: > Vladimir Ozerov created IGNITE-2009: > --- > > Summary: Cached prepared

Re: [jira] [Created] (IGNITE-2009) Cached prepared SQL statement causes IgniteKernal leak.

As I understand, the main goal of thes thread-local - to allow re-use query *between *task execution. On Thu, Nov 26, 2015 at 5:27 PM, Vladimir Ershov wrote: > Hi, > Why then thread couldn't clear this threadLocal query at the end of the > task execution? > > On Thu, Nov

[GitHub] ignite pull request: ignite-2010 IgniteCacheCrossCacheTxFailoverTe...

GitHub user agura opened a pull request: https://github.com/apache/ignite/pull/268 ignite-2010 IgniteCacheCrossCacheTxFailoverTest.testCrossCachePessimisticTxFailoverOffheapSwap test fixed You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-2011) .Net: Servi

Pavel Tupitsyn created IGNITE-2011: --- Summary: .Net: Servi Key: IGNITE-2011 URL: https://issues.apache.org/jira/browse/IGNITE-2011 Project: Ignite Issue Type: Bug Components:

Re: ignite is not listed among Apache projects

On Thu, Nov 26, 2015 at 1:22 PM, Dmitriy Setrakyan wrote: > Anyone knows how do we get a mention on this page? > http://projects-old.apache.org/indexes/quick.html > We need a DOAP file (Description Of A Project) for Ignite, and once we have that, we get in touch with

[jira] [Created] (IGNITE-2012) Add support for ConcurrentLinkedQueue type in .NET/C++

Alexey Goncharuk created IGNITE-2012: Summary: Add support for ConcurrentLinkedQueue type in .NET/C++ Key: IGNITE-2012 URL: https://issues.apache.org/jira/browse/IGNITE-2012 Project: Ignite

[jira] [Created] (IGNITE-2013) [Test failed] GridCacheEvictionLockUnlockSelfTest.testPartitioned test fails sometimes

Andrey Gura created IGNITE-2013: --- Summary: [Test failed] GridCacheEvictionLockUnlockSelfTest.testPartitioned test fails sometimes Key: IGNITE-2013 URL: https://issues.apache.org/jira/browse/IGNITE-2013

[GitHub] ignite pull request: ignite-2013 GridCacheEvictionLockUnlockSelfTe...

GitHub user agura opened a pull request: https://github.com/apache/ignite/pull/269 ignite-2013 GridCacheEvictionLockUnlockSelfTest.testPartitioned test fixed You can merge this pull request into a Git repository by running: $ git pull https://github.com/agura/incubator-ignite