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
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
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)
>
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.
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.
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
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
>
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
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
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
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?
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 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 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 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
Anyone knows how do we get a mention on this page?
http://projects-old.apache.org/indexes/quick.html
D.
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
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
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 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
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:
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
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
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 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
25 matches
Mail list logo