[jira] [Created] (IGNITE-3037) we need to enable read-through or write-through if cache generated during importing model from DB

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-3037:
--

 Summary: we need to enable read-through or write-through if cache 
generated during importing model from DB
 Key: IGNITE-3037
 URL: https://issues.apache.org/jira/browse/IGNITE-3037
 Project: Ignite
  Issue Type: Sub-task
Reporter: Pavel Konstantinov


In case when cache created from a template which doesn't have these properties 
enabled we must enable at least one of its.



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

[jira] [Created] (IGNITE-3036) We need to set red border to empty mandatory fields after Save

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-3036:
--

 Summary: We need to set red border to empty mandatory fields after 
Save
 Key: IGNITE-3036
 URL: https://issues.apache.org/jira/browse/IGNITE-3036
 Project: Ignite
  Issue Type: Sub-task
Reporter: Pavel Konstantinov






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

Re: Hello

[Alexey Kuznetsov]

Hello, Juan!

Welcome to Apache Ignite!

You could start from reading docs and running examples.
After that you could start from easy tasks.

More info is here:
https://ignite.apache.org/community/contribute.html#contribute

Looking forward for your contribution.


On Thu, Apr 21, 2016 at 10:34 AM, Juan Carlos Fiorenzano <
jcfiorenzan...@gmail.com> wrote:

> Hello community I want to contribute in the Ignite project, I would like to
> begin with the easier issues and while I get used to the project I will
> increase the complexity of the tasks.
>
> Thank you in advance
>



-- 
Alexey Kuznetsov
GridGain Systems
www.gridgain.com

Hello

[Juan Carlos Fiorenzano]

Hello community I want to contribute in the Ignite project, I would like to
begin with the easier issues and while I get used to the project I will
increase the complexity of the tasks.

Thank you in advance

Local updates to cache on backup node in FULL_ASYNC mode

[Alexei Scherbakov]

Hello,

I tried the following:
Started two server nodes.
Created a cache in ATOMIC, REPLICATED, FULL_ASYNC modes
>From the client deployed a service on backup node for that cache.
In the service I executed the code:
put(key, val); // val is not null
V v = get(key);
and got v equal to null (not suprising)
But javadoc for FULL_ASYNC mode states:
"remote nodes may get their state updated a bit after any of the cache
write methods complete"
>From the user point of view this update is local, so it might be confusing.
Should we do anything about it?


-- 

Best regards,
Alexei Scherbakov

Re: Documentation for Deployment Modes and Resource Injection

[Prachi Garg]

Any update, guys?

-Prachi

On Mon, Apr 11, 2016 at 3:15 PM, Prachi Garg  wrote:

> Hello engineers,
>
> I have added documentation on readme.io for Deployment Modes[1] and
> Resource Injection[2]. Can some one please review the content and verify
> its correctness?
> Currently these pages are hidden/private, and will not show up on the
> sidebar. Once reviewed, you ( or I) can make it public.
>
> [1] https://apacheignite.readme.io/v1.5/docs/deployment-modes
> [2] https://apacheignite.readme.io/v1.5/docs/resource-injection
>
> Thanks,
> -Prachi
>

[jira] [Created] (IGNITE-3035) Recent JDBC discovery changes cause errors for Postgres and Microsoft SQL Server databases

[Peter Griffiths (JIRA)]

Peter Griffiths created IGNITE-3035:
---

 Summary: Recent JDBC discovery changes cause errors for Postgres 
and Microsoft SQL Server databases
 Key: IGNITE-3035
 URL: https://issues.apache.org/jira/browse/IGNITE-3035
 Project: Ignite
  Issue Type: Bug
  Components: SQL
Affects Versions: 1.6
Reporter: Peter Griffiths


The changes introduced by IGNITE-1993 to the TcpDiscoveryJdbcIpFinder  class to 
introduce Oracle compatibility cause errors when Postgres or Microsoft SQL 
Server are used as the database.  No such issues were encountered using either 
database before.

The first node to join a grid succeeds and creates the IP table in the 
database, but any further node attempting to join the grid throws the following 
error (for Postgres):
{code}
Failed to register local node address in IP finder on start (retrying every 
2000 ms).: class org.apache.ignite.spi.IgniteSpiException: Failed to initialize 
DB schema.
...
Caused by: org.postgresql.util.PSQLException: ERROR: current transaction is 
aborted, commands ignored until end of transaction block
{code}

The same behaviour occurs when using Microsoft SQL Server, but it throws a 
different error.



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

[GitHub] ignite pull request: IGNITE-2383

[vldpyatkov]

GitHub user vldpyatkov opened a pull request:

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

IGNITE-2383

Non-string system properties should be ignored in node attributes and 
update checker

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

$ git pull https://github.com/vldpyatkov/ignite ignite-2383

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

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


commit a810a8e914c070dc65a4889025dfba2ac10b3445
Author: vdpyatkov 
Date:   2016-04-20T14:25:36Z

IGNITE-2383
Non-string system properties should be ignored in node attributes and 
update checker




---
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-3019 Implement config variations test ...

[tledkov-gridgain]

GitHub user tledkov-gridgain opened a pull request:

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

 IGNITE-3019  Implement config variations test for IgniteCompute

IGNITE-3019 Implement config variations test for IgniteCompute

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

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

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

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


commit 3e0fdceb3c8512689e34dc101b687e3e537c686c
Author: tledkov-gridgain 
Date:   2016-04-19T15:42:24Z

IGNITE-3019 Implement config variations test for IgniteCompute

commit 3e6274da0b2ad517763792d009d2cb132788708c
Author: tledkov-gridgain 
Date:   2016-04-20T10:50:00Z

IGNITE-3019 add tests for call and affinityCall

commit 3fb06ae0722ad288fe608a19e6943f1175c83987
Author: tledkov-gridgain 
Date:   2016-04-20T10:53:04Z

Merge branch 'master' of https://github.com/gridgain/apache-ignite into 
ignite-3019




---
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-3034) Domain model for SQL query: Undo button not hide after undo

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-3034:
--

 Summary: Domain model for SQL query: Undo button not hide after 
undo
 Key: IGNITE-3034
 URL: https://issues.apache.org/jira/browse/IGNITE-3034
 Project: Ignite
  Issue Type: Sub-task
Reporter: Pavel Konstantinov
Assignee: Alexey Kuznetsov


the button is hidden only on the second click



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

[jira] [Created] (IGNITE-3033) Domain model for SQL query: Name field and Type field do not have red border and triangle in case of invalid value

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-3033:
--

 Summary: Domain model for SQL query: Name field and Type field do 
not have red border and triangle in case of invalid value
 Key: IGNITE-3033
 URL: https://issues.apache.org/jira/browse/IGNITE-3033
 Project: Ignite
  Issue Type: Sub-task
Reporter: Pavel Konstantinov
Assignee: Alexey Kuznetsov


Name field = 7
Type field = !!!



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

[jira] [Created] (IGNITE-3032) 'Domain model for SQL query' section doesn't expand if 'Fields' contains invalid field

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-3032:
--

 Summary: 'Domain model for SQL query' section doesn't expand if 
'Fields' contains invalid field
 Key: IGNITE-3032
 URL: https://issues.apache.org/jira/browse/IGNITE-3032
 Project: Ignite
  Issue Type: Sub-task
Reporter: Pavel Konstantinov
Assignee: Alexey Kuznetsov


1) expand the 'Domain model for SQL query' section
2) set invalid type for field
3) collapse the section
4) click Save



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

[jira] [Created] (IGNITE-3031) 'Domain model for SQL query' section shows the old values for new Type

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-3031:
--

 Summary: 'Domain model for SQL query' section shows the old values 
for new Type
 Key: IGNITE-3031
 URL: https://issues.apache.org/jira/browse/IGNITE-3031
 Project: Ignite
  Issue Type: Sub-task
Reporter: Pavel Konstantinov
Assignee: Alexey Kuznetsov


1) import some types from DB
2) remove all
3) add new type

observed:
'Domain model for SQL query' section shows the old values for new Type



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

[jira] [Created] (IGNITE-3030) Add missing properties to configuration

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-3030:


 Summary: Add missing properties to configuration
 Key: IGNITE-3030
 URL: https://issues.apache.org/jira/browse/IGNITE-3030
 Project: Ignite
  Issue Type: Sub-task
Reporter: Alexey Kuznetsov
 Fix For: 1.6


1. userAttributes
2. failoverSpi
3. gridLogger

See 
http://apache-ignite-users.70518.x6.nabble.com/How-to-auto-generate-spring-configuration-file-td4284.html



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

[jira] [Created] (IGNITE-3029) Web console should generate fields aliases with database names.

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-3029:


 Summary: Web console should generate fields aliases with database 
names.
 Key: IGNITE-3029
 URL: https://issues.apache.org/jira/browse/IGNITE-3029
 Project: Ignite
  Issue Type: Sub-task
  Components: wizards
Affects Versions: 1.6
Reporter: Alexey Kuznetsov
Assignee: Alexey Kuznetsov






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

[jira] [Created] (IGNITE-3028) Schema Import Utility should generate fields aliases with database names.

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-3028:


 Summary: Schema Import Utility should generate fields aliases with 
database names.
 Key: IGNITE-3028
 URL: https://issues.apache.org/jira/browse/IGNITE-3028
 Project: Ignite
  Issue Type: Task
  Components: wizards
Reporter: Alexey Kuznetsov






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