[GitHub] ignite pull request #789: Fix for ignite-3293

[irudyak]

GitHub user irudyak reopened a pull request:

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

Fix for ignite-3293

It's a patch to scripts bootstrapping Ignite-Cassandra-LoadTests 
infrastructure in Amazon

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

$ git pull https://github.com/irudyak/ignite ignite-3293

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

https://github.com/apache/ignite/pull/789.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 #789


commit a725b5f16d9b6fb4363432710cb87d420b2c8a88
Author: Igor 
Date:   2016-06-10T00:03:09Z

fix for ignite-3293

commit 7ba18f937fcd4d54ba156397d893731588a04f4e
Author: Igor 
Date:   2016-06-10T04:04:21Z

shell scripts to recreate Cassandra artifacts on each load tests execution




---
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 #789: Fix for ignite-3293

[irudyak]

Github user irudyak closed the pull request at:

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


---
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 #793: Ignite 2938

[iveselovskiy]

GitHub user iveselovskiy opened a pull request:

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

Ignite 2938



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

$ git pull https://github.com/gridgain/apache-ignite ignite-2938

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

https://github.com/apache/ignite/pull/793.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 #793


commit f5261a00aff96c98e0c78bed7c3c82e810a4e5c6
Author: vershov 
Date:   2016-02-08T18:54:48Z

IGNITE-2509 - Fixed evictions for OFFHEAP_VALUES memory mode - Fixes #452.

Signed-off-by: Alexey Goncharuk 

commit 2e2d271d28328f3d483fb1570d2ce88e73b51707
Author: vershov 
Date:   2016-02-12T09:51:50Z

IGNITE-2509 - Fixed offheap metrics - Fixes #470.

Signed-off-by: Alexey Goncharuk 

commit 89c3f20755ca9714b997162b2bbe6393332b5d2b
Author: Anton Vinogradov 
Date:   2016-02-12T11:08:25Z

IGNITE-2468
(cherry picked from commit 725d6cb)

commit 22f41bc5840b23f1fa0e1a4a7f2332a3d60b613c
Author: Anton Vinogradov 
Date:   2016-02-12T11:30:08Z

IGNITE-2603
(cherry picked from commit a32dfc4)

commit a835fc498d18b16e4711350aec31c2afba0a253a
Author: sboikov 
Date:   2016-02-15T09:00:44Z

ignite-2542 'Dummy' merge index should not try to access h2 table. (cherry 
picked from commit 9c4f811)

commit 015162de24737c46e8ea6f6a73c5eb321cf30507
Author: Anton Vinogradov 
Date:   2016-02-15T09:09:04Z

IGNITE-2468 hotfix
(cherry picked from commit e6b5087)

commit cab1f80f3703fff6d632a8e46bb0fd46209b9f09
Author: vozerov-gridgain 
Date:   2016-02-15T09:53:43Z

IGNITE-2509: Added one more tests to ensure that all is fine.

commit 9360cce383827e9abef13ec2fc061bc316a2afd2
Author: vozerov-gridgain 
Date:   2016-02-15T09:54:41Z

Merge remote-tracking branch 'origin/ignite-1.5.7' into ignite-1.5.7

commit e41ab7664888f1253636d65c3950e8a5f874946a
Author: Pavel Tupitsyn 
Date:   2016-02-12T13:09:00Z

IGNITE-2625 .NET: Fixed field offset calculation in BinaryReader.

commit 0964f14b421df978456126637b7ac796e08b3aae
Author: Alexey Goncharuk 
Date:   2016-02-15T17:12:04Z

IGNITE-2325 - Fixed assertion in optimistic tx prepare future on remap - 
Fixes #434.

Signed-off-by: Alexey Goncharuk 

commit dd6681046ffc0bea4cb2120845deb5e5e37cbc53
Author: nikolay_tikhonov 
Date:   2016-02-16T10:47:44Z

Fixed IGNITE-2604 "CacheContinuousQueryBatchAck is sent to nodes that 
doesn't hold cache data".

commit 4de124c41a30e8b4ee825c355686e16228a4390d
Author: nikolay_tikhonov 
Date:   2016-02-16T15:28:51Z

Fixed "IGNITE-2515 Make 'updateCntr' available through 
CacheContinuousQueryEvent public API"

commit 6291c64efab4a2e3d5d9986479bc7a4372fdb553
Author: sboikov 
Date:   2016-02-10T11:07:40Z

ignite-2587 Fixed continuous query notifications in offheap mode and 
BinaryObjectOffheapImpl usage.

commit 72500026cf69429a81dcdcf5ffc81c1db3ee7642
Author: nikolay_tikhonov 
Date:   2016-02-17T08:04:08Z

Fixed "IGNITE-2466 OutOfMemory when ONHEAP_TIERED mode is used".

commit e0eefa50588efcf3b836f93a4b1ca32f92d8973d
Author: sboikov 
Date:   2016-02-17T12:57:27Z

ignite-2669 Changed BinaryUtils.isBinaryType to always convert enums to 
BinaryObject
(cherry picked from commit 8be62f0)

commit 528d6aea65e5d0053649442e704476ee964ca218
Author: sboikov 
Date:   2016-02-17T12:04:30Z

ignite-2669 Changed BinaryUtils.isBinaryType to always convert enums to 
BinaryObject
(cherry picked from commit 8be62f0)

commit 1d3e8cf16eba8d34ee1f7021df6f9ec3bcf5b409
Author: Valentin Kulichenko 
Date:   2016-02-18T02:21:54Z

IGNITE-2249 - Do not deserialize services on client node

commit cffde1b58c56f05fcd4071c56862003afbbc8067
Author: Denis Magda 
Date:   2016-02-18T06:28:10Z

IGNITE-2647: Cache is undeployed even when BinaryMarshaller is used. Fixed.

commit 1a4db916d4b7ba202e22c12ca689337a3c3d1da2
Author: sboikov 
Date:   2016-02-18T06:06:32Z

ignite-2669 Register BinaryEnumObjectImpl as predefined type.
(cherry picked from commit 21f22d3)

commit 9d0f45372c7161bf7f67243cfab0451c293e8ba9
Author: dkarachentsev 
Date:   2016-02-12T13:02:32Z

IGNITE-2430: Fixed binary builder serialization logic for non-standard 
collections.

commit d24ecb1e4409b6dae005394d73f21bdb116a9376
Author: dkarachentsev 

[jira] [Created] (IGNITE-3302) .NET: Inject resources into user ILogger

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-3302:
--

 Summary: .NET: Inject resources into user ILogger
 Key: IGNITE-3302
 URL: https://issues.apache.org/jira/browse/IGNITE-3302
 Project: Ignite
  Issue Type: Sub-task
  Components: platforms
Affects Versions: 1.7
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 1.7






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

[GitHub] ignite pull request #792: Ignite 2938b

[iveselovskiy]

GitHub user iveselovskiy opened a pull request:

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

Ignite 2938b



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

$ git pull https://github.com/iveselovskiy/ignite ignite-2938b

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

https://github.com/apache/ignite/pull/792.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 #792


commit a652adec401dc11e6f930fcef9de9b2ee5ecdbb9
Author: iveselovskiy 
Date:   2016-02-10T15:54:36Z

added missing file header to 
org.apache.ignite.hadoop.fs.KerberosHadoopFileSystemFactorySelfTest

commit 48f00cac3ba7668247585ab7c257562951c4f04f
Author: iveselovskiy 
Date:   2016-02-11T10:36:12Z

Merge branch 'master' of https://github.com/apache/ignite

commit a5c5ed4d5bbd61c62acfbb19610aac2f710935cd
Author: iveselovskiy 
Date:   2016-02-15T17:58:10Z

Merge branch 'master' of https://github.com/apache/ignite

commit b81ee18308307dad2416f7635120a387b98bb967
Author: iveselovskiy 
Date:   2016-02-17T18:32:53Z

Merge branch 'master' of https://github.com/apache/ignite

commit 4280cbdeef94a6956ea3ebe1ae389f1db57ed249
Author: iveselovskiy 
Date:   2016-02-18T09:47:12Z

Merge branch 'master' of https://github.com/apache/ignite

commit 754132067d73757f9d362129444b7a6dea3b3f5b
Author: iveselovskiy 
Date:   2016-02-19T13:18:16Z

Merge branch 'master' of https://github.com/apache/ignite

commit cd3a1e02cec00bd089deb3e7cc4c9ec39e7279a7
Author: iveselovskiy 
Date:   2016-02-26T16:24:36Z

Merge branch 'master' of https://github.com/apache/ignite

commit de70be2bc0a6c545428650b1cc09965ac87de8aa
Author: iveselovskiy 
Date:   2016-03-11T09:30:30Z

Merge branch 'master' of https://github.com/apache/ignite

commit 6af5c26f04d2a03795b7c1279dd5532edecc31c4
Author: iveselovskiy 
Date:   2016-03-14T16:47:51Z

Merge branch 'master' of https://github.com/apache/ignite

commit 13a17ba842eb8b2a6820424df8516e0009085387
Author: iveselovskiy 
Date:   2016-03-17T14:35:21Z

Merge branch 'master' of https://github.com/apache/ignite

commit a9d57332727460019b7fc83581b5ba2107707a7c
Author: iveselovskiy 
Date:   2016-03-21T09:35:39Z

Merge branch 'master' of https://github.com/apache/ignite

commit 9cdbef79f9e6a9252076b367f76ba1073b231338
Author: iveselovskiy 
Date:   2016-03-22T09:40:58Z

Merge branch 'master' of https://github.com/apache/ignite

commit e559f51c6bb7cce38e195ffe0503662f0a5b8916
Author: iveselovskiy 
Date:   2016-03-22T12:28:37Z

Merge branch 'master' of https://github.com/apache/ignite

commit a7d9070ef0f6395a19089201020b8052676fb7e1
Author: iveselovskiy 
Date:   2016-03-22T16:00:05Z

Merge branch 'master' of https://github.com/apache/ignite

commit 4c3f10d5a6f3a995a7f553709704e1f9526991ef
Author: iveselovskiy 
Date:   2016-03-23T16:16:56Z

Merge branch 'master' of https://github.com/apache/ignite

commit b3788e4d569352659f855c355fe27c6aec62d344
Author: iveselovskiy 
Date:   2016-03-24T11:46:57Z

Merge branch 'master' of https://github.com/apache/ignite

commit ce7ed2398d5a74ac72292c6dd61959aeee324453
Author: iveselovskiy 
Date:   2016-03-30T13:54:27Z

Merge branch 'master' of https://github.com/apache/ignite

commit 7625c1c0ab76f1ac9c4a530c5c9b50b3852f2089
Author: iveselovskiy 
Date:   2016-03-31T09:08:45Z

Merge branch 'master' of https://github.com/apache/ignite

commit 59e48db3c3e9cd604c238eb691a5205fb95fac11
Author: iveselovskiy 
Date:   2016-03-31T11:03:38Z

Merge branch 'master' of https://github.com/apache/ignite

commit 58f0299b60a5cf428aa875f07df15b7eebd25dea
Author: iveselovskiy 
Date:   2016-04-05T10:21:52Z

Merge branch 'master' of https://github.com/apache/ignite

commit 9ef72306f5633ea70de701be69268b234232afa3
Author: iveselovskiy 
Date:   2016-04-05T15:26:45Z

Merge branch 'master' of https://github.com/apache/ignite

commit a9baa7710343f259b84a34bb0b08a1446694321b
Author: iveselovskiy 
Date:   2016-04-06T13:51:19Z

Merge branch 'master' of https://github.com/apache/ignite

commit f446214916a8beea6a624cc6695faac12a80207a
Author: iveselovskiy 
Date:   2016-04-08T13:43:03Z

Merge branch 'master' of https://github.com/apache/ignite

commit 878d14e3c1dbeea8c968d450a876a95d6d3f3560

[jira] [Created] (IGNITE-3301) .NET: Logging extension methods

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-3301:
--

 Summary: .NET: Logging extension methods
 Key: IGNITE-3301
 URL: https://issues.apache.org/jira/browse/IGNITE-3301
 Project: Ignite
  Issue Type: Sub-task
  Components: platforms
Affects Versions: 1.7
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 1.7


* Trace, Debug, Info, Warn, Error overloads
* GetLogger(category)



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

[jira] [Created] (IGNITE-3300) ArrayIndexOutOfBoundsException: -1 during capitalization benchmark running

[Ksenia Rybakova (JIRA)]

Ksenia Rybakova created IGNITE-3300:
---

 Summary: ArrayIndexOutOfBoundsException: -1 during capitalization 
benchmark running
 Key: IGNITE-3300
 URL: https://issues.apache.org/jira/browse/IGNITE-3300
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 1.7
Reporter: Ksenia Rybakova


Test config:
1 client, 16 servers
warmup 60
duration 1h
preload 5M
operations: capitalization benchmark
backups count 1

After ~30 min after start the following errors occur at the driver:
{noformat}
[08:42:51,367][ERROR][sys-#5%null%][GridTaskWorker] Failed to obtain remote job 
result policy for result from ComputeTask.result(..) method (will fail the 
whole task): GridJobResultImpl [job=C4V2 
[r=o.a.i.yardstick.cache.load.IgniteCapitalizationBenchmark$ScanQueryBroadcastClosure@41013d64],
 sib=GridJobSiblingImpl 
[sesId=bfb21563551-a8d91d06-89bd-41a5-8b4f-6a02416dfc63, 
jobId=51c21563551-a8d91d06-89bd-41a5-8b4f-6a02416dfc63, 
nodeId=79226bcc-651f-4af7-8d39-fd4019b7708c, isJobDone=false], 
jobCtx=GridJobContextImpl 
[jobId=51c21563551-a8d91d06-89bd-41a5-8b4f-6a02416dfc63, timeoutObj=null, 
attrs={}], node=TcpDiscoveryNode [id=79226bcc-651f-4af7-8d39-fd4019b7708c, 
addrs=[10.20.0.216, 127.0.0.1], sockAddrs=[fosters-216/10.20.0.216:47501, 
/10.20.0.216:47501, /127.0.0.1:47501], discPort=47501, order=5, intOrder=5, 
lastExchangeTime=1465485122287, loc=false, ver=1.7.0#20160603-sha1:82573436, 
isClient=false], ex=class o.a.i.compute.ComputeUserUndeclaredException: Failed 
to execute job due to unexpected runtime exception 
[jobId=51c21563551-a8d91d06-89bd-41a5-8b4f-6a02416dfc63, ses=GridJobSessionImpl 
[ses=GridTaskSessionImpl 
[taskName=o.a.i.yardstick.cache.load.IgniteCapitalizationBenchmark$ScanQueryBroadcastClosure,
 dep=LocalDeployment [super=GridDeployment [ts=1465485111989, depMode=SHARED, 
clsLdr=sun.misc.Launcher$AppClassLoader@6da264f1, 
clsLdrId=cee28b53551-79226bcc-651f-4af7-8d39-fd4019b7708c, userVer=0, loc=true, 
sampleClsName=java.lang.String, pendingUndeploy=false, undeployed=false, 
usage=0]], 
taskClsName=o.a.i.yardstick.cache.load.IgniteCapitalizationBenchmark$ScanQueryBroadcastClosure,
 sesId=bfb21563551-a8d91d06-89bd-41a5-8b4f-6a02416dfc63, 
startTime=1465486810898, endTime=9223372036854775807, 
taskNodeId=a8d91d06-89bd-41a5-8b4f-6a02416dfc63, 
clsLdr=sun.misc.Launcher$AppClassLoader@6da264f1, closed=false, cpSpi=null, 
failSpi=null, loadSpi=null, usage=1, fullSup=false, 
subjId=a8d91d06-89bd-41a5-8b4f-6a02416dfc63, mapFut=IgniteFuture 
[orig=GridFutureAdapter [resFlag=0, res=null, startTime=1465486811180, 
endTime=0, ignoreInterrupts=false, state=INIT]]], 
jobId=51c21563551-a8d91d06-89bd-41a5-8b4f-6a02416dfc63]], hasRes=true, 
isCancelled=false, isOccupied=true]
class org.apache.ignite.IgniteException: Remote job threw user exception 
(override or implement ComputeTask.result(..) method if you would like to have 
automatic failover for this exception).
at 
org.apache.ignite.compute.ComputeTaskAdapter.result(ComputeTaskAdapter.java:101)
at 
org.apache.ignite.internal.processors.task.GridTaskWorker$3.apply(GridTaskWorker.java:912)
at 
org.apache.ignite.internal.processors.task.GridTaskWorker$3.apply(GridTaskWorker.java:905)
at 
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6491)
at 
org.apache.ignite.internal.processors.task.GridTaskWorker.result(GridTaskWorker.java:905)
at 
org.apache.ignite.internal.processors.task.GridTaskWorker.onResponse(GridTaskWorker.java:801)
at 
org.apache.ignite.internal.processors.task.GridTaskProcessor.processJobExecuteResponse(GridTaskProcessor.java:995)
at 
org.apache.ignite.internal.processors.task.GridTaskProcessor$JobMessageListener.onMessage(GridTaskProcessor.java:1220)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1219)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:847)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:105)
at 
org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:810)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: class org.apache.ignite.compute.ComputeUserUndeclaredException: 
Failed to execute job due to unexpected runtime exception 
[jobId=51c21563551-a8d91d06-89bd-41a5-8b4f-6a02416dfc63, ses=GridJobSessionImpl 
[ses=GridTaskSessionImpl 
[taskName=org.apache.ignite.yardstick.cache.load.IgniteCapitalizationBenchmark$ScanQueryBroadcastClosure,
 dep=LocalDeployment [super=GridDeployment 

[jira] [Created] (IGNITE-3299) Cache remove can be lost in ATOMIC cache with OFFHEAP_TIERED memory mode

[Semen Boikov (JIRA)]

Semen Boikov created IGNITE-3299:


 Summary: Cache remove can be lost in ATOMIC cache with 
OFFHEAP_TIERED memory mode
 Key: IGNITE-3299
 URL: https://issues.apache.org/jira/browse/IGNITE-3299
 Project: Ignite
  Issue Type: Bug
  Components: cache
Reporter: Semen Boikov
Assignee: Semen Boikov
Priority: Critical
 Fix For: 1.7


Added test reproducing issue (IgniteCacheConcurrentPutGetRemove).

1. There is an issue with 'deferredDelete' implementation - entry marked as 
'deleted' can be evicted from cache, after this information about remove is 
lost (note: this can be reproduced not only in OFFHEAP_TIERED, but also in 
ONHEAP_TIERED mode with eviction policy, also this can also cause lost update 
in transactional cache on changing topology).

2. Looks like condition for removing from offheap in 
GridCacheMapEntry.innerUpdate is not correct:
{noformat}
if (op != GridCacheOperation.UPDATE && cctx.offheapTiered() && 
hasValPtr) {
boolean rmv = cctx.swap().removeOffheap(key);
{noformat}

It is possible that value was put in offheap, but 'hasValPtr' is false.




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

[jira] [Created] (IGNITE-3298) Do not work "Export all" on SQL page

[Vasiliy Sisko (JIRA)]

Vasiliy Sisko created IGNITE-3298:
-

 Summary: Do not work "Export all" on SQL page
 Key: IGNITE-3298
 URL: https://issues.apache.org/jira/browse/IGNITE-3298
 Project: Ignite
  Issue Type: Sub-task
  Components: wizards
Affects Versions: 1.7
Reporter: Vasiliy Sisko






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

[jira] [Created] (IGNITE-3297) Pipe chart is empty in special case.

[Vasiliy Sisko (JIRA)]

Vasiliy Sisko created IGNITE-3297:
-

 Summary: Pipe chart is empty in special case.
 Key: IGNITE-3297
 URL: https://issues.apache.org/jira/browse/IGNITE-3297
 Project: Ignite
  Issue Type: Sub-task
  Components: wizards
Affects Versions: 1.7
Reporter: Vasiliy Sisko


# Execute query where column A and B have the same values in all rows.
# Build Pipe chart where A and B columns set as X and Y columns. 
Showed legend for chart but chart area is empty.




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

[jira] [Created] (IGNITE-3296) Validation fail in special case

[Vasiliy Sisko (JIRA)]

Vasiliy Sisko created IGNITE-3296:
-

 Summary: Validation fail in special case
 Key: IGNITE-3296
 URL: https://issues.apache.org/jira/browse/IGNITE-3296
 Project: Ignite
  Issue Type: Sub-task
  Components: wizards
Affects Versions: 1.7
Reporter: Vasiliy Sisko
Assignee: Dmitriyff


# Enable some section that have disabled fields.
# Input in field invalid value.
# Disable section and try to save.
- Validation show invalid message for disabled field.



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

[GitHub] ignite pull request #791: fix for ignite-3238

[avinogradovgg]

GitHub user avinogradovgg opened a pull request:

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

fix for ignite-3238



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

$ git pull https://github.com/irudyak/ignite ignite-3238

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

https://github.com/apache/ignite/pull/791.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 #791


commit e2767670fb048b24478e797f78be8dccc8587b94
Author: Igor 
Date:   2016-06-09T23:38:41Z

fix for ignite-3238




---
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 #783: Ignite 3238

[avinogradovgg]

Github user avinogradovgg closed the pull request at:

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


---
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-3295) IGFS: Introduce file ID cache (HashMap) to minimize cache calls.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-3295:
---

 Summary: IGFS: Introduce file ID cache (HashMap) to minimize cache 
calls.
 Key: IGNITE-3295
 URL: https://issues.apache.org/jira/browse/IGNITE-3295
 Project: Ignite
  Issue Type: Sub-task
  Components: IGFS
Affects Versions: 1.6
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
 Fix For: 1.7






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

[GitHub] ignite pull request #790: Mysql support broken in 1.6, externalize sql synta...

[krosenvold]

GitHub user krosenvold opened a pull request:

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

Mysql support broken in 1.6, externalize sql syntax to make it configurable

To avoid quarreling about different dialects, made it configurable

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

$ git pull https://github.com/krosenvold/ignite externalizeSqlSyntax

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

https://github.com/apache/ignite/pull/790.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 #790


commit 0160a13c79c4e57151d2d4f68aa20aa55d1686d6
Author: Kristian Rosenvold 
Date:   2016-06-10T07:19:38Z

Externalized sql dialect

To avoid quarreling about different dialects, made it configurable




---
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-3294) IGFS: Request multiple path IDs in a single request during sync step.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-3294:
---

 Summary: IGFS: Request multiple path IDs in a single request 
during sync step.
 Key: IGNITE-3294
 URL: https://issues.apache.org/jira/browse/IGNITE-3294
 Project: Ignite
  Issue Type: Task
  Components: IGFS
Affects Versions: 1.6
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
 Fix For: 1.7


Currently during secondary file system synchronization we request multiple 
paths in a separate "idsForPaths()" requests.

Instead, it is better to get all required IDs in a single request. Moreover, we 
can re-use already requested IDs.



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