I looked into code and I think that we could do the following:
1) Use user and password for authentication.
2) Use newUser and newPassword for new authentication API (add, remove and
update user).
3) Debug why sessionToken is null.
Created issues:
https://issues.apache.org/jira/browse/IGNITE-8201
Alexey Kuznetsov created IGNITE-8202:
Summary: Debug why REST return null as sessionToken when
authentication enabled
Key: IGNITE-8202
URL: https://issues.apache.org/jira/browse/IGNITE-8202
Projec
Alexey, are you suggesting that we have "newUser" as command parameter, while
"user" is also a valid command parameter?
D.
On Apr 10, 2018, 12:00 AM, at 12:00 AM, Alexey Kuznetsov
wrote:
>I looked into code and I think that we could do the following:
>
>1) Use user and password for authenti
Dmitriy,
Yes, because we have a command "Add new user" and this command can be
executed only with credentials of some "admin" user.
It means, that in one command you need to specify name of new user and
"admin" credentials at the same time.
If you have any ideas how we can handle this - I will b
On Tue, Apr 10, 2018 at 12:28 AM, Alexey Kuznetsov
wrote:
> Dmitriy,
>
> Yes, because we have a command "Add new user" and this command can be
> executed only with credentials of some "admin" user.
>
> It means, that in one command you need to specify name of new user and
> "admin" credentials at
Hi
Can some one reply to my comments in the following ticket or redirect to
someone who can look into
https://issues.apache.org/jira/browse/IGNITE-6252
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Hi
I a bit investigated the issue for REST authentication and found following
approaches:
1. Add authenticate command providing sessions token by login and password.
Any further requests will require that token.
Advantages:
- Small changes for REST requests (just add token parameter)
Disadvantag
Hi Dmitry!
I`ve just commited new fix. I renamed package of new module to
springdata20, it helps us to separate old implementation from new and also
should fix all compilation errors.
пн, 9 апр. 2018 г. в 23:54, Роман Меерсон :
> Ok, I'll check it, but I haven't face this problem.
> If I'll find
Igniters,
Cache groups were implemented for a sole purpose - to hide internal
inefficiencies. Namely (add more if I missed something):
1) Excessive heap usage for affinity/partition data
2) Too much data files as we employ file-per-partition approach.
These problems were resolved, but now cache g
GitHub user dmekhanikov opened a pull request:
https://github.com/apache/ignite/pull/3784
ignite-8058 fix flaky GridMarshallerMappingConsistencyTest
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-80
Vladimir, sounds like a huge refactoring. Other than "cache groups are
confusing", are we solving any other big issues with the new proposed
approach?
(every time we try to refactor rebalancing, I get goose bumps)
D.
On Tue, Apr 10, 2018 at 1:32 AM, Vladimir Ozerov
wrote:
> Igniters,
>
> Cache
Dmitriy,
Yes, sound reasonable to add "authenticate" command and require token for
all subsequent commands.
Will update issue description.
On Tue, Apr 10, 2018 at 2:43 PM, Dmitriy Setrakyan
wrote:
> On Tue, Apr 10, 2018 at 12:28 AM, Alexey Kuznetsov
> wrote:
>
> > Dmitriy,
> >
> > Yes, becaus
Dima,
1) Easy to understand for users
AI 2.x: cluster -> cache group -> cache -> table
AI 3.x: cluster -> cache(==table)
2) Fine grained cache management
- MVCC on/off per-cache
- WAL mode on/off per-cache
- Data size per-cache
3) Performance:
- Efficient scans are not possible with cache groups
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3760
---
Ivan Daschinskiy created IGNITE-8203:
Summary: Interrupting task can cause node fail with
PersistenceStorageIOException.
Key: IGNITE-8203
URL: https://issues.apache.org/jira/browse/IGNITE-8203
Pr
Thank you, Roman.
Igniters,
IMO we should consider one more alternative - renaming of old module and
package names. Users, which prefer to stay on previous version will be
requiered to update their pom's. In the same time users which are ready to
migrate to spring data 2.0 will need to update met
Hi Vladimir,
We can solve "too many fsyncs" or 'too many small files' by placing several
partitions of cache group in one file.
We don't need to get rid from cache groups in this case.
It is not trivial task, but it is doable. We need to create simplest FS for
paritition chunks inside one file.
Alexander Paschenko created IGNITE-8204:
---
Summary: Tests hang with lazy query flag on
Key: IGNITE-8204
URL: https://issues.apache.org/jira/browse/IGNITE-8204
Project: Ignite
Issue Type:
GitHub user alexpaschenko opened a pull request:
https://github.com/apache/ignite/pull/3785
IGNITE-8204
(cherry picked from commit cabdc52)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8204
Altern
Hi,
It seems your question is related to code of Cassandra cache store.
According to git, author of this code is Igor Rudyak, and it seems Igor is
also watcher of ticket, where you were asking.
Igor,
could you please advice?
Sincerely,
Dmitriy Pavlov
вт, 10 апр. 2018 г. в 10:49, kotamrajuyash
GitHub user AMashenkov opened a pull request:
https://github.com/apache/ignite/pull/3786
Ignite 2.4.4.b2
For test purposes
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2.4.4.b2
Alternatively you c
GitHub user dmitrievanthony opened a pull request:
https://github.com/apache/ignite/pull/3787
IGNITE-8176 Integrate gradient descent linear regression with partition
based dataset
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/
Val,
They are simply not implemented yet. I am not aware of concrete plans to
support them.
On Mon, Apr 9, 2018 at 11:33 PM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> Guys,
>
> Is there a way to run collocated compute job in C++? I can't find
> affinityRun and affinityCall me
GitHub user NSAmelchev opened a pull request:
https://github.com/apache/ignite/pull/3788
IGNITE-7170
Fixed log message.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/NSAmelchev/ignite ignite-7170
Alternatively you can review an
Github user NSAmelchev closed the pull request at:
https://github.com/apache/ignite/pull/3788
---
GitHub user NSAmelchev reopened a pull request:
https://github.com/apache/ignite/pull/3788
IGNITE-7824
Fixed log message.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/NSAmelchev/ignite ignite-7170
Alternatively you can review
Denis Mekhanikov created IGNITE-8205:
Summary: Services are not redeployed when cluster is getting
activated
Key: IGNITE-8205
URL: https://issues.apache.org/jira/browse/IGNITE-8205
Project: Ignite
Igor Seliverstov created IGNITE-8206:
Summary: SQL TX: Rewrite MvccCursor
Key: IGNITE-8206
URL: https://issues.apache.org/jira/browse/IGNITE-8206
Project: Ignite
Issue Type: Task
Igor Seliverstov created IGNITE-8207:
Summary: SQL TX: Cleanup own previous changes on update
Key: IGNITE-8207
URL: https://issues.apache.org/jira/browse/IGNITE-8207
Project: Ignite
Issue
Igor Seliverstov created IGNITE-8208:
Summary: SQL TX: Do not check with TxLog rows having the same
insert and update versions
Key: IGNITE-8208
URL: https://issues.apache.org/jira/browse/IGNITE-8208
Hi NIkolay,
Regarding system caches, rule of thumb here - do not use them. Keys should
be stored near cache.
As far as password:
1) Oracle auto-login wallet [1]
2) MySQL- password may be set inside configuration [2]
I do not think that any kind of prompts are needed here out of the box. May
be w
Github user andrey-kuznetsov closed the pull request at:
https://github.com/apache/ignite/pull/3722
---
GitHub user tledkov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/3789
IGNITE-7999 Enhance performance of the thin JDBC streaming mode
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-igni
Igniters,
Looks like commit:
d0adb61ecd9af0d9907e480ec747ea1465f97cd7 is the first bad commit
> commit d0adb61ecd9af0d9907e480ec747ea1465f97cd7
> Author: Ivan Rakov
> Date: Tue Mar 27 20:11:52 2018 +0300
> IGNITE-7754 WAL in LOG_ONLY mode doesn't execute fsync on checkpoint
> begin - Fixes
Hi Ilya,
Thank you for checking Ignite performance.
Is it slower than our old default WAL mode 'Default'?
Sincerely,
Dmitriy Pavlov
вт, 10 апр. 2018 г. в 17:57, Ilya Suntsov :
> Igniters,
>
> Looks like commit:
>
> d0adb61ecd9af0d9907e480ec747ea1465f97cd7 is the first bad commit
> > commit d0a
Ilya, can we find out why pure in-memory scenario also had a performance
drop and which commit caused it? It should not be affected by changes in
persistence at all.
D.
On Tue, Apr 10, 2018 at 7:56 AM, Ilya Suntsov wrote:
> Igniters,
>
> Looks like commit:
>
> d0adb61ecd9af0d9907e480ec747ea1465
GitHub user devozerov opened a pull request:
https://github.com/apache/ignite/pull/3790
IGNITE-8042
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8042
Alternatively you can review and apply these
16% looks perfectly ok to me provided that we compare correct
implementation with incorrect one.
вт, 10 апр. 2018 г. в 18:24, Dmitriy Setrakyan :
> Ilya, can we find out why pure in-memory scenario also had a performance
> drop and which commit caused it? It should not be affected by changes in
>
++1 from me for Vladimir's point
вт, 10 апр. 2018 г. в 19:08, Vladimir Ozerov :
> 16% looks perfectly ok to me provided that we compare correct
> implementation with incorrect one.
>
> вт, 10 апр. 2018 г. в 18:24, Dmitriy Setrakyan :
>
> > Ilya, can we find out why pure in-memory scenario also ha
Hi Raúl, Igniters,
Test related to OSGI/Karaf
(IgniteKarafFeaturesInstallationTest.testAllBundlesActiveAndFeaturesInstalled)
is currently failing
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=451522206339372479&branch=%3Cdefault%3E&tab=testDetails
with low succe
I am not convinced that the performance degradation is only due to the new
change that fixes the incorrect behavior. To my knowledge, there is also a
drop in memory-only mode. Can someone explain why do we have such a drop?
D.
On Tue, Apr 10, 2018 at 9:08 AM, Vladimir Ozerov
wrote:
> 16% looks
Alexey Goncharuk created IGNITE-8209:
Summary: Exchange worker busy-spins after
ForceRebalanceExchangeTask
Key: IGNITE-8209
URL: https://issues.apache.org/jira/browse/IGNITE-8209
Project: Ignite
Stanislav Lukyanov created IGNITE-8210:
--
Summary: Rebalancing sometimes is not triggered when a node is
added to the baseline topology
Key: IGNITE-8210
URL: https://issues.apache.org/jira/browse/IGNITE-8210
Hi Pavel,
thank you for bring up test questions. It seems my previous comments were
not taken into account.
Igniters,
let me remind we should get passing TC suites before merge,
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-ReviewProcessandMaintainers
(hi
GitHub user Jokser opened a pull request:
https://github.com/apache/ignite/pull/3791
IGNITE-8116 Historical rebalance fixes
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8116-8122
Alternatively yo
GitHub user daradurvs opened a pull request:
https://github.com/apache/ignite/pull/3792
-
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/daradurvs/ignite ignite-8141
Alternatively you can review and apply these changes as the p
Github user daradurvs closed the pull request at:
https://github.com/apache/ignite/pull/3709
---
Dmitry,
Sorry for confusing topic. I I'm pretty sure that configuration for atomic
caches is validated, will double-check this. I was referring only atomic
data structures cache.
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Hi!
I use local cache and get a lot of warnings when execute ScanQueries.
[13:26:25 WRN] Ignoring query projection because
it's executed over LOCAL cache (only local node will be queried):
GridCacheQueryAdapter [type=SCAN, clsName=null, clause=null,
filter=o.a.i.i.processors.platform.cache.P
Vladimir,
- Data size per-cache
Could you elaborate how the data size per-cache/table task will be
addressed with proposed architecture? Are you going to store data of a
specific cache in dedicated pages/segments? What's about index size?
--
Denis
On Tue, Apr 10, 2018 at 2:31 AM, Vladimir Ozer
In our Hibernate integration we define following two modules to distinguish
incompatible versions:
- ignite-hiberbate_4.2
- ignite-hibernate_5.1
In Spark we have:
- ignite-spark
- ignite-spark_2.10
After thinking this over, I would do the following with Spring Data:
- ignite-spr
Aleksandr Tceluiko created IGNITE-8211:
--
Summary: .Net Invalid cast to CacheEvent
Key: IGNITE-8211
URL: https://issues.apache.org/jira/browse/IGNITE-8211
Project: Ignite
Issue Type: Bug
Hi all!
IMHO if we do so we'll produce big pain for everybody while migrating on
new version, because ones should change method and others should change
their poms. This change would be backward incompatible so it probably
should follow with major version upgrade, but I'm not sure about it.
Other
Roman,
Your suggestion sounds reasonable to me. Backing it up.
--
Denis
On Tue, Apr 10, 2018 at 2:50 PM, Роман Меерсон wrote:
> Hi all!
>
> IMHO if we do so we'll produce big pain for everybody while migrating on
> new version, because ones should change method and others should change
> their
Alexey Kosenchuk created IGNITE-8212:
Summary: Binary Client Protocol spec: Key-Value Queries
clarifications
Key: IGNITE-8212
URL: https://issues.apache.org/jira/browse/IGNITE-8212
Project: Ignite
On Tue, Apr 10, 2018 at 2:03 PM, akurbanov wrote:
> Dmitry,
>
> Sorry for confusing topic. I I'm pretty sure that configuration for atomic
> caches is validated, will double-check this. I was referring only atomic
> data structures cache.
>
Got it. We should definitely add validation for the ato
On Tue, Apr 10, 2018 at 2:22 PM, Alew wrote:
> Hi!
>
> I use local cache and get a lot of warnings when execute ScanQueries.
>
> [13:26:25 WRN] Ignoring query projection because it's
> executed over LOCAL cache (only local node will be queried):
> GridCacheQueryAdapter [type=SCAN, clsName=null,
Hi, Dmitriy
Of course I understand what a local cache means and it is not a mistake.
But why does Ignite warn me on every query?
My logs full with this warning. Maybe log level should be information or
debug.
On 11/04/2018 01:33, Dmitriy Setrakyan wrote:
On Tue, Apr 10, 2018 at 2:22 PM, Alew
Guys,
I also not sure I understand the purpose of methods like [1] that accept
instance of AtomicConfiguration to create new atomic structure. Per my
knowledge, all atomics are stored in a single cache which is configured by
AtomicConfiguration provided on startup as part of IgniteConfiguration. I
Alew,
This looks like a bug as there is no way to provide cluster group for a
query in the latest versions. Can you create a Jira ticket and attach unit
test if you have one?
-Val
On Tue, Apr 10, 2018 at 4:11 PM, Alew wrote:
> Hi, Dmitriy
>
> Of course I understand what a local cache means and
Is there a ticket? Let's create one if not.
-Val
On Tue, Apr 10, 2018 at 6:17 AM, Vladimir Ozerov
wrote:
> Val,
>
> They are simply not implemented yet. I am not aware of concrete plans to
> support them.
>
> On Mon, Apr 9, 2018 at 11:33 PM, Valentin Kulichenko <
> valentin.kuliche...@gmail.com
Look into both Docusaraus and Jekyll from the usage perspective. Here is my
summary:
*Documentation Sources *
Will be stored on GitHub. My preference is to store them in "ignite/docs"
folder as many other ASF projects do (Spark [1], Flink [2] and Storm [3]).
If we need to update the sources of an
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3773
---
This is on my plate, will try to take a look this week.
-Val
On Mon, Apr 9, 2018 at 10:28 AM, Denis Magda wrote:
> Val,
>
> As an initial reviewer and reporter, could you have a look and sign the
> contribution off?
>
> --
> Denis
>
> On Mon, Apr 9, 2018 at 12:56 AM, Aleksey Kuznetsov <
> alkuz
Pavel Konstantinov created IGNITE-8213:
--
Summary: control.sh: make a correct error message in case of
adding non-existen node to baseline
Key: IGNITE-8213
URL: https://issues.apache.org/jira/browse/IGNITE-821
Pavel Konstantinov created IGNITE-8214:
--
Summary: Web console: add validation for Persistent + Swap file
for data region configuration
Key: IGNITE-8214
URL: https://issues.apache.org/jira/browse/IGNITE-8214
Pavel Konstantinov created IGNITE-8215:
--
Summary: Web console: some fields are not generated
Key: IGNITE-8215
URL: https://issues.apache.org/jira/browse/IGNITE-8215
Project: Ignite
Issue
Dmitriy,
I've measured performance on the current master and haven't found any
problems with in-memory mode.
On Tue, Apr 10, 2018, 20:33 Dmitriy Setrakyan wrote:
> I am not convinced that the performance degradation is only due to the new
> change that fixes the incorrect behavior. To my knowle
68 matches
Mail list logo
