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