Fwd: When will Ignite support cross-cache SQL joins?

[Valentin Kulichenko]

Folks,

Are ad-hoc queries already available in master?

-Val

-- Forwarded message --
From: ght230 
Date: Mon, Feb 15, 2016 at 6:09 AM
Subject: When will Ignite support cross-cache SQL joins?
To: u...@ignite.apache.org


I had learned that in version 1.5, Ignite will support cross-cache SQL joins
without setting specified cache mode and AffinityKey.Is it right?

Today, using gridgain-community-fabric-1.5.6, I have tried cross-cache SQL
joins with 3 tables(all tables are Partitioned Mode and AffinityKey have
been setted), but the result is not correct.

I want to know whether there is plan to support cross-cache SQL joins
without setting specified cache mode and AffinityKey.



--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/When-will-Ignite-support-cross-cache-SQL-joins-tp3005.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: NoopSwapSpaceSpi and dynamically started caches

[Konstantin Margorin]

Probably I can handle this ticket, but I want to clarify one thing.

Suppose dynamic cache with enabled swap should be partitioned between two
nodes with backups=1. First node started with FileSwapSpaceSpi, second with
NoopSwapSpaceSpi.

How cache should start in this case?


On Mon, Feb 15, 2016 at 3:45 PM, Artem Shutak  wrote:

> I've created a newbie issue for that:
> https://issues.apache.org/jira/browse/IGNITE-2650.
>
> -- Artem --
>
> On Wed, Feb 10, 2016 at 8:53 PM, Dmitriy Setrakyan 
> wrote:
>
> > Artem,
> >
> > I like the option with proper exception in case if a dynamic cache is
> > started with swap enabled while there was no swap configured in Ignite.
> >
> > Starting FileSwapSpaceSpi all the time is not a good option as user will
> > face the same problem when trying to change to a different SPI.
> >
> > D.
> >
> > On Wed, Feb 10, 2016 at 4:39 AM, Artem Shutak 
> > wrote:
> >
> > > Igniters,
> > >
> > > I've noticed an issue with NoopSwapSpaceSpi and dynamically started
> > cashes.
> > >
> > > We have the following logic on node start:
> > >
> > > if (cfg.getSwapSpaceSpi() == null) {
> > > boolean needSwap = false;
> > >
> > > if (cfg.getCacheConfiguration() != null &&
> > > !Boolean.TRUE.equals(cfg.isClientMode())) {
> > > for (CacheConfiguration c :
> > > cfg.getCacheConfiguration()) {
> > > if (c.isSwapEnabled()) {
> > > needSwap = true;
> > >
> > > break;
> > > }
> > > }
> > > }
> > >
> > > cfg.setSwapSpaceSpi(needSwap ? new FileSwapSpaceSpi() :
> > new
> > > NoopSwapSpaceSpi());
> > > }
> > >
> > > According to the code above, if IgniteConfiguration doesn't contain
> cache
> > > configurations or all configured caches configured without swap, then
> > node
> > > will be started with NoopSwapSpaceSpi.
> > > As a result in this case, when we start dynamic cache with enabled swap
> > > then actually swap doesn't work.
> > >
> > > There is simple workaround - user have to explicitly set
> FileSwapSpaceSpi
> > > to configuration. But now, there is no any warning or exception.
> > >
> > > What we can do:
> > >
> > >1. Throw an exception on dynamic cache start (with swap enabled)
> > >if NoopSwapSpaceSpi is configured.
> > >2. Actually, I don't see why we need NoopSwapSpaceSpi at all. I
> think
> > we
> > >should configure FileSwapSpaceSpi always if user doesn't provide any
> > >SwapSpaceSpi explicitly.
> > >
> > > Thoughts?
> > >
> > > Thanks,
> > > -- Artem --
> > >
> >
>

Re: Grid behavior at key deserialization failure during rebalancing

[Dmitriy Setrakyan]

Anton,

I am not sure why we would deserialize on the server side with Binary
Marshaller. The data should remain in binary form. Do you know if we have a
test for it?

Thanks,
D.

On Mon, Feb 15, 2016 at 1:20 AM, Anton Vinogradov 
wrote:

> Dmitriy,
>
> Key can be undeserializable during rebalancing because of many reasons.
> For example,
> 1) It was serialized with errors
> 2) Deserialization cause error
> 3) It based on classes unavailable at node trying to deserialize it
> Third is the most possible case.
>
>
> On Sat, Feb 13, 2016 at 3:44 AM, Dmitriy Setrakyan 
> wrote:
>
> > Anton,
> >
> > I am not sure I fully grok the use case. Can you please explain why a key
> > can be broken?
> >
> > D.
> >
> > On Fri, Feb 12, 2016 at 7:11 AM, Anton Vinogradov <
> > avinogra...@gridgain.com>
> > wrote:
> >
> > > Igniters,
> > >
> > > At this moment key deserialization failure during rebalancing cause
> > strange
> > > situation:
> > >
> > > Rebalancing from node sent supply message with broken key will be
> > cancelled
> > > at current topology.
> > > All upcoming supply messages from this node will be be ignored, no new
> > > demand messages to this node will be sent.
> > >
> > > But when topology will be changed again, node with broken key will take
> > > path at rebalancing again, untill key deserialization failure happen
> ...
> > > again.
> > >
> > > Do we need to improve this situation, and if we have to how should be
> > > handled case with key deserialization failure?
> > >
> > > I see some ways:
> > > 1) We can inform user about data loss because of deserialization
> > problems,
> > > but keep current rebalancing strategy
> > > 2) We can continue rebalancing from this node, but ignore messages with
> > > broken keys. And inform user about data loss.
> > > 3) We can pause rebalancing untill deserialization will be fixed
> somehow,
> > > for example by shutdowning demanding or supplying node.
> > >
> > > Thoughts?
> > >
> >
>

[GitHub] ignite pull request: IGNITE-2627: Removed OdbcNioParser. Using Gri...

[isapego]

GitHub user isapego opened a pull request:

https://github.com/apache/ignite/pull/485

IGNITE-2627: Removed OdbcNioParser. Using GridBufferedParser for message 
separation.

Message parsing moved to OdbcNioListener.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/isapego/ignite ignite-2627

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/485.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #485


commit feb8350d0ae40a6e98cf4b911ab16c85ed0f659a
Author: isapego 
Date:   2016-02-15T18:23:31Z

IGNITE-2627: Removed OdbcNioParser. Using GridBufferedParser for message
separation. Message parsing moved to OdbcNioListener.

commit c16549cd8866929b7974c18c867954a4c8c2504a
Author: isapego 
Date:   2016-02-15T19:26:09Z

Merge branch 'ignite-1786' into ignite-2627




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request: Ignite 2521 TMP (not for merge)

[ashutakGG]

GitHub user ashutakGG opened a pull request:

https://github.com/apache/ignite/pull/484

Ignite 2521 TMP (not for merge)

TMP PR

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ashutakGG/incubator-ignite 
ignite-2521-tmp-good-set

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/484.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #484


commit cebd5e5d8a985efa79cf75e070a580ba24b7b641
Author: ashutak 
Date:   2016-02-01T15:42:33Z

ignite-2521: Test framework. GridTestSuite

commit b919cc70bcb1cb4673968e2562faf1aa8c080773
Author: ashutak 
Date:   2016-02-01T15:49:02Z

ignite-2521: Test framework. Add new suite.

commit 972bec815cb4d60c9ae80d19401eecc3efe70f70
Author: ashutak 
Date:   2016-02-01T19:39:59Z

ignite-2521: Test framework. PoC

commit bcb992812433de56c025f3da25728bd5e7ffe19b
Author: ashutak 
Date:   2016-02-02T09:41:09Z

ignite-2521: suffix

commit 624937ddbc2e5b4de0eb44fa89f36e6c63199d83
Author: ashutak 
Date:   2016-02-02T10:40:53Z

ignite-2191: mute tests

commit fb8328b31fe2d120147a54bdc26908f4fd114286
Author: ashutak 
Date:   2016-02-02T12:34:17Z

ignite-2191: added configuration generator interfaces

commit 70eabd91da4f851af0957eac4448596f62a4b647
Author: ashutak 
Date:   2016-02-02T12:44:33Z

ignite-2191: move cache destroy

commit c4e8e16b51e392c09996c8407b1e587fa1d6098d
Author: ashutak 
Date:   2016-02-02T12:57:38Z

ignite-2191: fix cache start

commit 4a5dbb35882ab43d56c0ae5078dceccd230e804b
Author: ashutak 
Date:   2016-02-02T17:00:08Z

ignite-2191: implement StateIterator and test suite

commit 570aae3c0e925d01bcb65918a44467c94dfb44ef
Author: ashutak 
Date:   2016-02-03T09:17:45Z

ignite-2191: reconfigure suite and add debug info (count of nodes)

commit af5541d963aa4617c739bd02e4e7c157cfb9a730
Author: ashutak 
Date:   2016-02-03T10:43:59Z

ignite-2521: self-review

commit a48878e023d0b9d1c5021aa851f38254de0cac65
Author: ashutak 
Date:   2016-02-03T10:46:39Z

ignite-2521: rename TestsConfiguration

commit 072b517f6f7e87ef36c0212cc63e2427af67ebb8
Author: ashutak 
Date:   2016-02-03T11:18:04Z

ignite-2465: Variants API

commit 713bf8192978c5cb13f176c7db3cca135bdd4106
Author: ashutak 
Date:   2016-02-03T12:00:40Z

ignite-2465: fix node starting and variants

commit f7c185f2159dc7d4537a2daf2e447eedf6f0ecc8
Author: ashutak 
Date:   2016-02-03T12:21:13Z

ignite-2465: modes from configs

commit ba819c3bfcf70c7252c036de1e751085f0cbd37e
Author: ashutak 
Date:   2016-02-03T13:09:24Z

ignite-2465: ConfigurationParameter

commit d9e889100f7856d188ef6b4b6b9e6253dafbdbc7
Author: ashutak 
Date:   2016-02-03T16:00:40Z

ignite-2521: cache configuration from old

commit 5bf2fa24035c89014f2213d9607db5c36683493b
Author: ashutak 
Date:   2016-02-04T11:21:55Z

ignite-2521: rename NewCacheFullApiSelfTest and cfg manipulations

commit fc7c0ed59a9be3c1470d95931c98a1937e0fef63
Author: ashutak 
Date:   2016-02-04T12:19:11Z

ignite-2521: cfg from source cfg as method parameter

commit dd7ac362fd5ffa11373cf97f36c0d155c05a7ed9
Author: ashutak 
Date:   2016-02-04T12:21:08Z

ignite-2521: enable 3 cache modes

commit 8b6457dab9614ed86e658b03c36fe50ecffeaa2f
Author: ashutak 
Date:   2016-02-04T13:25:27Z

ignite-2521: add CacheFullApiNodesThenCachesTestSuite suite

commit f402c97b169decebc461e9cc5bac20d9e17859a1
Author: ashutak 
Date:   2016-02-04T13:33:08Z

ignite-2521: rename suite

commit f39bdecbc34fb5730d72759007670771ed166bc9
Author: ashutak 
Date:   2016-02-04T13:41:35Z

Merge branch 'master' into ignite-2521-tests

commit fd9d3c0a30c91df97e69422edc30dc8d2c3ca92d
Author: ashutak 
Date:   2016-02-04T14:38:43Z

ignite-2521: add static mode

commit 0cb49162c410b2284b27aae90a8549bb7617eee8
Author: ashutak 
Date:   2016-02-04T17:31:42Z

ignite-2521: add CacheFullApiNodesThenCachesTestSuite2-3

commit e297d0cb62d5fee364f8bac13467c8e04a279a92
Author: ashutak 
Date:   2016-02-04T18:39:44Z

ignite-2521: a simple fix for IGNITE-2554

commit 755fec377ab9dbac4a01afef418a7393f51d4485
Author: ashutak 
Date:   2016-02-04T19:18:05Z

ignite-2521: add debug info for tests

commit 

[GitHub] ignite pull request: ignite-2325 - Fixing assertion on prepare fut...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/434


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Remove GridBoundedConcurrentLinkedHashMap and replace its usages with ConcurrentLinkedHashMap

[Denis Magda]

Hi Konstantin,

I've shared my thoughts on your questions. Yakov, as a creator of the 
ticket, please share your view on whether these changes are really 
needed or not.


--
Denis

 Forwarded Message 
Subject:Re: Hello
Date:   Mon, 15 Feb 2016 15:08:25 +0300
From:   Konstantin Margorin 
Reply-To:   dev@ignite.apache.org
To: dev@ignite.apache.org



Hi all.

Could please someone review my comment to
https://issues.apache.org/jira/browse/IGNITE-1783

It's easy to make a patch, but this will lead to longer arguments list in
some places. Is it ok?

On Tue, Feb 9, 2016 at 3:11 PM, Vladimir Ozerov 
wrote:


Konstantin,

This ticket is more about build process. You can also look at the following
ones:
https://issues.apache.org/jira/browse/IGNITE-1783
https://issues.apache.org/jira/browse/IGNITE-2555

Vladimir.

On Tue, Feb 9, 2016 at 2:57 PM, Konstantin Margorin 
wrote:

> Hi Vladimir.
>
> I had searched through open tickets for newbies. And looks like the only
> open unassigned ticked is:
> https://issues.apache.org/jira/browse/IGNITE-2049
>
> Is this ticket right point to start?
>
> Best regards,
> Konstantin
>
> On Tue, Feb 9, 2016 at 2:30 PM, Vladimir Ozerov 
> wrote:
>
> > Konstantin, sorry I confused the name.
> >
> > Should you have any further questions please feel free to ask.
> >
> > On Tue, Feb 9, 2016 at 2:29 PM, Vladimir Ozerov 
> > wrote:
> >
> > > Hi Carlos,
> > >
> > > Welcome to the Ignite community!
> > >
> > > You should get familiar with Ignite development process described
here:
> > >
https://cwiki.apache.org/confluence/display/IGNITE/Development+Process
> > >
> > > Instructions on how to contribute can be found here:
> > > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
> > >
> > > Once you got familiar and were able to run a few examples, you should
> > pick
> > > a Jira ticket you would like to start on. Send an email to the dev
> list,
> > so
> > > we can add you as a contributor in Jira.
> > >
> > > You can find interesting tickets to get started here:
> > > https://ignite.apache.org/community/contribute.html#pick-ticket
> > >
> > > Looking forward to your contributions!
> > >
> > > Regards,
> > > Vladimir.
> > >
> > >
> > > On Tue, Feb 9, 2016 at 12:58 PM, Konstantin Margorin <
rus...@gmail.com
> >
> > > wrote:
> > >
> > >> Hi All,
> > >>
> > >> I'm Konstantin Margorin from Anturis.
> > >>
> > >> I would like to contribute my effort on Apache Ignite project and
> > >> appreciate if I could join with you.
> > >>
> > >> Looking forward to your reply.
> > >>
> > >> Best regards,
> > >> Konstantin
> > >>
> > >
> > >
> >
>

[jira] [Created] (IGNITE-2654) Protocol optimization for GridNearLockRequest/Response

[Ilya Lantukh (JIRA)]

Ilya Lantukh created IGNITE-2654:


 Summary: Protocol optimization for GridNearLockRequest/Response
 Key: IGNITE-2654
 URL: https://issues.apache.org/jira/browse/IGNITE-2654
 Project: Ignite
  Issue Type: Sub-task
Reporter: Ilya Lantukh
Assignee: Ilya Lantukh


Create new, more lightweight versions of GridNearLockRequest/Response:
- Make miniId integer.
- Store boolean flags in a single byte field.
- Remove unused fields.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-2653) .Net: StoreExample failed when running with remote nodes

[Vasilisa Sidorova (JIRA)]

Vasilisa  Sidorova created IGNITE-2653:
--

 Summary: .Net: StoreExample failed when running with remote nodes
 Key: IGNITE-2653
 URL: https://issues.apache.org/jira/browse/IGNITE-2653
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 1.6
 Environment: release version 1.6.1-b1
Reporter: Vasilisa  Sidorova


-
DESCRIPTION
-
.Net: StoreExample failed when running with remote nodes
-
STEPS FOR REPRODUCE
-
# Build .Net examples project
# Run several remote nodes from ./bin directory by the command:
{noformat}
Apache.Ignite.exe -IgniteHome="%IGNITE_HOME%" 
-springConfigUrl=platforms\dotnet\examples\config\example-cache-store.xml 
-assembly=[path_to_Apache.Ignite.ExamplesDll.dll]
{noformat}
# Run StoreExample
-
ACTUAL RESULT
-
Example failed with error:
{noformat}
GridGain.Cache.CacheException was unhandled
  HResult=-2146233088
  Message=class org.apache.ignite.IgniteCheckedException: Duplicate field name: 
args
  Source=GridGain.Core
  StackTrace:
   at GridGain.Impl.Unmanaged.UnmanagedCallbacks.Error(Void* target, Int32 
errType, SByte* errClsChars, Int32 errClsCharsLen, SByte* errMsgChars, Int32 
errMsgCharsLen, Void* errData, Int32 errDataLen)
   at 
GridGain.Impl.Unmanaged.UnmanagedUtils.TargetInStreamOutLong(IUnmanagedTarget 
target, Int32 opType, Int64 memPtr)
   at GridGain.Impl.GridTarget.DoOutOp(Int32 type, Action`1 action)
   at GridGain.Impl.Cache.CacheImpl`2.LoadCache0(ICacheEntryFilter`2 p, 
Object[] args, Int32 opId)
   at GridGain.Impl.Cache.CacheImpl`2.LoadCache(ICacheEntryFilter`2 p, 
Object[] args)
   at GridGain.Impl.Cache.CacheProxyImpl`2.LoadCache(ICacheEntryFilter`2 p, 
Object[] args)
   at GridGain.Examples.Datagrid.StoreExample.Main() in 
C:\work_vsidorova\GG\gridgain-last\platforms\gridgain\dotnet\examples\GridGainExamples\Datagrid\StoreExample.cs:line
 62
   at System.AppDomain._nExecuteAssembly(RuntimeAssembly assembly, String[] 
args)
   at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly()
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext 
executionContext, ContextCallback callback, Object state, Boolean 
preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext 
executionContext, ContextCallback callback, Object state, Boolean 
preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext 
executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()
  InnerException: 
{noformat}
-
EXPECTED RESULT
-
Examples passed without any exceptions
-
ADDITIONAL INFO
-
Isn't reproducible when StoreExample runs without remote nodes



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Ignite components deserialization

[Vladimir Ershov]

Yes, thanks, already working on it.

The reason was: Ignite experts decided, that there should be no case for
Ignite to be deserialized outside of IgniteThread.

On Sat, Feb 13, 2016 at 2:30 AM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:

> Folks,
>
> I reopened the ticket where we improved the serialization of Ignite
> components [1].
>
> From what I can see, the fix was made for IgniteKernal, but not for other
> classes like ClusterGroupAdapter, GridKernalContextImpl and others. What is
> the reason for this?
>
> Vladimir Ershov, it looks like you were working on this, can you please
> respond?
>
> [1] https://issues.apache.org/jira/browse/IGNITE-10
>
> -Val
>

[GitHub] ignite pull request: IGNITE-2652: Fix for the QueryFieldsRow::GetN...

[isapego]

GitHub user isapego opened a pull request:

https://github.com/apache/ignite/pull/483

IGNITE-2652: Fix for the QueryFieldsRow::GetNext.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/isapego/ignite ignite-2652

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/483.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #483


commit 555b242317c770136d93a0ccc95335d4e1146781
Author: isapego 
Date:   2016-02-15T13:09:53Z

IGNITE-2652: Fix for the QueryFieldsRow::GetNext.




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (IGNITE-2652) CPP: The throwing version of the QueryFieldsRow::GetNext() can't be used.

[Igor Sapego (JIRA)]

Igor Sapego created IGNITE-2652:
---

 Summary: CPP: The throwing version of the 
QueryFieldsRow::GetNext() can't be used.
 Key: IGNITE-2652
 URL: https://issues.apache.org/jira/browse/IGNITE-2652
 Project: Ignite
  Issue Type: Bug
  Components: platforms
Affects Versions: 1.5.0.final
Reporter: Igor Sapego
Assignee: Igor Sapego
 Fix For: 1.6


Method {{QueryFieldsRow::GetNext()}} can't be used as it has error in it's 
body. Basically, any code that uses this method will fail to compile. Need to 
fix it and add test with this method.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-2651) Table name inference

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-2651:
--

 Summary: Table name inference
 Key: IGNITE-2651
 URL: https://issues.apache.org/jira/browse/IGNITE-2651
 Project: Ignite
  Issue Type: Sub-task
  Components: platforms
Affects Versions: 1.1.4
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 1.6






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: NoopSwapSpaceSpi and dynamically started caches

[Artem Shutak]

I've created a newbie issue for that:
https://issues.apache.org/jira/browse/IGNITE-2650.

-- Artem --

On Wed, Feb 10, 2016 at 8:53 PM, Dmitriy Setrakyan 
wrote:

> Artem,
>
> I like the option with proper exception in case if a dynamic cache is
> started with swap enabled while there was no swap configured in Ignite.
>
> Starting FileSwapSpaceSpi all the time is not a good option as user will
> face the same problem when trying to change to a different SPI.
>
> D.
>
> On Wed, Feb 10, 2016 at 4:39 AM, Artem Shutak 
> wrote:
>
> > Igniters,
> >
> > I've noticed an issue with NoopSwapSpaceSpi and dynamically started
> cashes.
> >
> > We have the following logic on node start:
> >
> > if (cfg.getSwapSpaceSpi() == null) {
> > boolean needSwap = false;
> >
> > if (cfg.getCacheConfiguration() != null &&
> > !Boolean.TRUE.equals(cfg.isClientMode())) {
> > for (CacheConfiguration c :
> > cfg.getCacheConfiguration()) {
> > if (c.isSwapEnabled()) {
> > needSwap = true;
> >
> > break;
> > }
> > }
> > }
> >
> > cfg.setSwapSpaceSpi(needSwap ? new FileSwapSpaceSpi() :
> new
> > NoopSwapSpaceSpi());
> > }
> >
> > According to the code above, if IgniteConfiguration doesn't contain cache
> > configurations or all configured caches configured without swap, then
> node
> > will be started with NoopSwapSpaceSpi.
> > As a result in this case, when we start dynamic cache with enabled swap
> > then actually swap doesn't work.
> >
> > There is simple workaround - user have to explicitly set FileSwapSpaceSpi
> > to configuration. But now, there is no any warning or exception.
> >
> > What we can do:
> >
> >1. Throw an exception on dynamic cache start (with swap enabled)
> >if NoopSwapSpaceSpi is configured.
> >2. Actually, I don't see why we need NoopSwapSpaceSpi at all. I think
> we
> >should configure FileSwapSpaceSpi always if user doesn't provide any
> >SwapSpaceSpi explicitly.
> >
> > Thoughts?
> >
> > Thanks,
> > -- Artem --
> >
>

[jira] [Created] (IGNITE-2650) Ignite should throw an exception on start of dynamic cache with swap if Ignite uses NoopSwapSpaceSpi

[Artem Shutak (JIRA)]

Artem Shutak created IGNITE-2650:


 Summary: Ignite should throw an exception on start of dynamic 
cache with swap if Ignite uses NoopSwapSpaceSpi
 Key: IGNITE-2650
 URL: https://issues.apache.org/jira/browse/IGNITE-2650
 Project: Ignite
  Issue Type: Bug
Reporter: Artem Shutak
 Fix For: 1.6


Ignite should throw an exception on start of dynamic cache with enabled swap if 
Ignite uses NoopSwapSpaceSpi.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Hello

[Konstantin Margorin]

Hi all.

Could please someone review my comment to
https://issues.apache.org/jira/browse/IGNITE-1783

It's easy to make a patch, but this will lead to longer arguments list in
some places. Is it ok?

On Tue, Feb 9, 2016 at 3:11 PM, Vladimir Ozerov 
wrote:

> Konstantin,
>
> This ticket is more about build process. You can also look at the following
> ones:
> https://issues.apache.org/jira/browse/IGNITE-1783
> https://issues.apache.org/jira/browse/IGNITE-2555
>
> Vladimir.
>
> On Tue, Feb 9, 2016 at 2:57 PM, Konstantin Margorin 
> wrote:
>
> > Hi Vladimir.
> >
> > I had searched through open tickets for newbies. And looks like the only
> > open unassigned ticked is:
> > https://issues.apache.org/jira/browse/IGNITE-2049
> >
> > Is this ticket right point to start?
> >
> > Best regards,
> > Konstantin
> >
> > On Tue, Feb 9, 2016 at 2:30 PM, Vladimir Ozerov 
> > wrote:
> >
> > > Konstantin, sorry I confused the name.
> > >
> > > Should you have any further questions please feel free to ask.
> > >
> > > On Tue, Feb 9, 2016 at 2:29 PM, Vladimir Ozerov 
> > > wrote:
> > >
> > > > Hi Carlos,
> > > >
> > > > Welcome to the Ignite community!
> > > >
> > > > You should get familiar with Ignite development process described
> here:
> > > >
> https://cwiki.apache.org/confluence/display/IGNITE/Development+Process
> > > >
> > > > Instructions on how to contribute can be found here:
> > > > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
> > > >
> > > > Once you got familiar and were able to run a few examples, you should
> > > pick
> > > > a Jira ticket you would like to start on. Send an email to the dev
> > list,
> > > so
> > > > we can add you as a contributor in Jira.
> > > >
> > > > You can find interesting tickets to get started here:
> > > > https://ignite.apache.org/community/contribute.html#pick-ticket
> > > >
> > > > Looking forward to your contributions!
> > > >
> > > > Regards,
> > > > Vladimir.
> > > >
> > > >
> > > > On Tue, Feb 9, 2016 at 12:58 PM, Konstantin Margorin <
> rus...@gmail.com
> > >
> > > > wrote:
> > > >
> > > >> Hi All,
> > > >>
> > > >> I'm Konstantin Margorin from Anturis.
> > > >>
> > > >> I would like to contribute my effort on Apache Ignite project and
> > > >> appreciate if I could join with you.
> > > >>
> > > >> Looking forward to your reply.
> > > >>
> > > >> Best regards,
> > > >> Konstantin
> > > >>
> > > >
> > > >
> > >
> >
>

[jira] [Created] (IGNITE-2649) Ignition.localIgnite() unreliable under Gateways and cause wrong components deserialization.

[Vladimir Ershov (JIRA)]

Vladimir Ershov created IGNITE-2649:
---

 Summary: Ignition.localIgnite() unreliable under Gateways and 
cause wrong components deserialization.
 Key: IGNITE-2649
 URL: https://issues.apache.org/jira/browse/IGNITE-2649
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 1.5.0.final
Reporter: Vladimir Ershov
Assignee: Vladimir Ershov
Priority: Critical
 Fix For: 1.6


We can get something like this:
{noformat}
java.lang.IllegalArgumentException: This method should be accessed under 
org.apache.ignite.thread.IgniteThread
at org.apache.ignite.internal.IgnitionEx.localIgnite(IgnitionEx.java:1252)
at org.apache.ignite.Ignition.localIgnite(Ignition.java:531)
at org.project.MyPojo.readResolve(MyPojo.java:123)
at 
org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:746)
at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1448)
at 
org.apache.ignite.internal.binary.BinaryUtils.doReadObject(BinaryUtils.java:1564)
at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.readObject(BinaryReaderExImpl.java:1086)
at 
org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.readFixedType(BinaryFieldAccessor.java:827)
at 
org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read(BinaryFieldAccessor.java:643)
at 
org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:734)
at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1448)
at 
org.apache.ignite.internal.binary.BinaryUtils.doReadObject(BinaryUtils.java:1564)
at 
org.apache.ignite.internal.binary.BinaryUtils.deserializeOrUnmarshal(BinaryUtils.java:1908)
at 
org.apache.ignite.internal.binary.BinaryUtils.doReadMap(BinaryUtils.java:1892)
at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1595)
at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.readField(BinaryReaderExImpl.java:1644)
at 
org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read(BinaryFieldAccessor.java:643)
at 
org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:734)
at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1448)
at 
org.apache.ignite.internal.binary.BinaryObjectImpl.deserializeValue(BinaryObjectImpl.java:537)
at 
org.apache.ignite.internal.binary.BinaryObjectImpl.value(BinaryObjectImpl.java:117)
at 
org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinary(CacheObjectContext.java:257)
at 
org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinaryIfNeeded(CacheObjectContext.java:148)
at 
org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinaryIfNeeded(CacheObjectContext.java:135)
at 
org.apache.ignite.internal.processors.cache.GridCacheContext.unwrapBinaryIfNeeded(GridCacheContext.java:1757)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.setResult(GridPartitionedSingleGetFuture.java:629)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.localGet(GridPartitionedSingleGetFuture.java:421)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.mapKeyToNode(GridPartitionedSingleGetFuture.java:337)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.map(GridPartitionedSingleGetFuture.java:204)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedSingleGetFuture.init(GridPartitionedSingleGetFuture.java:196)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedCache.getAsync(GridDhtColocatedCache.java:266)
at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4774)
at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4758)
at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1391)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.get(IgniteCacheProxy.java:865)
{noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] ignite pull request: IGNITE-1630 Language Integrated Queries in ca...

[ptupitsyn]

GitHub user ptupitsyn opened a pull request:

https://github.com/apache/ignite/pull/482

IGNITE-1630 Language Integrated Queries in cache (LINQ)



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ptupitsyn/ignite ignite-1630

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/482.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #482


commit eaa8d99ece9d43eb11f51222cf837669e2e8ce6c
Author: Pavel Tupitsyn 
Date:   2016-02-03T09:15:49Z

wip

commit 00f1d0030960f95dbf8aba20151b87e01147f362
Author: Pavel Tupitsyn 
Date:   2016-02-03T09:37:23Z

wip queryField serialization

commit 62bd822c65b6aa5de594036663799c5c4cbca45a
Author: Pavel Tupitsyn 
Date:   2016-02-03T09:47:16Z

wip tests

commit b805d11dffb0bab8af57d9603cdae40376f84402
Author: Pavel Tupitsyn 
Date:   2016-02-03T09:51:19Z

wip

commit 3037de5119a534db6631bdb03adcbead2c16f49e
Author: Pavel Tupitsyn 
Date:   2016-02-03T09:54:01Z

Fix conversion

commit ed7ceadb809cc3d5100c25f09e7860720b947194
Author: Pavel Tupitsyn 
Date:   2016-02-03T10:01:06Z

wip

commit e8c400a25a2fd4323c85009d77db55ae597ccae0
Author: Pavel Tupitsyn 
Date:   2016-02-03T10:21:47Z

wip

commit 67946c45f0921daa504fcc00cb6f38232d786900
Author: Pavel Tupitsyn 
Date:   2016-02-03T10:26:26Z

formatdatetime

commit 777afd0ebb3edc89225e7b6ac566846847db3d1b
Author: Pavel Tupitsyn 
Date:   2016-02-03T10:37:59Z

wip DateTimeToString

commit a7081d69f708a3fb3878fd937514c89a659fe567
Author: Pavel Tupitsyn 
Date:   2016-02-03T10:41:38Z

wip

commit 7aa47d8f6cda9e4a9717ca49a4f5e56d455699d8
Author: Pavel Tupitsyn 
Date:   2016-02-03T10:51:30Z

wip

commit 2b82aedbbc19a91827c78052263f178a278ff2df
Author: Pavel Tupitsyn 
Date:   2016-02-03T10:55:09Z

wip

commit 2b4feea9879e9bc00fb879c4c3e8f74f97dfd75a
Author: Pavel Tupitsyn 
Date:   2016-02-03T10:59:12Z

wip

commit aa8762280d06260eb08cd232ce8374acf4a9926e
Author: Pavel Tupitsyn 
Date:   2016-02-03T11:58:18Z

wip num tests

commit 852ceaea3a211a0fe0e64014eb6d9b99a313f59a
Author: Pavel Tupitsyn 
Date:   2016-02-03T12:05:15Z

wip

commit 3c41eb4ec3ba5594bd9369c0568cfccc3834f1d3
Author: Pavel Tupitsyn 
Date:   2016-02-03T12:28:55Z

Refactor method handling

commit 25a1963f401bc75b0215f91d972cdea74cafd070
Author: Pavel Tupitsyn 
Date:   2016-02-03T12:29:53Z

wip

commit eb5277af81378ef32a12663d75a1e67320f27674
Author: Pavel Tupitsyn 
Date:   2016-02-03T12:30:12Z

wip

commit 53e76ac446996894d2aebaa59915a79a110ffefd
Author: Pavel Tupitsyn 
Date:   2016-02-03T12:34:15Z

wip

commit f3f4a7c058460a94e012dd6b53a8e140a0dc1dc0
Author: Pavel Tupitsyn 
Date:   2016-02-03T12:36:04Z

wip math abs

commit 9c9160760877c0ab9fe07c6d69203f22d6792e70
Author: Pavel Tupitsyn 
Date:   2016-02-03T12:37:49Z

Fix tests dependency

commit 4df1b58b7dd97fe29a55c316ad8e6b925e99f37a
Author: Pavel Tupitsyn 
Date:   2016-02-03T12:46:00Z

wip

commit 8922f3dbeab87c3a91f4ed9113472ca1d657863a
Author: Pavel Tupitsyn 
Date:   2016-02-03T12:48:10Z

wip

commit 8c32aa85127e58eb3b8ed53b661cb306ad06c64f
Author: Pavel Tupitsyn 
Date:   2016-02-03T14:21:23Z

Numeric tests

commit 50986d823297c62cbffd4cc5a3514aa4c977e93f
Author: Pavel Tupitsyn 
Date:   2016-02-03T14:57:40Z

Logger

commit ea87f25a1cb30f79baa59362c42537ab2718972e
Author: Pavel Tupitsyn 
Date:   2016-02-03T15:09:59Z

Type conversion warnings

commit 39cf8bd3565d132c722c21070146f1b5886bcaaf
Author: Pavel Tupitsyn 
Date:   2016-02-03T15:21:48Z

wip

commit b1c7ce67b441ec0b16d73b24e546b8ce461acc54
Author: Pavel Tupitsyn 
Date:   2016-02-03T15:33:03Z

QueryFields typed overload

commit 60608a7664f4956e9eb67d437c6e6c0658c95a7f
Author: Pavel Tupitsyn 
Date:   2016-02-03T15:52:26Z

Use new QueryFields overload

commit 0dcc04028b45e991ea3e4b6f995f1820e9ecfb1a
Author: Pavel Tupitsyn 
Date:   2016-02-03T16:02:15Z

Numeric test passes




---
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 

Re: Grid behavior at key deserialization failure during rebalancing

[Anton Vinogradov]

Dmitriy,

Key can be undeserializable during rebalancing because of many reasons.
For example,
1) It was serialized with errors
2) Deserialization cause error
3) It based on classes unavailable at node trying to deserialize it
Third is the most possible case.


On Sat, Feb 13, 2016 at 3:44 AM, Dmitriy Setrakyan 
wrote:

> Anton,
>
> I am not sure I fully grok the use case. Can you please explain why a key
> can be broken?
>
> D.
>
> On Fri, Feb 12, 2016 at 7:11 AM, Anton Vinogradov <
> avinogra...@gridgain.com>
> wrote:
>
> > Igniters,
> >
> > At this moment key deserialization failure during rebalancing cause
> strange
> > situation:
> >
> > Rebalancing from node sent supply message with broken key will be
> cancelled
> > at current topology.
> > All upcoming supply messages from this node will be be ignored, no new
> > demand messages to this node will be sent.
> >
> > But when topology will be changed again, node with broken key will take
> > path at rebalancing again, untill key deserialization failure happen ...
> > again.
> >
> > Do we need to improve this situation, and if we have to how should be
> > handled case with key deserialization failure?
> >
> > I see some ways:
> > 1) We can inform user about data loss because of deserialization
> problems,
> > but keep current rebalancing strategy
> > 2) We can continue rebalancing from this node, but ignore messages with
> > broken keys. And inform user about data loss.
> > 3) We can pause rebalancing untill deserialization will be fixed somehow,
> > for example by shutdowning demanding or supplying node.
> >
> > Thoughts?
> >
>

[GitHub] ignite pull request: IGNITE-2597 added socket support

[Dmitriyff]

GitHub user Dmitriyff opened a pull request:

https://github.com/apache/ignite/pull/481

IGNITE-2597 added socket support 



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/Dmitriyff/ignite ignite-2597

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/481.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #481






---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request: Ignite 2598

[dkarachentsev]

GitHub user dkarachentsev opened a pull request:

https://github.com/apache/ignite/pull/480

Ignite 2598



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/dkarachentsev/ignite ignite-2598

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/480.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #480


commit 946dccb9e98419bf9921b12607667d74ef87ecda
Author: dkarachentsev 
Date:   2016-02-10T08:33:04Z

IGNITE-2575 Add limit on minimal value of IGFS IPC port configuration.

commit 3d5999821d0efd6c026adbb3256c86bc798dc1c7
Author: dkarachentsev 
Date:   2016-02-10T08:50:09Z

Merge remote-tracking branch 'upstream/master'

commit 375eb11ba8c9076906971785fdb7bead294d8022
Author: dkarachentsev 
Date:   2016-02-11T09:47:18Z

Merge remote-tracking branch 'upstream/master'

commit 88a11b4554884acd2dbd956fcbd37a8932fbde8e
Author: dkarachentsev 
Date:   2016-02-12T08:39:32Z

Merge remote-tracking branch 'upstream/master'

commit ee9647f304b01299e18a5eb962680c197f41dbbb
Author: dkarachentsev 
Date:   2016-02-15T08:20:38Z

IGNITE-2598 - Fix Enum arguments in SQL queries are not considered with 
BinaryMarshaller

commit 210668fe7d9d91e0f244ff7ac6e1ff38db1af152
Author: dkarachentsev 
Date:   2016-02-15T08:23:35Z

IGNITE-2598 - Fix Enum arguments in SQL queries are not considered with 
BinaryMarshaller

commit 1ad41053d6f101714aa970693937a14ee5f40546
Author: dkarachentsev 
Date:   2016-02-15T08:27:28Z

IGNITE-2598 - Fix Enum arguments in SQL queries are not considered with 
BinaryMarshaller




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---