[jira] [Created] (IGNITE-3276) Develop Cloudera Service Descriptor for PnP integration with Cloudera Manager.

[Nikita Ivanov (JIRA)]

Nikita Ivanov created IGNITE-3276:
-

 Summary: Develop Cloudera Service Descriptor for PnP integration 
with Cloudera Manager.
 Key: IGNITE-3276
 URL: https://issues.apache.org/jira/browse/IGNITE-3276
 Project: Ignite
  Issue Type: New Feature
  Components: hadoop
Affects Versions: 1.6
Reporter: Nikita Ivanov


Several people expressed an idea of PnP integration with Cloudera via CSR: 
https://blog.cloudera.com/blog/2014/04/how-to-extend-cloudera-manager-with-custom-service-descriptors/

Sounds like a great feature when running within Cloudera YARN.



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

Re: IgniteRDD type mapping

[Alexey Goncharuk]

Taras,

According to IgniteRDD non-predefined types (including Object) are mapped
to StructType with no fields, which should be recognizable by Spark. Can
you explain why MatchError happens?
​

[GitHub] ignite pull request #786: IGNITE-1629 .Net: Introduce native logging facilit...

[ptupitsyn]

GitHub user ptupitsyn opened a pull request:

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

IGNITE-1629 .Net: Introduce native logging facility.



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

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

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

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


commit 649203a12a6e92732381aa726e091befb9a3ad79
Author: Pavel Tupitsyn 
Date:   2016-06-07T14:47:33Z

IGNITE-1629 .Net: Introduce native logging facility.

commit a882f23a6d292eb4881642e10d02358752a0fcdc
Author: Pavel Tupitsyn 
Date:   2016-06-07T15:20:31Z

wip

commit 0d1545cfe30c9227e2a445b0453481fedab59f11
Author: Pavel Tupitsyn 
Date:   2016-06-07T16:07:44Z

wip

commit 68448e5c0c23e040fe5a751d3946aaf83e73e055
Author: Pavel Tupitsyn 
Date:   2016-06-07T16:15:28Z

wip C#

commit 99c3be4f38e2b9f9010dc2ff3dd22aeeefc51b9a
Author: Pavel Tupitsyn 
Date:   2016-06-07T16:29:24Z

wip

commit 246779d721816299c8ced48cb34b25d4593905ad
Author: Pavel Tupitsyn 
Date:   2016-06-07T16:34:37Z

wip

commit 20d37ca0c91030539dc9083d299b507d854d84c0
Author: Pavel Tupitsyn 
Date:   2016-06-07T16:55:40Z

wip

commit 54f6b8b313cd4b0cc6296194aed437a513b0be99
Author: Pavel Tupitsyn 
Date:   2016-06-08T09:53:47Z

wip

commit 6470b49c361c2c0d35bf1b5566971154442c0e7a
Author: Pavel Tupitsyn 
Date:   2016-06-08T09:57:03Z

wip

commit 81a83121f19701a32506e75fb8a790a7315173f2
Author: Pavel Tupitsyn 
Date:   2016-06-08T10:05:53Z

wip

commit 7aac8f6376a9914447b00db9fda14bc3d4c3ea2f
Author: Pavel Tupitsyn 
Date:   2016-06-08T10:41:34Z

wip

commit cc5d487ae81646e5afddf10e622b1864568fab79
Author: Pavel Tupitsyn 
Date:   2016-06-08T11:00:11Z

wip

commit 7445d83c266ea29e1441ffc34f98e4266980dfa2
Author: Pavel Tupitsyn 
Date:   2016-06-08T11:46:44Z

wip

commit f508bf55008296bfe7d3b204b3f4e3274d0a6eea
Author: Pavel Tupitsyn 
Date:   2016-06-08T11:49:27Z

wip

commit 1cddb1a4ef65852d49930990652c5484679577e7
Author: Pavel Tupitsyn 
Date:   2016-06-08T11:53:59Z

wip

commit 13d73e281ff92aba9e46de6b96f18d824070a197
Author: Pavel Tupitsyn 
Date:   2016-06-08T11:56:26Z

wip

commit dba27541301016ccbf6445b3813217cbde3ef64c
Author: Pavel Tupitsyn 
Date:   2016-06-08T11:57:46Z

wip

commit b5761a5578c703c60f2066b8d5459ec83dda91cd
Author: Pavel Tupitsyn 
Date:   2016-06-08T12:19:05Z

ConsoleLogger implemented

commit bbda4ef50b1696670f26373dca9b40818d6e0ad8
Author: Pavel Tupitsyn 
Date:   2016-06-08T12:24:41Z

wip

commit 2d56c88ee4389dee9728ef2b8afa1bd9ee9750c6
Author: Pavel Tupitsyn 
Date:   2016-06-08T12:28:51Z

wip

commit 1ee78904004909b080648a5a979d3dae4b080511
Author: Pavel Tupitsyn 
Date:   2016-06-08T12:33:48Z

wip

commit e04b3564e200dff9176b43fb765143faa1fa2ae8
Author: Pavel Tupitsyn 
Date:   2016-06-08T12:34:33Z

wip

commit 789560702f56c0e121d2ab7751d5600f34a49109
Author: Pavel Tupitsyn 
Date:   2016-06-08T12:52:22Z

wip

commit 3ec2688ec609c6be06cdbc77cdc58a623da1600f
Author: Pavel Tupitsyn 
Date:   2016-06-08T13:21:58Z

wip callbacks

commit 8ac78e202f07d466dada70274a8c968c7cea0ae7
Author: Pavel Tupitsyn 
Date:   2016-06-08T13:23:46Z

wip callbacks

commit 1345aa93542c01dec123e2faaa520ec82e153089
Author: Pavel Tupitsyn 
Date:   2016-06-08T13:36:52Z

Java callbacks done

commit 50323054e129985f697d1661fec3e701459895ab
Author: Pavel Tupitsyn 
Date:   2016-06-08T14:07:10Z

wip

commit ec21d607ffa78a1c958f2593a0c77e22911950d7
Author: Pavel Tupitsyn 
Date:   2016-06-08T14:07:53Z

Callback in Java done

commit 713dd4c2f25d075754dd268b53c9f33125c44c45
Author: Pavel Tupitsyn 
Date:   2016-06-08T14:15:23Z

Fix jbool result

commit 2022532ee36e6fe88d2aa642369b9674fe7f99d9
Author: Pavel Tupitsyn 
Date:   2016-06-08T14:19:28Z

fix callback exports




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

[GitHub] ignite pull request #785: [IGNITE-3221] Bad ip used , when fixed ip in hostn...

[sebadiaz]

GitHub user sebadiaz opened a pull request:

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

[IGNITE-3221] Bad ip used , when fixed ip in hostname

The target is to set the ip written in a string format instead to call the 
DNS to resolve it. 

DNS could not be well working in some case and the IP is the more clear 
connection that we can make

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

$ git pull https://github.com/sebadiaz/ignite master

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

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


commit 266a2dd9725eaa5251a6fce876745ee4080b3dfb
Author: Sebastien Diaz 
Date:   2016-06-08T11:36:47Z

IGNITE-3221 check IP and convert it

commit 26443bf41e4a8acb031054c5c295be22b6921102
Author: Sebastien Diaz 
Date:   2016-06-08T11:37:50Z

IGNITE-3221 check IP and convert it

commit f3bdc95f8a507d26e6b7ca598a609f77f9609fba
Author: Sebastien Diaz 
Date:   2016-06-08T11:39:51Z

IGNITE-3221 check IP and convert it

commit 0d1091e9ad7b8cee9f1078171a6e8362d8731f1f
Author: Sebastien Diaz 
Date:   2016-06-08T11:42:49Z

IGNITE-3221 check IP and convert it

commit 9f357d020e64b7374d47593bc35dc57d685f87f1
Author: Sebastien Diaz 
Date:   2016-06-08T11:43:54Z

IGNITE-3221 check IP and convert it




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

Fwd: ignite cache get performance issue when Key, Value not exist

[Denis Magda]

Igniters,

This is not the first time I hear about from the community side about the 
performance issue Kevin is talking below.

In short if a key is not located in a cache then we will go to an underlying 
storage. This process will be repeated all the time for the same key and this 
leads to performance degradation in cases when someone needs to check whether a 
key exists before applying an action.

Probably we can use already existed remove queue to cache such queries of non 
existed keys. Any thoughts & ideas?

—
Denis

> Begin forwarded message:
> 
> From: Zhengqingzheng 
> Subject: ignite cache get performance issue when Key, Value not exist 
> Date: June 8, 2016 at 6:26:17 AM GMT+3
> To: "u...@ignite.apache.org" 
> Reply-To: u...@ignite.apache.org
> 
> Hi there,
> When I am using cache.get(key) operation to find some value.
> I notice that if the key is not exist (neither no record in the database 
> too), the performance is really slow: about 830ms to return the null result;
> BTW, I have set read through and write-behind for this cache, also I add near 
> cache configurations when create this cache.
>  
> Is it a bug?
>  
> Cheers,
> Kevin

[jira] [Created] (IGNITE-3274) Hadoop: NPE when mappings are not set in BasicUserNameMapper.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-3274:
---

 Summary: Hadoop: NPE when mappings are not set in 
BasicUserNameMapper.
 Key: IGNITE-3274
 URL: https://issues.apache.org/jira/browse/IGNITE-3274
 Project: Ignite
  Issue Type: Bug
  Components: hadoop
Affects Versions: 1.6
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
 Fix For: 1.7


We simply forgot null check there.



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

[GitHub] ignite pull request #784: IgniteRDD type mapping: add the test for StructFie...

[tledkov-gridgain]

GitHub user tledkov-gridgain opened a pull request:

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

IgniteRDD type mapping: add the test for StructField



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

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

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

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


commit 13a53275e454b1dfbe2f9c542356a5357b07ca2f
Author: tledkov-gridgain 
Date:   2016-06-08T07:56:47Z

IgniteRDD type mapping: add the test for StructField




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