[jira] [Created] (IGNITE-2458) Wrong generation on general section of model screen
Vasiliy Sisko created IGNITE-2458: - Summary: Wrong generation on general section of model screen Key: IGNITE-2458 URL: https://issues.apache.org/jira/browse/IGNITE-2458 Project: Ignite Issue Type: Sub-task Components: wizards Affects Versions: 1.6 Reporter: Vasiliy Sisko Assignee: Vasiliy Sisko Incorrect generation when *Annotation* value selected for *Query metadata*. Should be cache.setIndexedTypes... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2459) Validation for java reserved keywords is not working
Alexey Kuznetsov created IGNITE-2459: Summary: Validation for java reserved keywords is not working Key: IGNITE-2459 URL: https://issues.apache.org/jira/browse/IGNITE-2459 Project: Ignite Issue Type: Sub-task Components: wizards Affects Versions: 1.5.0.final Reporter: Alexey Kuznetsov Assignee: Andrey Novikov Fields that require fully qualified class names should validate user input for java reserved keywords, but now JavaTypes.nonKeywords(value) does not work properly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2460) issue with mandatory fields
Pavel Konstantinov created IGNITE-2460: -- Summary: issue with mandatory fields Key: IGNITE-2460 URL: https://issues.apache.org/jira/browse/IGNITE-2460 Project: Ignite Issue Type: Sub-task Reporter: Pavel Konstantinov now user cannot leave mandatory field for example on new cluster: 1) choose Discovery = AWS S3 2) Bucket name: is mandatory 3) try to change Discovery type -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2461) cannot edit address in discovery settings in cluster
Pavel Konstantinov created IGNITE-2461: -- Summary: cannot edit address in discovery settings in cluster Key: IGNITE-2461 URL: https://issues.apache.org/jira/browse/IGNITE-2461 Project: Ignite Issue Type: Sub-task Reporter: Pavel Konstantinov -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2463) UI should expand groups and scroll focus to first invalid field on Save button click
Alexey Kuznetsov created IGNITE-2463: Summary: UI should expand groups and scroll focus to first invalid field on Save button click Key: IGNITE-2463 URL: https://issues.apache.org/jira/browse/IGNITE-2463 Project: Ignite Issue Type: Sub-task Reporter: Alexey Kuznetsov Assignee: Dmitriyff Steps #Expand advanced settings #Enter some invalid value to any group #Collapse group #Hide advanced settings #Click on [Save] button Expected #Advanced settings expanded #Group expanded #Focus transferred (with scroll to viewport) to field with invalid value #Popup with error message shown -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2462) issue with empty address list in discovery on clusters page
Pavel Konstantinov created IGNITE-2462:
--
Summary: issue with empty address list in discovery on clusters
page
Key: IGNITE-2462
URL: https://issues.apache.org/jira/browse/IGNITE-2462
Project: Ignite
Issue Type: Sub-task
Reporter: Pavel Konstantinov
Just remove all addresses
{code}
17:12:35.935 Error: element[0] is undefined
TooltipFactory@https://staging-console.gridgain.com/app.min.js:57784:17
PopoverFactory@https://staging-console.gridgain.com/app.min.js:59706:28
showPopoverMessage@https://staging-console.gridgain.com/common-module.js:599:30
validate@https://staging-console.gridgain.com/all.js:1415:1
$scope.saveItem@https://staging-console.gridgain.com/all.js:1519:21
anonymous/fn@https://staging-console.gridgain.com/app.min.js line 92832 >
Function:2:450
ngEventHandler/https://staging-console.gridgain.com/app.min.js:96580:21
$RootScopeProvider/this.$gethttps://staging-console.gridgain.com/app.min.js:9:22
$RootScopeProvider/this.$gethttps://staging-console.gridgain.com/app.min.js:94467:26
ngEventHandler/<@https://staging-console.gridgain.com/app.min.js:96585:21
jQuery.event.dispatch@https://staging-console.gridgain.com/app.min.js:126675:25
jQuery.event.add/elemData.handle@https://staging-console.gridgain.com/app.min.js:126546:91
1 app.min.js:92038:24
consoleLog/<() app.min.js:92038
$ExceptionHandlerProvider/this.$get
[GitHub] ignite pull request: IGNITE-1786: Review-related fixes and refacto...
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/426 --- 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-2464) Text for validation tooltips should be configurable or specified.
Alexey Kuznetsov created IGNITE-2464: Summary: Text for validation tooltips should be configurable or specified. Key: IGNITE-2464 URL: https://issues.apache.org/jira/browse/IGNITE-2464 Project: Ignite Issue Type: Sub-task Components: wizards Affects Versions: 1.5.0.final Reporter: Alexey Kuznetsov Assignee: Dmitriyff -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] ignite pull request: IGNITE-2453 Fixed single primary and single b...
GitHub user VladimirErshov opened a pull request: https://github.com/apache/ignite/pull/427 IGNITE-2453 Fixed single primary and single backup failure cause NPE ⦠â¦at future for backup You can merge this pull request into a Git repository by running: $ git pull https://github.com/VladimirErshov/ignite ignite-2453 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/427.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 #427 commit 32d1524345e47cb13b68fc8890f1689584d6b4de Author: vershov Date: 2016-01-27T10:45:03Z IGNITE-2453 Fixed single primary and single backup failure cause NPE at future for backup --- 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-2465) Assertion in load cache closure
Denis Magda created IGNITE-2465:
---
Summary: Assertion in load cache closure
Key: IGNITE-2465
URL: https://issues.apache.org/jira/browse/IGNITE-2465
Project: Ignite
Issue Type: Bug
Components: cache
Affects Versions: 1.5.0.final
Reporter: Denis Magda
Assignee: Artem Shutak
Priority: Blocker
Fix For: 1.6
This is a tricky one. Every once in a while I get an assertion exception due to
a null cache instance. It's difficult to reproduce, but the reason is more or
less clear.
First, here's the sequence of events:
1) node N0 starts a cache with GridGain's LocalCacheStore configured (see the
cache config below).
2) also, N0 registers a listener for the Ignite DISCO_EVENTS.
3) node N1 joins the cluster.
4) N0 receives a discovery event (EVT_NODE_JOINED) and triggers cache loading
using IgniteCache.loadCache(null).
5) N1 throws an AssertionException due to Ignite.cache("persistent-cache") call
returning a null.
>From the log snippet below you can see that the exception is first reported
>and then a millisecond later GridCacheProcessor reports that the cache was
>started. This means that the cache load closure starts executing on node N1 a
>bit too early while the cache is still being started. I believe Ignite must be
>able to handle such race properly.
{noformat}
9319 [pub-#212%N1%] ERROR GridJobWorker - Failed to execute job due to
unexpected runtime exception
[jobId=0af5bad7251-9f7af4ba-6a64-4de4-b5d2-81d59be05303, ses=GridJobSessionImpl
[ses=GridTaskSessionImpl
[taskName=o.a.i.i.processors.cache.GridCacheAdapter$LoadCacheClosure,
dep=LocalDeployment [super=GridDeployment [ts=1453807336443, depMode=SHARED,
clsLdr=sun.misc.Launcher$AppClassLoader@15db9742,
clsLdrId=46f5bad7251-9f7af4ba-6a64-4de4-b5d2-81d59be05303, userVer=0, loc=true,
sampleClsName=java.lang.String, pendingUndeploy=false, undeployed=false,
usage=0]],
taskClsName=o.a.i.i.processors.cache.GridCacheAdapter$LoadCacheClosure,
sesId=e9f5bad7251-1edbab1e-37bf-424e-a9e1-0c866b95009d,
startTime=1453807336874, endTime=9223372036854775807,
taskNodeId=1edbab1e-37bf-424e-a9e1-0c866b95009d,
clsLdr=sun.misc.Launcher$AppClassLoader@15db9742, closed=false, cpSpi=null,
failSpi=null, loadSpi=null, usage=1, fullSup=false,
subjId=1edbab1e-37bf-424e-a9e1-0c866b95009d, mapFut=IgniteFuture
[orig=GridFutureAdapter [resFlag=0, res=null, startTime=1453807336894,
endTime=0, ignoreInterrupts=false, lsnr=null, state=INIT]]],
jobId=0af5bad7251-9f7af4ba-6a64-4de4-b5d2-81d59be05303]]
java.lang.AssertionError: persistent-cache
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter$LoadCacheClosure.call(GridCacheAdapter.java:5788)
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter$LoadCacheClosure.call(GridCacheAdapter.java:5740)
at
org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2.execute(GridClosureProcessor.java:1789)
at
org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:509)
at
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6397)
at
org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:503)
at
org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:456)
at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at
org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1166)
at
org.apache.ignite.internal.processors.job.GridJobProcessor$JobExecutionListener.onMessage(GridJobProcessor.java:1770)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:821)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$1600(GridIoManager.java:103)
at
org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:784)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
9320 [Thread-19] INFO GridCacheProcessor - Started cache
[name=persistent-cache, mode=REPLICATED]
{noformat}
For reference, here's the code that configures the cache:
{noformat}
CacheConfiguration config = new CacheConfiguration<>("persistent-cache");
config.setCacheMode(CacheMode.REPLICATED);
config.setAtomicityMode(CacheAtomicityMode.TRANSACTIONAL);
config.setRebalanceMode(CacheRebalanceMode.SYNC);
config.setWriteSynchronizationMode(CacheWriteSynchronizationMode.FULL_SYNC);
config.setStartSize(1024);
config.setCacheStoreFactory(new LocalCacheStoreFactory(somepath));
config.setWriteThrough(true);
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-2466) OutOfMemory when OFFHEAP_TIRED mode is used
Denis Magda created IGNITE-2466: --- Summary: OutOfMemory when OFFHEAP_TIRED mode is used Key: IGNITE-2466 URL: https://issues.apache.org/jira/browse/IGNITE-2466 Project: Ignite Issue Type: Bug Affects Versions: 1.5.0.final Reporter: Denis Magda Assignee: Nikolay Tikhonov Fix For: 1.6 To reproduce, run two server nodes with 2g of heap each and then MemTest. Servers will fail with OOME. If backups are disabled or there is only one server node, it works. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2467) Check box [Enable peer class loading] on [Class deployment] group should disable fields
Alexey Kuznetsov created IGNITE-2467: Summary: Check box [Enable peer class loading] on [Class deployment] group should disable fields Key: IGNITE-2467 URL: https://issues.apache.org/jira/browse/IGNITE-2467 Project: Ignite Issue Type: Sub-task Reporter: Alexey Kuznetsov Check box [Enable peer class loading] on [Class deployment] group should disable fields, but now they are hide. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2468) Continuous query is no longer deployed when node, that deployed it initially, leaves topology
Denis Magda created IGNITE-2468: --- Summary: Continuous query is no longer deployed when node, that deployed it initially, leaves topology Key: IGNITE-2468 URL: https://issues.apache.org/jira/browse/IGNITE-2468 Project: Ignite Issue Type: Bug Affects Versions: 1.5.0.final Reporter: Denis Magda Assignee: Nikolay Tikhonov Fix For: 1.6 Steps to reproduce: - Start a server node and run a continuous query setting autoUnsubscribe to false; - Start a client node that will update a single entry in a loop; - Start additional server node (without starting a query). Already existed query will be registered on this server node; - Check remote filter of both server nodes, they both have to receive updates (one server is primary while the other is backup); - Stop the first server that initiated the query; - Start one more server and you will see that the query won't be registered on it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Ignite Readme.IO UX issue
Hi: I have seen the changes in the document. I also found that part of the DataGrid has added a new section called "Lock". I maintain manual approach is, first from github document backup find changes, then according to the change point to find the online version of the difference and according to the online version do translation to ensure document consistency, because I know there is a part of the document is not open. So, I would like to have the official github backup function, otherwise I can't know what parts of the document have changed. 在 16/1/27 11:11, Dmitriy Setrakyan 写道: The version that corresponds to the documentation translated in Chinese is 1.5.0-b1: https://apacheignite.readme.io/v1.5-b1 The new v.1.5 contains mainly the following changes: - Hadoop and Spark were moved to a separate space: https://apacheignite-fs.readme.io/docs - Every category has an overview session now, e.g. Clustering, Data Structures, etc. You should be able to compare the GIT repos to apply the changes. Let me know if you have more questions. D. On Tue, Jan 26, 2016 at 4:13 AM, 李玉珏@163 <18624049...@163.com> wrote: Hi： I found that there was update on the online manual, but the GitHub backup is not updated.What is the reason? Https://github.com/apacheignite/documentation/tree/v1.5 I was through the GitHub document to update the Chinese version of the document, if you do not have this backup, I can not know that the document has been adjusted. 在 16/1/26 01:28, Dmitriy Setrakyan 写道: Hadoop/IGFS documentation is being refactored right now. Could be a side effect of what you were observing. Btw, everyone with login to readme can file a support issue. However, I would not do it yet, while Prachi is still working on refactoring. D. On Mon, Jan 25, 2016 at 6:51 AM, Alexey Kuznetsov < akuznet...@gridgain.com> wrote: Hi! Does someone knows it is possible or not to "sync" left pane with documentation categories and right pane with content of some selected category? For example: https://apacheignite.readme.io/docs/igfs I see some IGFS documentation, but on the left pane I do not see selected category "IGFS", I need to scroll down. This is very annoying when you are reading several related topics - you need to scroll every time. As I know readme.io is a kind of CMS, so who knows how to open an issue for them? Do they have any kind of JIRA / mail list / support forum? -- Alexey Kuznetsov GridGain Systems www.gridgain.com
Proxy serialization issue
Igniters, A end user reported on the issue related to proxy serialization/deserialization https://issues.apache.org/jira/browse/IGNITE-2450 Could someone experienced in marshalling take a look at this? Seems that the original proxy related issue wasn't fully fixed. -- Denis
[GitHub] ignite pull request: ignite-2408
GitHub user ilantukh opened a pull request: https://github.com/apache/ignite/pull/428 ignite-2408 You can merge this pull request into a Git repository by running: $ git pull https://github.com/ilantukh/ignite ignite-2408 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/428.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 #428 commit 62596435dd775b573cbaa71f3ad6c70fcdafebdf Author: Ilya Lantukh Date: 2016-01-27T12:11:38Z ignite-2408 : Simplified and optimized algorithm in GridDhtAtomicCache$DeferredResponseBuffer#addResponse(). --- 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. ---
Re: ignite cache process entry should inject source?
Hi Wei Jiang,
In my understanding you should persuade them to a valid design ;)
--
Denis
On 1/26/2016 4:50 PM, 姜 为 wrote:
Hi Denis,
Yes , I can change the way to do this.
But my business follows MVC paradigm it will be very bloated.
Hope can provide an option to do this.
What do you think so?
Wei Jiang
在 2016年1月26日，下午8:10，Denis Magda 写道：
Hi Wei Jiang,
I've taken look at your code sample and in my understanding you just shouldn't
design an app in a way when a business model object (Entity) incorporates and
performs a business logic (Entity.doSomething()).
Ignite follows MVC paradigm thus there is no sense to inject services into
business model objects.
I would use Entity only for storing actual data and if I it's needed to perform
an operation on an Entity or in general using a service (ExampleService) would
follow one of the below:
- get a reference to an instance of ExampleService 'context.getBean(...)' and
use it if I need to do some operation locally;
- inject a reference into an Ignite Compute closure if I need to run the
computation across the cluster
ignite.compute().broadcast(new ComputeJob());
.
private static class ComputeJobimplements IgniteRunnable {
@SpringResource(resourceName ="exampleService")
private transient ExampleServiceservice;
@Override public void run() {
System.out.println("Executing service from compute");
service.doSomething();
}
}
Hope this helps you.
Denis
On 1/25/2016 4:45 PM, 姜 为 wrote:
Hi Denis,
I create example project https://github.com/wmz7year/ignite-example
.
Please see README file to run example.
Wei Jiang
在 2016年1月23日，上午2:40，Denis Magda 写道：
Hi Wei Jiang,
I would better review your current approach to have better understanding on
what you're trying to implement.
Please share the code. If it's the same as being discussed in "about AOP
development" thread that let me know, I'll take a look there.
--
Denis
On 1/22/2016 10:28 AM, 姜 为 wrote:
Hi Denis,
How about provide an option for this?
Ignite cache user can chose enable or disable inject resources.
Wei Jiang
在 2016年1月22日，下午3:22，Denis Magda 写道：
Hi Wei Jiang,
You can inject @SpringResource and @SpringApplicationContextResource into
Ignite Service or Ignite Compute. This feature is not supported for individual
cache entries, at least because of performance reasons.
@Autowired is unsupported for both Ignite services and computes.
So if you need to process the entries inside of Ignite Compute or Ignite
Service then just inject a resource there using one of the annotations above.
The main point here is that all the nodes have to be started as a part of
spring app context or have to have a reference to it.
Please refer to org.apache.ignite.IgniteSpring for more info.
Regards,
Denis
On 1/22/2016 10:07 AM, 姜 为 wrote:
Hi Denis,
I try to use Ignite cache to store the service object.
The object use Externalizable interface and has a @Autowired field.
When different node use this object, the @Autowired field will be
null,even @SpringResources on the field.
The field like JPA interface , it can’t be serialization.
Wei Jiang
在 2016年1月22日，下午2:58，Denis Magda 写道：
Hi,
Spring resource injection is considered to be used only for Ignite Compute Jobs.
It's quite expensive operation to inject a resource for a CacheEntry cause this
logic will be called for every entry stored in a cache.
Why do you need to inject the resource into a CacheEntry? What do you try to
achieve?
Regards,
Denis
On 1/22/2016 6:26 AM, 姜 为 wrote:
Hi Igniters,
I’m using Ignite cache store objects. The object use Externalizable
interface
to serialization and deserialization.
When object has field use @SpringSource will not inject.
Should add resource inject to Ignite cache?
example :
class Entey implements Externalizable {
@SpringSource(“springSource")
private Service service;
public void read… and write...
}
[jira] [Created] (IGNITE-2469) ODBC: Remove OdbcProtocolHandler.
Vladimir Ozerov created IGNITE-2469: --- Summary: ODBC: Remove OdbcProtocolHandler. Key: IGNITE-2469 URL: https://issues.apache.org/jira/browse/IGNITE-2469 Project: Ignite Issue Type: Sub-task Components: odbc Affects Versions: 1.5.0.final Reporter: Vladimir Ozerov Assignee: Igor Sapego Fix For: 1.6 The only thing this component does is additional complexity. Let's remove it and rework start logic as follows: 1) OdbcProcessor.constructor - instantiate all required components if isOdbcEnabled() == true 2) Remove all unnecessary abstractions like OdbcServer and OdbcTcpListener. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Ignite documentation: keep 1.6 docs in sync with 1.5
Igniters, Some of you have already been working on features that will be available in the next release 1.6 and adding documentation to the doc versioned 1.6. [1] In the same time the community improves docs for version 1.5 (Hadoop + IGFS, queries, etc.). These changes are not reflected automatically in 1.6 docs. Does anybody know an easy way to merge the changes from 1.5 to 1.6 docs? [1] https://apacheignite.readme.io/v1.6 -- Denis
[jira] [Created] (IGNITE-2470) AtomicConfiguration is necessary to add an attribute, similar nodeFilter
liyujue created IGNITE-2470: --- Summary: AtomicConfiguration is necessary to add an attribute, similar nodeFilter Key: IGNITE-2470 URL: https://issues.apache.org/jira/browse/IGNITE-2470 Project: Ignite Issue Type: New Feature Components: data structures Affects Versions: 1.5.0.final Reporter: liyujue Fix For: 1.6 the performance of IgniteAtomicSequence may related to the performance of cache nodes, therefore,AtomicConfiguration is necessary to add an attribute, similar nodeFilter such, let developers control a distributed datastructure cache deployed on the nodes with high performance. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] ignite pull request: IGNITE-2273
GitHub user ilantukh opened a pull request: https://github.com/apache/ignite/pull/429 IGNITE-2273 You can merge this pull request into a Git repository by running: $ git pull https://github.com/ilantukh/ignite ignite-2273 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/429.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 #429 commit 0e6e55bce1567430caf47bfaf7a498f9172031ff Author: Ilya Lantukh Date: 2016-01-27T14:15:41Z ignite-2273 : Alternative to Arrays.asList() optimized for 1 and 2 element arrays. commit 4ec95281af610334296d258d6b8b8d1f533c11e0 Author: Ilya Lantukh Date: 2016-01-27T14:19:47Z ignite-2273 : reverted Arrays.asList() replacement in examples. --- 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-2471) LINQ provider foundation
Pavel Tupitsyn created IGNITE-2471: -- Summary: LINQ provider foundation Key: IGNITE-2471 URL: https://issues.apache.org/jira/browse/IGNITE-2471 Project: Ignite Issue Type: Sub-task Components: interop Affects Versions: 1.1.4 Reporter: Pavel Tupitsyn Assignee: Pavel Tupitsyn Basic query support. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2472) Aggregate functions
Pavel Tupitsyn created IGNITE-2472: -- Summary: Aggregate functions Key: IGNITE-2472 URL: https://issues.apache.org/jira/browse/IGNITE-2472 Project: Ignite Issue Type: Sub-task Components: interop Affects Versions: 1.1.4 Reporter: Pavel Tupitsyn Assignee: Pavel Tupitsyn min, max, sum, count, avg, bool_and, bool_or -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2473) Numeric functions
Pavel Tupitsyn created IGNITE-2473: -- Summary: Numeric functions Key: IGNITE-2473 URL: https://issues.apache.org/jira/browse/IGNITE-2473 Project: Ignite Issue Type: Sub-task Components: interop Affects Versions: 1.1.4 Reporter: Pavel Tupitsyn Assignee: Pavel Tupitsyn http://www.h2database.com/html/functions.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2474) String functions
Pavel Tupitsyn created IGNITE-2474: -- Summary: String functions Key: IGNITE-2474 URL: https://issues.apache.org/jira/browse/IGNITE-2474 Project: Ignite Issue Type: Sub-task Components: interop Affects Versions: 1.1.4 Reporter: Pavel Tupitsyn Assignee: Pavel Tupitsyn http://www.h2database.com/html/functions.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2475) DateTime support and functions
Pavel Tupitsyn created IGNITE-2475: -- Summary: DateTime support and functions Key: IGNITE-2475 URL: https://issues.apache.org/jira/browse/IGNITE-2475 Project: Ignite Issue Type: Sub-task Components: interop Affects Versions: 1.1.4 Reporter: Pavel Tupitsyn Assignee: Pavel Tupitsyn http://www.h2database.com/html/functions.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2478) Field queries (projections)
Pavel Tupitsyn created IGNITE-2478: -- Summary: Field queries (projections) Key: IGNITE-2478 URL: https://issues.apache.org/jira/browse/IGNITE-2478 Project: Ignite Issue Type: Sub-task Components: interop Affects Versions: 1.1.4 Reporter: Pavel Tupitsyn Assignee: Pavel Tupitsyn -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2477) Nested queries
Pavel Tupitsyn created IGNITE-2477: -- Summary: Nested queries Key: IGNITE-2477 URL: https://issues.apache.org/jira/browse/IGNITE-2477 Project: Ignite Issue Type: Sub-task Components: interop Affects Versions: 1.1.4 Reporter: Pavel Tupitsyn Assignee: Pavel Tupitsyn -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2476) Joins and Unions
Pavel Tupitsyn created IGNITE-2476: -- Summary: Joins and Unions Key: IGNITE-2476 URL: https://issues.apache.org/jira/browse/IGNITE-2476 Project: Ignite Issue Type: Sub-task Components: interop Affects Versions: 1.1.4 Reporter: Pavel Tupitsyn Assignee: Pavel Tupitsyn -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2479) Missed continuous query notification when cache listener is used
Denis Magda created IGNITE-2479: --- Summary: Missed continuous query notification when cache listener is used Key: IGNITE-2479 URL: https://issues.apache.org/jira/browse/IGNITE-2479 Project: Ignite Issue Type: Bug Affects Versions: 1.5.0.final Reporter: Denis Magda Assignee: Nikolay Tikhonov Priority: Critical Fix For: 1.6 Attachments: MissingUpdates.java Test attached showcases that an expected notification is missed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2480) Optimization: Typed FieldsQueryCursor
Pavel Tupitsyn created IGNITE-2480: -- Summary: Optimization: Typed FieldsQueryCursor Key: IGNITE-2480 URL: https://issues.apache.org/jira/browse/IGNITE-2480 Project: Ignite Issue Type: Sub-task Components: interop Affects Versions: 1.1.4 Reporter: Pavel Tupitsyn Current FieldsQueryCursor returns untyped IList, after that LINQ provider casts list items to specific types. We should create an alternate cursor that will deserialize values directly as specific types, to avoid boxing and casts. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] ignite pull request: IGNITE-2429: Added examples for the ODBC.
GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/430 IGNITE-2429: Added examples for the ODBC. You can merge this pull request into a Git repository by running: $ git pull https://github.com/isapego/ignite ignite-2429 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/430.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 #430 commit 4b171c9ecf1a1b00a5f2a6f565a4839306fe1e55 Author: isapego Date: 2016-01-22T16:57:07Z IGNITE-2429: Implemented examples for ODBC. Tested for Windows. commit a937ffeaf5e35cf85aef090b26823beb426af821 Author: Igor Sapego Date: 2016-01-22T17:27:43Z IGNITE-2429: Fixes for Autotools build system. commit c4017d249571dadddf66e544a292841e87d85718 Author: Igor Sapego Date: 2016-01-22T18:22:45Z IGNITE-2429: Fix for ODBC-driver autotools build system. commit bc5a70c0194c57a9ed7bcb893851c0845f49b6f3 Author: Igor Sapego Date: 2016-01-22T18:28:13Z IGNITE-2429: Fix for ODBC test build system. commit a156539ae597ae942c6ef22ea93208905e5c6941 Author: isapego Date: 2016-01-26T14:52:31Z Merge branch 'ignite-1786-review' into ignite-2429 commit e0c3c9d58bd4f37a60e30a67b69e817731e5347c Author: isapego Date: 2016-01-26T15:23:34Z IGNITE-2429: Put-Get example moved to separate folder. commit 8ee39220a30a8a43ad5688d9aab622f230fdaaac Author: isapego Date: 2016-01-26T15:29:31Z IGNITE-2429: Examples projects structure changed commit 452f637c151a070570dddea71c846c9ac5c9133f Author: isapego Date: 2016-01-27T15:10:15Z IGNITE-2429: Implemented simple ODBC example with single type. commit 51c7d8b5321b45b0e68f473dad47f300b44b909b Author: isapego Date: 2016-01-27T15:19:13Z IGNITE-2429: Moved common types to examples-wide include directory. commit 705094ce582370a9faf67636fe9fd7af8b156f2b Author: isapego Date: 2016-01-27T15:54:50Z IGNITE-2429: ODBC example contains 2 types now. commit 2d59cc23039815c795d3a517e07e81d17bc7f33a Author: isapego Date: 2016-01-27T16:04:15Z IGNITE-2429: Added more people to Person cache. commit e3bf0c6e80d8457e1c36d42d8ff8a83c4a326826 Author: isapego Date: 2016-01-27T16:28:25Z IGNITE-2429: Added instruction to the top of ODBC example. commit 381fc4b41153ad6b818a468ab61170cd7ee948bd Author: isapego Date: 2016-01-27T16:34:42Z Merge branch 'ignite-1786' into ignite-2429 --- 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. ---
Re: Ignite documentation: keep 1.6 docs in sync with 1.5
There is no easy way other than the same old copy-n-paste. To my knowledge, readme team is working on automating this process. D. On Wed, Jan 27, 2016 at 4:25 AM, Denis Magda wrote: > Igniters, > > Some of you have already been working on features that will be available > in the next release 1.6 and adding documentation to the doc versioned 1.6. > [1] > > In the same time the community improves docs for version 1.5 (Hadoop + > IGFS, queries, etc.). These changes are not reflected automatically in 1.6 > docs. > > Does anybody know an easy way to merge the changes from 1.5 to 1.6 docs? > > [1] https://apacheignite.readme.io/v1.6 > > -- > Denis >
affinityRun() and affinityCall() (JIRA ticket)
Hello, I am playing with https://issues.apache.org/jira/browse/IGNITE-1144 as introduction to hacking on Ignite. I am not a Java developer by day but have experience writing code in various languages. This is my first in-depth exposure to Ignite internals (have lightly used it as a user in a POC project). Looking at this ticket, I am guessing that what it needs to do is get the cache name from the kernel context. After that it can just pass on the call (such as affinityRun()) to the regular affinityRun() call with the cache name filled in as the first parameter. This is because an internal (un-exposed) cache is used to track the queue/set data structures. Is this all correct? My question is: how do I get the cache name from within the queue implementation. Thanks!
Check list for test implementation
Guys, While reviewing tests and production code we often see that developers do not add full test set to entirely cover all the aspects of a new feature or a fix. So, it seems to be very handy to have some kind of checklist for contributors and reviewers to follow. Here is the link - https://cwiki.apache.org/confluence/display/IGNITE/Implementing+Tests. Comments and suggestions are welcome. --Yakov
[GitHub] ignite pull request: IGNITE-2465: Assertion in load cache closure ...
GitHub user ashutakGG opened a pull request: https://github.com/apache/ignite/pull/431 IGNITE-2465: Assertion in load cache closure (a race fixed) https://issues.apache.org/jira/browse/IGNITE-2465. You can merge this pull request into a Git repository by running: $ git pull https://github.com/ashutakGG/incubator-ignite ignite-2465-closure Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/431.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 #431 commit 77894309934ee062d7b6459b1aae7618d2dc441f Author: ashutak Date: 2016-01-27T15:11:50Z ignite-2465: add test commit a7f53fef46f538de10119699212f35b1259f1f4d Author: ashutak Date: 2016-01-27T17:36:46Z ignite-2465: fix commit c736aaba062e9b6794d0ccba7e565428e31e5e17 Author: ashutak Date: 2016-01-27T17:39:18Z ignite-2465: revert test changes --- 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. ---
Re: MyBatis and Apache Ignite integration
Hi Denis, and people from the ignite project.
I have just created an empty project at Github for the integration:
https://github.com/mybatis/ignite-cache
As we spoke before, the interface is really simple. Probably we may have
gone too far with the simplicity because some things need to be explained.
The cache adapter just needs to implement the Cache interface:
https://github.com/mybatis/ignite-cache/blob/master/src/main/java/org/mybatis/caches/ignite/IgniteCache.java
One instance of this class is created for each namespace. The namespace is
an String received as a paremeter to the constructor:
public IgniteCache(String id) {
super();
this.id = id;
}
The namespace is just a set of statatements. They are held in the same
mapper xml file or in the same mapper interface. From the cache
perspective, all the statements in a namespace have only one thing in
common: they are flushed all together and share the same properties (like
eviction policy, size...)
There is no special method to bootstrap the underlying cache system so this
has to be done in an static block. See the Redis cache adapter for an
example:
https://github.com/mybatis/redis-cache/blob/master/src/main/java/org/mybatis/caches/redis/RedisCache.java
Properties are read from the cache elament and passed to any setter method
in the adapter class. The code is here:
https://github.com/mybatis/mybatis-3/blob/master/src/main/java/org/apache/ibatis/mapping/CacheBuilder.java
Hope this basic info is enough to start.
Apart from that... the only condition is that any code contributed will be
licensed under the Apache License 2.0 which I suppose that is not going to
be a problem ;)
And that we can start with pull requests but have no problem at all in
giving direct commit rights to the creator (or creators) of the plugin.
Regards.
2016-01-25 17:16 GMT+01:00 Denis Magda :
> HI All,
>
> I've opened an Ignite ticket with tasks description [1]
>
> Is there anyone in Apache Ignite community who is interested in this kind
> of work and will be able to complete it in the nearest couple of weeks?
>
> [1] https://issues.apache.org/jira/browse/IGNITE-2448
>
> Regards,
> Denis
>
>
> On 1/23/2016 11:28 AM, dma...@gridgain.com wrote:
>
> Hi Eduardo,
>
> It's nice to hear from you! Thanks the help and details!
>
> Absolutely agree with you that the interface is straightforward and I
> don't see any difficulties that can arise during its implementation.
> I'll open an Apache Ignite JIRA ticket soon describing the integration
> details and hope that someone from Ignite community will pick it up the
> next week starting working on the plugin.
>
> As per the hosting I would host everything on MyBatis GitHub repo as it is
> already done for other plugins and in addition would add a documentation to
> Apache Ignite [1]. This way both MyBatis and Ignite community will be aware
> about the integration and we don't need to host the plugin in different
> repos.
>
> I've copied Ignite dev community to the discussion - dev@ignite.apache.org.
> So please make sure that this dev list is copied when you reply ;)
>
> If someone else from either MyBatis or Ignite community has any thoughts
> on this topic please share.
>
> [1] https://apacheignite.readme.io
>
> Regards,
> Denis
>
> On Saturday, January 23, 2016 at 12:46:08 AM UTC+3, Eduardo wrote:
>>
>> Hi Denis,
>>
>> First of all. Wellcome to the list!
>>
>> AFAIK all the cache integration plugins have been developed by ourselves.
>> The interface is quite easy so the task is usualy pretty straight forward.
>>
>> I will be very happy to help with the integration! I would suggest
>> creating a new repo and work on it. Probably it will be better that that
>> someone from the Ignite project builds the plugin and we provide
>> information about how the interface works.
>>
>> Regarding the future hosting, I suppose there will be no problem in
>> hosting the new project at our home in Github but is also perfect that you
>> host it as part of the ignite project. No problem at all with any option!
>>
>> Looking forward to starting! :)
>>
>> 2016-01-21 10:30 GMT+01:00 :
>>
>>> Hi MyBatis community!
>>>
>>> I'm a committer and PMC of Apache Ignite [1] project and writing to you
>>> on behalf of our community (+ CC-ed) to discuss an integration between our
>>> projects that should be useful for both sides.
>>>
>>> In short, Apache Ignite is a high-performance, integrated and
>>> distributed in-memory platform for computing and transacting on large-scale
>>> data sets in real-time, orders of magnitude faster than possible with
>>> traditional disk-based or flash technologies.
>>> Inside of our community we see a growing interest in a field of usage
>>> MyBatis along with Apache Ignite. There are use cases when developers/users
>>> wants to use Apache Ignite as MyBatis second level cache. Since such an
>>> interest is growing constantly we think that it's a right time to make this
>>> happen.
>>>
>>> As I see MyBatis already s
Re: affinityRun() and affinityCall() (JIRA ticket)
Hi, Both GridCacheQueueAdapter and GridCacheSetImpl have a reference to GridCacheContext which represents the underlying cache for the data structure. GridCacheContext.name() will give you the correct cache name that you can use when calling affinityRun method. -Val On Wed, Jan 27, 2016 at 9:13 AM, Dood@ODDO wrote: > Hello, > > I am playing with https://issues.apache.org/jira/browse/IGNITE-1144 as > introduction to hacking on Ignite. I am not a Java developer by day but > have experience writing code in various languages. This is my first > in-depth exposure to Ignite internals (have lightly used it as a user in a > POC project). > > Looking at this ticket, I am guessing that what it needs to do is get the > cache name from the kernel context. After that it can just pass on the call > (such as affinityRun()) to the regular affinityRun() call with the cache > name filled in as the first parameter. This is because an internal > (un-exposed) cache is used to track the queue/set data structures. Is this > all correct? > > My question is: how do I get the cache name from within the queue > implementation. > > Thanks! > > > >
Re: affinityRun() and affinityCall() (JIRA ticket)
Hi, We should assign the ticket to you. Can you please send your Jira username here (you can create one)? This way I will add you to a list of Ignite contributors in Jira and assign the ticket to you. D. On Wed, Jan 27, 2016 at 9:13 AM, Dood@ODDO wrote: > Hello, > > I am playing with https://issues.apache.org/jira/browse/IGNITE-1144 as > introduction to hacking on Ignite. I am not a Java developer by day but > have experience writing code in various languages. This is my first > in-depth exposure to Ignite internals (have lightly used it as a user in a > POC project). > > Looking at this ticket, I am guessing that what it needs to do is get the > cache name from the kernel context. After that it can just pass on the call > (such as affinityRun()) to the regular affinityRun() call with the cache > name filled in as the first parameter. This is because an internal > (un-exposed) cache is used to track the queue/set data structures. Is this > all correct? > > My question is: how do I get the cache name from within the queue > implementation. > > Thanks! > > > >
Re: Proxy serialization issue
Who was originally responsible for fixing the Proxy serialization issue? On Wed, Jan 27, 2016 at 4:07 AM, Denis Magda wrote: > Igniters, > > A end user reported on the issue related to proxy > serialization/deserialization > https://issues.apache.org/jira/browse/IGNITE-2450 > > Could someone experienced in marshalling take a look at this? Seems that > the original proxy related issue wasn't fully fixed. > > -- > Denis > > >
Re: Check list for test implementation
Great start in improving the quality of JUnit testing in Ignite. It would be much better to put it in a table format, rather than list. I think, given the breadth of the tests listed, it will be almost impossible to follow this list for every fix or feature. Instead, we should provide an automatic test harness which will go through all the topology, memory, deployment, and other config property permutations and run all these tests automatically. Until we do, however, all the new functionality should be tested based on this list. Thoughts? D. On Wed, Jan 27, 2016 at 9:39 AM, Yakov Zhdanov wrote: > Guys, > > While reviewing tests and production code we often see that developers do > not add full test set to entirely cover all the aspects of a new feature or > a fix. So, it seems to be very handy to have some kind of checklist for > contributors and reviewers to follow. Here is the link - > https://cwiki.apache.org/confluence/display/IGNITE/Implementing+Tests. > Comments and suggestions are welcome. > > --Yakov >
Re: affinityRun() and affinityCall() (JIRA ticket)
On 1/27/2016 5:33 PM, Dmitriy Setrakyan wrote: Hi, We should assign the ticket to you. Can you please send your Jira username here (you can create one)? This way I will add you to a list of Ignite contributors in Jira and assign the ticket to you. D. Dmitriy, username is "maketo". Thanks!
Re: affinityRun() and affinityCall() (JIRA ticket)
On Wed, Jan 27, 2016 at 4:36 PM, Dood@ODDO wrote: > On 1/27/2016 5:33 PM, Dmitriy Setrakyan wrote: > >> Hi, >> >> We should assign the ticket to you. Can you please send your Jira username >> here (you can create one)? This way I will add you to a list of Ignite >> contributors in Jira and assign the ticket to you. >> >> D. >> > > Dmitriy, username is "maketo". Thanks! > Apache Jira is telling me that there is no such user. Did you create an account?
[jira] [Created] (IGNITE-2481) On the signup page add the following fields: Company, Country.
Andrey Novikov created IGNITE-2481: -- Summary: On the signup page add the following fields: Company, Country. Key: IGNITE-2481 URL: https://issues.apache.org/jira/browse/IGNITE-2481 Project: Ignite Issue Type: Sub-task Reporter: Andrey Novikov Assignee: Andrey Novikov Priority: Minor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2482) Unsaved changes confirmation partially does not work
Alexey Kuznetsov created IGNITE-2482: Summary: Unsaved changes confirmation partially does not work Key: IGNITE-2482 URL: https://issues.apache.org/jira/browse/IGNITE-2482 Project: Ignite Issue Type: Sub-task Reporter: Alexey Kuznetsov Assignee: Dmitriyff # Add new cluster # Save it # Change name and click another link or [Clone] Expected Dialog with warning about unsaved changes should be shown. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2483) Cache metrics bugs
Valentin Kulichenko created IGNITE-2483: --- Summary: Cache metrics bugs Key: IGNITE-2483 URL: https://issues.apache.org/jira/browse/IGNITE-2483 Project: Ignite Issue Type: Bug Components: cache Reporter: Valentin Kulichenko Fix For: 1.6 User list discussion: http://apache-ignite-users.70518.x6.nabble.com/Is-there-a-way-to-get-cache-metrics-for-all-the-nodes-in-cluster-combined-td2674.html Currently there are at least three issues with cache metrics: # When metrics are acquired on client, average put times are always zero. This happens because timings are calculated on the client, but puts are counted on servers. # Size and keySize are always zero even if cache is not empty. # Default metrics() method that doesn't take a cluster group provides metrics for local node only. So if it's called on client, they are always empty. It should calculate metrics for the whole cluster instead. Also looks like this code is very undertested. Coverage should be significantly improved. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: affinityRun() and affinityCall() (JIRA ticket)
On Wed, Jan 27, 2016 at 5:48 PM, Dmitriy Setrakyan wrote: > > > On Wed, Jan 27, 2016 at 4:36 PM, Dood@ODDO wrote: > >> On 1/27/2016 5:33 PM, Dmitriy Setrakyan wrote: >> >>> Hi, >>> >>> We should assign the ticket to you. Can you please send your Jira >>> username >>> here (you can create one)? This way I will add you to a list of Ignite >>> contributors in Jira and assign the ticket to you. >>> >>> D. >>> >> >> Dmitriy, username is "maketo". Thanks! >> > > Apache Jira is telling me that there is no such user. Did you create an > account? > Worked now. The ticket is assigned to you.
[jira] [Created] (IGNITE-2484) Performance: Cache compiled queries
Pavel Tupitsyn created IGNITE-2484: -- Summary: Performance: Cache compiled queries Key: IGNITE-2484 URL: https://issues.apache.org/jira/browse/IGNITE-2484 Project: Ignite Issue Type: Sub-task Components: interop Affects Versions: 1.1.4 Reporter: Pavel Tupitsyn Investigate SQL generation overhead and whether it is needed to cache "compiled" queries. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2485) tem.swapSpaceSpi[swapKind] is undefined
Pavel Konstantinov created IGNITE-2485:
--
Summary: tem.swapSpaceSpi[swapKind] is undefined
Key: IGNITE-2485
URL: https://issues.apache.org/jira/browse/IGNITE-2485
Project: Ignite
Issue Type: Sub-task
Reporter: Pavel Konstantinov
Assignee: Alexey Kuznetsov
{code}
14:55:30.884 Error: item.swapSpaceSpi[swapKind] is undefined
validate@https://staging-console.gridgain.com/all.js:1441:21
$scope.saveItem@https://staging-console.gridgain.com/all.js:1515:21
anonymous/fn@https://staging-console.gridgain.com/app.min.js line 92971 >
Function:2:450
ngEventHandler/https://staging-console.gridgain.com/app.min.js:96719:21
$RootScopeProvider/this.$gethttps://staging-console.gridgain.com/app.min.js:94583:22
$RootScopeProvider/this.$gethttps://staging-console.gridgain.com/app.min.js:94606:26
ngEventHandler/<@https://staging-console.gridgain.com/app.min.js:96724:21
jQuery.event.dispatch@https://staging-console.gridgain.com/app.min.js:126814:25
jQuery.event.add/elemData.handle@https://staging-console.gridgain.com/app.min.js:126685:91
1 app.min.js:92177:24
consoleLog/<() app.min.js:92177
$ExceptionHandlerProvider/this.$get
