Pavel Konstantinov created IGNITE-7658:
--
Summary: visorcmd: add ability to get configuration of certain
cache
Key: IGNITE-7658
URL: https://issues.apache.org/jira/browse/IGNITE-7658
Project:
Hello, Dmitriy.
IGNITE-7337 are merged to master [1]
Do I need to do something more to include this feature into 2.4. release?
[1]
https://github.com/apache/ignite/commit/7c01452990ad0de0fb84ab4c0424a6d71e5bccba
В Ср, 07/02/2018 в 11:26 -0800, Dmitriy Setrakyan пишет:
> Agree on both, the
Hello, Igniters.
Good news.
IGNITE-7337 [1](Spark Data Frames: support saving a data frame in Ignite) are
merged to master.
For now we can both - read from and write to Ignite SQL table with Data Frame
API.
Big thanks to Valentin Kulichenko for a quick review.
So it seems we can include this
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3438
---
GitHub user gg-shq opened a pull request:
https://github.com/apache/ignite/pull/3496
IGNITE-7657: Minor style fixes: imports, forgotten javadocs, annotations
â¦ons.
You can merge this pull request into a Git repository by running:
$ git pull
GitHub user sk0x50 opened a pull request:
https://github.com/apache/ignite/pull/3495
ignite-7193: IgniteReflectionFactory should properly handle primitive data
types
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sk0x50/ignite
Kirill Shirokov created IGNITE-7657:
---
Summary: SQL COPY: minor style fixes
Key: IGNITE-7657
URL: https://issues.apache.org/jira/browse/IGNITE-7657
Project: Ignite
Issue Type: Bug
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3493
---
Sergey,
These mappings are supposed to be the same on all nodes, so if the file
already exists, we can safely ignore this, or use a lock to avoid
concurrent access. Actually, I think we already fixed this in the past,
it's weird that issue came up again.
But in any case, switching marshaller
Mike Williams created IGNITE-7656:
-
Summary: Can't query a created cache
Key: IGNITE-7656
URL: https://issues.apache.org/jira/browse/IGNITE-7656
Project: Ignite
Issue Type: Bug
Nikolay Izhikov created IGNITE-7655:
---
Summary: Spark Data Frames: saving data frames into Ignite needs
to be documented
Key: IGNITE-7655
URL: https://issues.apache.org/jira/browse/IGNITE-7655
Mikhail Cherkasov created IGNITE-7654:
-
Summary: Geospatial queries does not work for JDBC/ODBC
Key: IGNITE-7654
URL: https://issues.apache.org/jira/browse/IGNITE-7654
Project: Ignite
Dmitry, thanks a lot, works as expected now!
Pavel
On Thu, Feb 8, 2018 at 5:47 PM, Dmitry Pavlov wrote:
> Could you please check now?
>
> чт, 8 февр. 2018 г. в 16:37, Pavel Tupitsyn :
>
> > Hi Dmitry,
> >
> > I've re-registered using
Github user nizhikov closed the pull request at:
https://github.com/apache/ignite/pull/2372
---
Hi Yaroslav,
The task is unassigned. So, you’re free to take over it and raise the questions
or implementation suggestions here.
—
Denis
> On Feb 8, 2018, at 4:39 AM, Yaroslav Lymar wrote:
>
> Hi Igniters!
>
> I would like to engage the task (IGNITE-6134).
>
Anton,
What’s wrong if we just go ahead and:
- replace “fabric” with “ignite”
- replace “hadoop” with “ignite-hadoop"
—
Denis
> On Feb 8, 2018, at 1:51 AM, Anton Vinogradov wrote:
>
> Denis,
>
> "hadoop" and "fabric" words work on same engine.
>
> We have special
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3469
---
GitHub user dmitrievanthony opened a pull request:
https://github.com/apache/ignite/pull/3494
IGNITE-7438 LSQR solver for Linear Regression
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-7438
GitHub user slukyano opened a pull request:
https://github.com/apache/ignite/pull/3493
Ignite 9486
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9486
Alternatively you can review and apply these
Could you please check now?
чт, 8 февр. 2018 г. в 16:37, Pavel Tupitsyn :
> Hi Dmitry,
>
> I've re-registered using ptupit...@apache.org email, can you give me back
> admin permissions?
>
> Thanks,
> Pavel
>
> On Thu, Feb 8, 2018 at 4:26 PM, Dmitry Pavlov
GitHub user pvinokurov opened a pull request:
https://github.com/apache/ignite/pull/3492
IGNITE-7398 Disabled MBean registration for cache group if IGNITE_MBEâ¦
You can merge this pull request into a Git repository by running:
$ git pull
Hello, Igniters!
We have some issues with current IgniteSet implementation ([1], [2], [3], [4]).
As was already described in this conversation, the main problem is
that current IgniteSet implementation maintains plain Java sets on
every node (see CacheDataStructuresManager.setDataMap). These
Eduard Shangareev created IGNITE-7653:
-
Summary: Issue with saved license causes snapshot test fails
Key: IGNITE-7653
URL: https://issues.apache.org/jira/browse/IGNITE-7653
Project: Ignite
GitHub user pvinokurov opened a pull request:
https://github.com/apache/ignite/pull/3491
IGNITE-7263 Ignore client configuration for daemon node
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-7263
Hi Dmitry,
I've re-registered using ptupit...@apache.org email, can you give me back
admin permissions?
Thanks,
Pavel
On Thu, Feb 8, 2018 at 4:26 PM, Dmitry Pavlov wrote:
> Hi Pavel,
>
> Could you please re-register using gmail or apache email?
>
> Sincerely,
> Dmitriy
Github user pvinokurov closed the pull request at:
https://github.com/apache/ignite/pull/3486
---
GitHub user Jokser opened a pull request:
https://github.com/apache/ignite/pull/3490
IGNITE-7540 Sequential checkpoints cause overwrite of already cleaned &
freed offheap page
You can merge this pull request into a Git repository by running:
$ git pull
Hi Pavel,
Could you please re-register using gmail or apache email?
Sincerely,
Dmitriy Pavlov
чт, 8 февр. 2018 г. в 16:03, Pavel Tupitsyn :
> Igniters,
>
> My teamcity (ci.ignite.apache.org) account "ptupitsin" seems to be removed
> or disabled.
> Does anyone know
Anton,
The merge is done!
Thank you, very much.
Your help can't be overestimated.
В Чт, 08/02/2018 в 12:38 +0300, Anton Vinogradov пишет:
> Looks like no one have objections.
>
> Nikolay,
> Let's merge.
>
> On Tue, Feb 6, 2018 at 8:45 PM, Nikolay Izhikov wrote:
>
> >
Igniters,
My teamcity (ci.ignite.apache.org) account "ptupitsin" seems to be removed
or disabled.
Does anyone know what's going on?
Thanks,
Pavel
GitHub user ilantukh opened a pull request:
https://github.com/apache/ignite/pull/3489
Deprecated WALMode.DEFAULT.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2.4.3-walmode
Alternatively you
Nikolay Izhikov created IGNITE-7652:
---
Summary: ContinuousQueryWithTransformer needs to be documented
Key: IGNITE-7652
URL: https://issues.apache.org/jira/browse/IGNITE-7652
Project: Ignite
Hi Igniters!
I would like to engage the task (IGNITE-6134).
Judging by the comments, this task was already taken by someone but the
progress was unknown.
Is this task still topicality? Сan I get it developed?
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3233
---
Hi Dmitriy,
This suite is needed for isolated methods tests and classes tests. Because
Ignite became not only in-memory solution, persistence enabled integration
tests were introduced also. These disk-enabled tests and/or tests with a
number of node startup-shutdown may require sufficient time
Hi Igniters!
I can't comprehend the meaning of the following note in javadoc for
EvictableEntry.isCached() method.
"If entry is not in cache (e.g. has been removed) {@code false} is
returned. In this case all operations on this entry will cause creation of
a new entry in cache."
That is, if I
Eduard Shangareev created IGNITE-7651:
-
Summary: Assertion error on cache start
Key: IGNITE-7651
URL: https://issues.apache.org/jira/browse/IGNITE-7651
Project: Ignite
Issue Type: Bug
Alexander Kalinin created IGNITE-7650:
-
Summary: Web Console: Rework signin page.
Key: IGNITE-7650
URL: https://issues.apache.org/jira/browse/IGNITE-7650
Project: Ignite
Issue Type:
Denis,
"hadoop" and "fabric" words work on same engine.
We have special assembly desctiptors, for example:
dependencies-fabric.xml
dependencies-fabric-lgpl.xml
dependencies-hadoop.xml
release-base.xml
release-fabric.xml
release-fabric-base.xml
release-fabric-lgpl.xml
release-hadoop.xml
So, I'ts
Looks like no one have objections.
Nikolay,
Let's merge.
On Tue, Feb 6, 2018 at 8:45 PM, Nikolay Izhikov wrote:
> Hello, Igniters.
>
> Improvement of Continuous Query public API are ready for merge.
> AFAIK Anton Vinogradov and Yakov Zhdanov are happy with proposed API.
Stanilovsky Evgeny created IGNITE-7649:
--
Summary: transformer instance is not properly transfers into
SqlQuery request.
Key: IGNITE-7649
URL: https://issues.apache.org/jira/browse/IGNITE-7649
Alexei Scherbakov created IGNITE-7648:
-
Summary: Revert IGNITE_ENABLE_FORCIBLE_NODE_KILL system property.
Key: IGNITE-7648
URL: https://issues.apache.org/jira/browse/IGNITE-7648
Project: Ignite
Peter Ivanov created IGNITE-7647:
Summary: Apache Ignite RPM packages
Key: IGNITE-7647
URL: https://issues.apache.org/jira/browse/IGNITE-7647
Project: Ignite
Issue Type: Task
+1 hadoop accelerator removing for AI 2.5
Also probably IGFS should be either removed or refactored, e.g. create FS
directly over the data region without using "cache" entity as an
intermidiate stage
On Thu, Feb 8, 2018 at 2:13 AM, Denis Magda wrote:
> Anton,
>
> I don’t get
Peter Ivanov created IGNITE-7646:
Summary: OSGI tests fail to unlock build directory causing
following builds to fail to start
Key: IGNITE-7646
URL: https://issues.apache.org/jira/browse/IGNITE-7646
45 matches
Mail list logo