I think the development effort would still be higher. Everything would have to
be put via JDBC into Ignite, then checkpointing would have to be done via JDBC
(again additional development effort), a lot of conversion from spark internal
format to JDBC and back to ignite internal format. Paginati
On Thu, Aug 3, 2017 at 9:04 AM, Jörn Franke wrote:
> I think the development effort would still be higher. Everything would
> have to be put via JDBC into Ignite, then checkpointing would have to be
> done via JDBC (again additional development effort), a lot of conversion
> from spark internal f
Pavel Konstantinov created IGNITE-5908:
--
Summary: Web console: may failed to open non-root if user is not
authorized
Key: IGNITE-5908
URL: https://issues.apache.org/jira/browse/IGNITE-5908
Projec
Dmitriy Shabalin created IGNITE-5909:
Summary: Web console: Implement editable list
Key: IGNITE-5909
URL: https://issues.apache.org/jira/browse/IGNITE-5909
Project: Ignite
Issue Type: Imp
Dmitry,
Ignite mode in H2 is about parsing only, it does not address other
issues pointed out by Vlad. Alas, implementing _parser_ surely won't
take no years, whilst things like smart query optimization, etc,
probably don't have and can't have proper "finished" state - it's
something that you can
Vyacheslav Daradur created IGNITE-5910:
--
Summary: Method stopGrid(name) doesn't work in multiJvm mode
Key: IGNITE-5910
URL: https://issues.apache.org/jira/browse/IGNITE-5910
Project: Ignite
Pavel Tupitsyn created IGNITE-5911:
--
Summary: .NET: EntityFramework cache eager update
Key: IGNITE-5911
URL: https://issues.apache.org/jira/browse/IGNITE-5911
Project: Ignite
Issue Type: Imp
GitHub user daradurvs opened a pull request:
https://github.com/apache/ignite/pull/2382
IGNITE-5910 Method stopGrid(name) doesn't work in multiJvm mode
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/daradurvs/ignite ignite-5910
Roman Shtykh created IGNITE-5912:
Summary: [Redis] EXPIRE/PEXPIRE on keys
Key: IGNITE-5912
URL: https://issues.apache.org/jira/browse/IGNITE-5912
Project: Ignite
Issue Type: New Feature
Pavel Konstantinov created IGNITE-5913:
--
Summary: Web console: code (spring\java) is not generated for
field 'Long query timeout:' on cluster level in Miscellaneous group
Key: IGNITE-5913
URL: https://issues.
GitHub user shroman opened a pull request:
https://github.com/apache/ignite/pull/2383
IGNITE-5912: Redis EXPIRE/PEXPIRE commands.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/shroman/ignite IGNITE-5912
Alternatively you can r
GitHub user nizhikov opened a pull request:
https://github.com/apache/ignite/pull/2384
IGNITE-5897: Fix session init/end logic. This fixes tests
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/nizhikov/ignite IGNITE-5897
Alterna
Dima,
Our goal is to have a format, which will work for both synchronous,
asynchronous, single-threaded and multi-threaded clients. All we need to
achieve this is "request ID" propagated from request to response. This way
3-rd party developers will be free to decide how to implement the client.
O
Got it, thanks!
On Aug 3, 2017, 11:04 AM, at 11:04 AM, Vladimir Ozerov
wrote:
>Dima,
>
>Our goal is to have a format, which will work for both synchronous,
>asynchronous, single-threaded and multi-threaded clients. All we need
>to
>achieve this is "request ID" propagated from request to response
Pavel Konstantinov created IGNITE-5914:
--
Summary: Web console: incorrect cache mode in case if cache was
created during importing model from DB
Key: IGNITE-5914
URL: https://issues.apache.org/jira/browse/IGN
> * Based on some sort of policies when the actual cluster topology differs
too much from the baseline or when some critical condition happens (e.g.,
when there are no more backups for a partition)
Good point, Alex! I would even go further. If cluster is active and under
load and nodes continue jo
How about naming it "minimal node set" or "required node set"?
D.
On Aug 3, 2017, 11:15 AM, at 11:15 AM, Yakov Zhdanov
wrote:
>> * Based on some sort of policies when the actual cluster topology
>differs
>too much from the baseline or when some critical condition happens
>(e.g.,
>when there a
Alexey Goncharuk created IGNITE-5915:
Summary: Add more clear WAL mode documentation and print a warning
when NONE mode is used
Key: IGNITE-5915
URL: https://issues.apache.org/jira/browse/IGNITE-5915
Ю> How about naming it "minimal node set" or "required node set"?
Required for what? I would add restart if there are no confusion.
--Yakov
>From my standpoint name for the concept should emphasize that nodes from
the set constitute a target topology - the place where user wants to be.
If we go in a "node set" way, what about FixedNodeSet or BaseNodeSet?
"restart node set" also is a bit confusing because this concept works not
only t
Yakov,
I think it is not just restarts, this set of nodes is minimally required for
the cluster to function, no?
D.
On Aug 3, 2017, 11:23 AM, at 11:23 AM, Yakov Zhdanov
wrote:
>Ю> How about naming it "minimal node set" or "required node set"?
>
>Required for what? I would add restart if the
Dmitriy,
Obvious connotation of "minimal set" is a set that cannot be decreased.
But lets consider the following case: user has a cluster of 50 nodes and
decides to switch off 3 nodes for maintenance for a while. Ok, user just
does it and then recreates this "minimal node set" to only 47 nodes.
Pavel Konstantinov created IGNITE-5916:
--
Summary: Web console: incorrect default value for Cache-Queries &
Indexing-SQL index max inline size = -1
Key: IGNITE-5916
URL: https://issues.apache.org/jira/browse/I
Pavel Konstantinov created IGNITE-5917:
--
Summary: Fields have no error-triangle in case of incorrect value
Key: IGNITE-5917
URL: https://issues.apache.org/jira/browse/IGNITE-5917
Project: Ignite
Mikhail Cherkasov created IGNITE-5918:
-
Summary: Adding and searching objects in index tree produce a lot
of garbage
Key: IGNITE-5918
URL: https://issues.apache.org/jira/browse/IGNITE-5918
Project
Folks,
As far as I see, Issue still in PatchAvailable state, what did you mean by
"solved"?
On Wed, Aug 2, 2017 at 8:01 PM, Kozlov Maxim wrote:
> Sure.
>
> CacheQueryEntryEvent:
>
> public abstract boolean isBackup();
> public abstract boolean isPrimary();
>
>
> > 2 авг. 2017 г., в 19:56, Nikol
Igniters, what about Target Node Set? Complete Node Set?
As when we reach this topology, we can activate cluster.
чт, 3 авг. 2017 г. в 12:58, Sergey Chugunov :
> Dmitriy,
>
> Obvious connotation of "minimal set" is a set that cannot be decreased.
>
> But lets consider the following case: user ha
>I think it is not just restarts, this set of nodes is minimally required
for the cluster to function, no?
I don't think so. Cluster can function if there is no data loss.
--Yakov
>Obvious connotation of "minimal set" is a set that cannot be decreased.
>But lets consider the following case: user has a cluster of 50 nodes and
>decides to switch off 3 nodes for maintenance for a while. Ok, user just
>does it and then recreates this "minimal node set" to only 47 nodes.
>So in
Irina Zaporozhtseva created IGNITE-5919:
---
Summary: .NET: EntryProcessorExample closes immediately after
execution
Key: IGNITE-5919
URL: https://issues.apache.org/jira/browse/IGNITE-5919
Project:
Aleksey Chetaev created IGNITE-5920:
---
Summary: CacheClientBinaryQueryExample return different results if
we add non local node
Key: IGNITE-5920
URL: https://issues.apache.org/jira/browse/IGNITE-5920
Guys,
I'm sorry for the misunderstanding, I was tired at the end of the day :-)
In the process of working on the task, I had to add 2 methods to the public
interface.
The first method is #isBackup(), it returns 'true' if cache is being updated on
the backup node.
The second method is #isPrimary
My understanding of Baseline Topology is the set of nodes which are
*expected* to be in the cluster.
Let me go a little bit further because BT (or whatever name we choose) may
and will solve more issues than just auto-activation:
1) More graceful control over rebalancing than just rebalance delay.
GitHub user agoncharuk opened a pull request:
https://github.com/apache/ignite/pull/2385
8.0.3.ea14
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-gg-8.0.3.ea14
Alternatively you can review and app
Mikhail Cherkasov created IGNITE-5921:
-
Summary: Reduce contention for free list access
Key: IGNITE-5921
URL: https://issues.apache.org/jira/browse/IGNITE-5921
Project: Ignite
Issue Type:
I also would like to provide more use cases of how BLT is supposed to work
(let me call it this way until we come up with a better one):
1. User creates new BLT using WebConsole or other tool and "applies" it
to brand-new cluster.
2. User starts up brand-new cluster with desired amount o
Den,
I see at least two problems here:
1. Metrics meaning for end user. How user should interpret metrics in
this case. Moreover, average is bad gauge for monitoring because it
hides actual latencies. User should have possibility to get accurate
metrics in order to build some monitoring that can
Hi,
I'll do it soon. But there is problem with Zeppelin because CI should
be configured on local machine. So I need more time than usually for
update Ignite version in Zeppelin (e.g. Ignite 2.0 still not relased
in Zeppelin).
On Tue, Aug 1, 2017 at 9:13 AM, Roman Shtykh wrote:
> Denis,
> I updat
GitHub user DmitriyGovorukhin opened a pull request:
https://github.com/apache/ignite/pull/2386
IGNITE-5890 Estimated time to rebalance completion
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-5890
Evgenii Zhuravlev created IGNITE-5922:
-
Summary: Improve collisionSpi doc - ParallelJobsNumber should be
less than PublicThreadPoolSize
Key: IGNITE-5922
URL: https://issues.apache.org/jira/browse/IGNITE-5922
Hi,
>>1. User creates new BLT using WebConsole or other tool and "applies" it
to brand-new cluster.
Good idea, but we also should implement *command-line utility* for the same
use case.
--
Alexey Kuznetsov
GitHub user daradurvs opened a pull request:
https://github.com/apache/ignite/pull/2387
IGNITE-5736 Add test of backward-compatibility
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/daradurvs/ignite ignite-5736
Alternatively yo
Github user tledkov-gridgain closed the pull request at:
https://github.com/apache/ignite/pull/2371
---
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 feat
GitHub user tledkov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/2388
IGNITE-5211 Classes based constructor for QueryEntities
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-
Igor Sapego created IGNITE-5923:
---
Summary: ODBC: SQLGetTypeInfo does not work with SQL_ALL_TYPES
Key: IGNITE-5923
URL: https://issues.apache.org/jira/browse/IGNITE-5923
Project: Ignite
Issue Ty
GitHub user tledkov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/2389
IGNITE-5920: Fix the example. Set CacheKeyConfiguration explicitly toâ¦
⦠enable affinity co-location.
You can merge this pull request into a Git repository by running:
$ git pull
GitHub user sergey-chugunov-1985 opened a pull request:
https://github.com/apache/ignite/pull/2390
ignored_tests suite fixes
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite z_Ignores_check
Alternatively yo
GitHub user andrey-kuznetsov opened a pull request:
https://github.com/apache/ignite/pull/2391
Ignite 5655
First implementation, uses global level configuration option (in
BinaryConfiguration)
You can merge this pull request into a Git repository by running:
$ git pull https:/
Pavel Tupitsyn created IGNITE-5924:
--
Summary: .NET: Decouple Marshaller from Ignite
Key: IGNITE-5924
URL: https://issues.apache.org/jira/browse/IGNITE-5924
Project: Ignite
Issue Type: Improv
GitHub user isapego opened a pull request:
https://github.com/apache/ignite/pull/2392
ODBC: SQLGetTypeInfo now works with SQL_ALL_TYPES
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-5923
Alternati
GitHub user skalashnikov opened a pull request:
https://github.com/apache/ignite/pull/2393
IGNITE-5738: SQL: Added support for batching for jdbc2 driver
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignit
Yury Babak created IGNITE-5925:
--
Summary: Get row/col for matrices
Key: IGNITE-5925
URL: https://issues.apache.org/jira/browse/IGNITE-5925
Project: Ignite
Issue Type: Improvement
Compo
GitHub user ybabak opened a pull request:
https://github.com/apache/ignite/pull/2394
IGNITE-5880: BLAS integration phase 2
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-5880
Alternatively you can
vinay created IGNITE-5926:
-
Summary: Puts on near cache hangs
Key: IGNITE-5926
URL: https://issues.apache.org/jira/browse/IGNITE-5926
Project: Ignite
Issue Type: Bug
Affects Versions: 2.1, 2.0
Pavel Tupitsyn created IGNITE-5927:
--
Summary: .NET: DataTable can't be serialized
Key: IGNITE-5927
URL: https://issues.apache.org/jira/browse/IGNITE-5927
Project: Ignite
Issue Type: Bug
GitHub user ptupitsyn opened a pull request:
https://github.com/apache/ignite/pull/2395
IGNITE-5927 .NET: Fix DataTable serialization
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ptupitsyn/ignite IGNITE-5927
Alternatively you
This JDBC integration is just a Spark data source, which means that Spark
will fetch data in its local memory first, and only then apply filters,
aggregations, etc. This is obviously slow and doesn't use all advantages
Ignite provides.
To create useful and valuable integration, we should create a
Folks,
One of the users reported an issue with near cache in 2.0:
https://issues.apache.org/jira/browse/IGNITE-5926
There is a reproducer attached, I don't see anything obviously wrong and
can reproduce the issue. Can someone take a deeper look?
-Val
If the solution is positive, can anyone see my pull request?
2017-08-03 4:28 GMT+03:00 dsetrakyan [via Apache Ignite Developers] <
ml+s2346864n20403...@n4.nabble.com>:
> Agree with Denis. I think that we should treat it as a starting point for
> the release notes, and further update it before rel
Hi Igniters,
I’ve created the simplest example using Ignite 2.1 and persistence (see the
code below). I've included Ignite instance into try-with-resources (I think
it is default approach for AutoCloseable inheritors).
But next time when I started this server I got message: “Ignite node
crashed i
60 matches
Mail list logo
