Eh... good enough I think ;) Thanks!
On Sat, May 09, 2015 at 01:34AM, Ivan Veselovskiy wrote:
> My guess: that was done in order to be uniform with ignite.bat .
>
> On Fri, May 8, 2015 at 11:50 PM, Konstantin Boudnik wrote:
>
> > Guys,
> >
> > I've been looking at bin/ignite.sh and noticed that
Nope, all the same. However if I copy the file from the git source tree -
everything starts working. In order to double-check me, please run
unzip -l ignite-1.1.0-incubating-src.zip | grep "bin/include"
Cos
On Fri, May 08, 2015 at 06:17PM, Konstantin Boudnik wrote:
> On Fri, May 08, 2015 at 0
On Fri, May 08, 2015 at 06:01PM, Valentin Kulichenko wrote:
> +1
>
> ./ignite.sh successfully started the node. Cos, you probably have incorrect
> IGNITE_HOME in environment.
Clean env - new shell for RC validation. No IGNITE vars in the env. I am
rebuilding once again just in case, but I really
+1
./ignite.sh successfully started the node. Cos, you probably have incorrect
IGNITE_HOME in environment.
Git error is OK, build procedure tries to get values from Git, fails to do
that, but doesn't stop and use default values (at least this is how it
works for me).
On Fri, May 8, 2015 at 5:51
Unless it is my environment issue (which doesn't seem to be likely)
-1
Here's the problem though:
$ ./bin/ignite.sh
./bin/ignite.sh: line 61:
/home/cos/workspaces/1.1.0-RC3/ignite-1.1.0-incubating-src/bin/include/target-classpath.sh:
No such file or directory
Error: Could not find or load main
Guys,
I noticed that some entities on cache configuration are configured via
factories, while others are set directly. For example, we use factory for
ExpiryPolicy, but not for EvictionPolicy, which looks inconsistent. Since
factory-based approach comes from JCache, I think we should use it wherev
Created ticket: https://issues.apache.org/jira/browse/IGNITE-884
I marked it as "newbie", because it seems to be pretty easy to implement.
Feel free to comment.
--
Val
On Thu, May 7, 2015 at 9:14 PM, Dmitriy Setrakyan
wrote:
> Valentin,
>
> I completely agree, there is a usability issue there.
Valentin Kulichenko created IGNITE-884:
--
Summary: Cache store usability issues
Key: IGNITE-884
URL: https://issues.apache.org/jira/browse/IGNITE-884
Project: Ignite
Issue Type: Bug
My guess: that was done in order to be uniform with ignite.bat .
On Fri, May 8, 2015 at 11:50 PM, Konstantin Boudnik wrote:
> Guys,
>
> I've been looking at bin/ignite.sh and noticed that a random number is
> getting
> generated to form the name of an essentially lock file. For that a java VM
>
Guys,
I've been looking at bin/ignite.sh and noticed that a random number is getting
generated to form the name of an essentially lock file. For that a java VM is
started. Eg
RANDOM_NUMBER=$("$JAVA" -cp "${CP}"
org.apache.ignite.startup.cmdline.CommandLineRandomNumberGenerator)
While the st
You're right, Yakov. We do not need rest-http dependency. I've fixed the
documentation and have also mentioned there that we only support binary
protocol for memcache.
-P
On Fri, May 8, 2015 at 1:32 AM, Dmitriy Setrakyan
wrote:
> On Fri, May 8, 2015 at 1:30 AM, Yakov Zhdanov wrote:
>
> > Prach
>> I agree. If we delay indexing, what do we do with queries in the mean
time?
Work slow :)
IMHO, initial load is usually performed in exclusive mode.
On Sat, May 9, 2015 at 12:40 AM, Dmitriy Setrakyan
wrote:
> On Fri, May 8, 2015 at 8:48 AM, Sergi Vladykin
> wrote:
>
> > It does not make any
On Fri, May 8, 2015 at 8:48 AM, Sergi Vladykin
wrote:
> It does not make any sense to disable indexing on data loading and to index
> later because it is exactly the same amount of work.
>
I agree. If we delay indexing, what do we do with queries in the mean time?
> Anyways lets create test an
And, as always, if you feel like and have cycles to do this - please consider
contributing to this implementation. As a user your involvement would be hard
to underestimate.
Cos
On Fri, May 08, 2015 at 12:17PM, Vladimir Ozerov wrote:
> Prashant,
>
> Yes, queries support is on the implementation
There is one situation where disabling indexing during the data load might make
a difference. When the source of my data is a log-based store (like Kafka) with
multiple versions of the same fact, I'd really want to play the entire log back
first, and then get the cache indexed...
Andrey
> Date
On Fri, May 08, 2015 at 04:18PM, Anton Vinogradov wrote:
> Cos, Yakov,
>
> I've fixed rat issues and removed insecure text from devnotes. Devnotes
> will be fully refactored during sprint-5.
>
> Also since next vote sources and binaries will be provided by svn link (
> https://dist.apache.org/rep
My main point is avoid not needed GC.
Vasiliy and Pavel will prepare test for you.
On Fri, May 8, 2015 at 10:48 PM, Sergi Vladykin
wrote:
> It does not make any sense to disable indexing on data loading and to index
> later because it is exactly the same amount of work.
> Anyways lets create tes
Ok, got it.
Sergi
2015-05-08 12:27 GMT+03:00 Alexey Kuznetsov :
> Dmitriy already created issue (
> https://issues.apache.org/jira/browse/IGNITE-872).
> Valentin already found problem root (and added comment to issue).
> Sergi should look and fix.
>
> On Fri, May 8, 2015 at 3:45 PM, Yakov Zhdano
It does not make any sense to disable indexing on data loading and to index
later because it is exactly the same amount of work.
Anyways lets create test and investigate this.
Sergi
2015-05-08 11:39 GMT+03:00 Alexey Kuznetsov :
> Issue created: https://issues.apache.org/jira/browse/IGNITE-878
>
+1, looks good to me.
On Fri, May 8, 2015 at 5:26 PM, Yakov Zhdanov wrote:
> Guys,
>
> We have uploaded release candidate to
> https://dist.apache.org/repos/dist/dev/incubator/ignite/1.1.0-rc3/
>
> Tag name is
> ignite-1.1.0-incubating-rc3
>
> We fixed rat issues and added "-incubating" to the v
Guys,
We have uploaded release candidate to
https://dist.apache.org/repos/dist/dev/incubator/ignite/1.1.0-rc3/
Tag name is
ignite-1.1.0-incubating-rc3
We fixed rat issues and added "-incubating" to the version and many more
changes which are
described in devnotes (link below).
DEVNOTES
https://
Cos, Yakov,
I've fixed rat issues and removed insecure text from devnotes. Devnotes
will be fully refactored during sprint-5.
Also since next vote sources and binaries will be provided by svn link (
https://dist.apache.org/repos/dist/dev/incubator/ignite/ignite-rc*).
Keys will be published each t
Yakov Zhdanov created IGNITE-883:
Summary: TCP client discovery should support 150 clients in 1 VM
Key: IGNITE-883
URL: https://issues.apache.org/jira/browse/IGNITE-883
Project: Ignite
Issue
Semen Boikov created IGNITE-882:
---
Summary: Node can join twice with the same ID
Key: IGNITE-882
URL: https://issues.apache.org/jira/browse/IGNITE-882
Project: Ignite
Issue Type: Bug
C
Guys,
I have just filed a ticket -
https://issues.apache.org/jira/browse/IGNITE-881
In my understanding it is a "newbie" one.
Dmitry, I think you may have something to add.
Thanks!
--Yakov
Yakov Zhdanov created IGNITE-881:
Summary: Refactor ATOMIC_INCREMENT and ATOMIC_DECREMENT REST
commands to use entry processor
Key: IGNITE-881
URL: https://issues.apache.org/jira/browse/IGNITE-881
Pro
Dmitriy already created issue (
https://issues.apache.org/jira/browse/IGNITE-872).
Valentin already found problem root (and added comment to issue).
Sergi should look and fix.
On Fri, May 8, 2015 at 3:45 PM, Yakov Zhdanov wrote:
> Alex, can you please create a junit and ticket?
>
> --Yakov
>
> 2
Prashant,
Yes, queries support is on the implementation roadmap. However, there is a
chance that implementation of advanced features (like filters in SCAN
queries, and continuous queries) will be postponed a bit.
Vladimir.
On Fri, May 8, 2015 at 12:09 PM, Yakov Zhdanov wrote:
> Prashant, we ar
Prashant, we are trying to achieve API parity. Of course, some limitations
will take place, but cache operations + queries will be supported.
Vladimir Ozerov, can you please reply to this thread with issue number, so
everyone can get updates on the progress?
--Yakov
2015-05-08 12:01 GMT+03:00 Pr
Hi Yakov,
We have Linux based application who would be using this.
2 months will be OK for us let us know if require any help.
We are looking for APIs especially for Query part will that be available of it
would be normal Cache APIs like get, put.
Best Regards,
Prashant Thakur
-Original Me
Well... how about implementing it? =)
https://issues.apache.org/jira/browse/IGNITE-89
--Yakov
2015-05-08 11:32 GMT+03:00 Dmitriy Setrakyan :
> On Fri, May 8, 2015 at 1:30 AM, Yakov Zhdanov wrote:
>
> > Prachi,
> >
> > 1. Is rest-http dependency really a requirement? I don't think so. Can
> yo
Yakov Zhdanov created IGNITE-880:
Summary: Add support for memcached text protocol
Key: IGNITE-880
URL: https://issues.apache.org/jira/browse/IGNITE-880
Project: Ignite
Issue Type: Task
Alex, can you please create a junit and ticket?
--Yakov
2015-05-08 9:43 GMT+03:00 Alexey Kuznetsov :
> Checked with 2 nodes - scan query works fast.
> So, problem in case of single node.
>
> On Fri, May 8, 2015 at 8:17 AM, Alexey Kuznetsov
> wrote:
>
> > Val, yes I remember that I tested with o
Prashant,
Ignite currently Ignite does not have C++ API - we are currently working on
this and this will be ready within 2 months or so.
If you are on Windows you can use .Net APIs available in Enterprise
edition. Will this work for you?
--Yakov
2015-05-08 9:01 GMT+03:00 Prashant Singh Thakur :
Issue created: https://issues.apache.org/jira/browse/IGNITE-878
Vasiliy will create simple test to reproduce issue.
And after that will assign issue to Sergi.
On Fri, May 8, 2015 at 3:33 PM, Yakov Zhdanov wrote:
> Sergi, please take a look at this.
>
> --Yakov
>
> 2015-05-08 6:51 GMT+03:00 Alexe
Sergi, please take a look at this.
--Yakov
2015-05-08 6:51 GMT+03:00 Alexey Kuznetsov :
> Hi,
>
> When I do initial load of data (with a lot of indexed fields) into a cache
> I see GC activity on indexing internal objects.
>
> It is possible to turn off reindexing while I'm loading data and do r
On Fri, May 8, 2015 at 1:30 AM, Yakov Zhdanov wrote:
> Prachi,
>
> 1. Is rest-http dependency really a requirement? I don't think so. Can you
> recheck?
> 2. we should mention that we only support Memcached binary protocol. Spec
> is here - https://code.google.com/p/memcached/wiki/BinaryProtocolR
Prachi,
1. Is rest-http dependency really a requirement? I don't think so. Can you
recheck?
2. we should mention that we only support Memcached binary protocol. Spec
is here - https://code.google.com/p/memcached/wiki/BinaryProtocolRevamped
Otherwise, looks good! Thanks!
--Yakov
2015-05-08 1:00
On Thu, May 7, 2015 at 4:27 PM, Prachi Garg wrote:
> I can migrate the forums.
>
> -Prachi
>
Prachi, I have integrated our user list with Nabble and tried to migrate a
few posts. I think you can use this one as example:
http://apache-ignite-users.70518.x6.nabble.com/Code-dependent-on-jars-do-jar
Anton, can you please look into RAT issue?
--Yakov
2015-05-08 0:35 GMT+03:00 Konstantin Boudnik :
> -1
>
> The RAT check failed for DEPENDENCIES. I don't see this file in the repo,
> so
> looks like it is a some kind of left-over. Let's clean it up and respin.
>
> Also, while we are at it:
>
> -
Ticket has been filed - https://issues.apache.org/jira/browse/IGNITE-879
--Yakov
2015-05-07 23:13 GMT+03:00 Valentin Kulichenko <
valentin.kuliche...@gmail.com>:
> Got it. Yes, looks like a bug.
>
> --
> Val
>
> On Thu, May 7, 2015 at 12:54 PM, Vladimir Ozerov
> wrote:
>
> > Message listeners a
Yakov Zhdanov created IGNITE-879:
Summary: Fix message and event listeners subscription
Key: IGNITE-879
URL: https://issues.apache.org/jira/browse/IGNITE-879
Project: Ignite
Issue Type: Bug
On Fri, May 8, 2015 at 12:53 AM, Yakov Zhdanov wrote:
> By default data streamer does not do puts, but does cache loading.
>
I still think metrics should be updated, no? From user standpoint there is
no difference between puts and loading.
>
> --Yakov
>
> 2015-05-07 19:20 GMT+03:00 Andrey Gura
By default data streamer does not do puts, but does cache loading.
--Yakov
2015-05-07 19:20 GMT+03:00 Andrey Gura :
> I think it's possible. If allowOverwrite isn't set then entry updates
> through initialValue method. All we need it is just update metrics from
> this method.
>
> On Wed, Apr 29,
I also think that Ignite Web Configuration and Web Visor are not related to
each other.
They only have in common brand UI look and feel.
On Fri, May 8, 2015 at 2:18 PM, Sergey Evdokimov
wrote:
> If I understand correctly, configuration wizards is a separated
> web-application to generate Ignite
Pavel Konstantinov created IGNITE-878:
-
Summary: Large GC if load data to the cache using datastreamer
Key: IGNITE-878
URL: https://issues.apache.org/jira/browse/IGNITE-878
Project: Ignite
Sure, I'll add this javadoc.
On Fri, May 8, 2015 at 10:16 AM, Dmitriy Setrakyan
wrote:
> On Fri, May 8, 2015 at 12:05 AM, Semyon Boikov
> wrote:
>
> > Replied.
> >
>
> Thanks!
>
> I actually agree with the user. Can you please add javadoc to
> PluginConfiguration describing how to plug it in?
>
If I understand correctly, configuration wizards is a separated
web-application to generate Ignite configuration before Ignite started.
Web-visor should start jetty server inside node JVM when node started,
similarly as "ignite-rest-http".
I have experience in web development but I didn't use Angu
On Fri, May 8, 2015 at 12:05 AM, Semyon Boikov wrote:
> Replied.
>
Thanks!
I actually agree with the user. Can you please add javadoc to
PluginConfiguration describing how to plug it in?
>
> On Thu, May 7, 2015 at 9:47 AM, Dmitriy Setrakyan
> wrote:
>
> > We have a user asking about this on
Replied.
On Thu, May 7, 2015 at 9:47 AM, Dmitriy Setrakyan
wrote:
> We have a user asking about this on forums:
> http://apacheignite.readme.io/v1.0/discuss/554a6dc6156a480d00e29262
>
> Can someone respond please?
>
> D.
>
50 matches
Mail list logo
