10:18 GMT+03:00 Sergi Vladykin sergi.vlady...@gmail.com:
Guys,
I've just updated SQL Queries documentation, please read and send your
feedback.
http://apacheignite.gridgain.org/v1.3/docs/sql-queries
Sergi
. I would prefer example that example can be copied-and-pasted and
launched. Can we add cache config, indexes, and cache loading?
3. Need more accent on necessity of indexed types configuration. Can you
put this into code box?
--Yakov
2015-08-19 10:18 GMT+03:00 Sergi Vladykin sergi.vlady
Agree, I don't like current approach as well and prefer explicit imports.
Since they are automatically maintained by IDE it will be easy enough to
change this.
Sergi
2015-08-20 0:37 GMT+03:00 Raul Kripalani ra...@apache.org:
(Found out that org.jsr166 is an internal package in this case).
Guys,
I've just updated SQL Queries documentation, please read and send your
feedback.
http://apacheignite.gridgain.org/v1.3/docs/sql-queries
Sergi
Agree, the whole concept of grid name looks weird if nodes with different
names still work as a single topology.
Though we will need to refactor our tests if we are going to remove it..
Sergi
2015-08-18 13:42 GMT+03:00 Yakov Zhdanov yzhda...@apache.org:
Guys,
I am thinking of deprecating
Sergi Vladykin created IGNITE-1259:
--
Summary: OFFSET clause does not work correctly in SQL queries
Key: IGNITE-1259
URL: https://issues.apache.org/jira/browse/IGNITE-1259
Project: Ignite
Sergi Vladykin created IGNITE-1249:
--
Summary: Incorrect example Group index example.
Key: IGNITE-1249
URL: https://issues.apache.org/jira/browse/IGNITE-1249
Project: Ignite
Issue Type: Bug
Sergi Vladykin created IGNITE-1247:
--
Summary: Support @QuerySqlField.Group annotation outside of
@QuerySqlField
Key: IGNITE-1247
URL: https://issues.apache.org/jira/browse/IGNITE-1247
Project
a broadcast which is a performance hit. I still vote that we
take this performance hit and do the broadcast (optimized with batching, of
course), and execute the query instead of throwing an exception.
D.
On Fri, Aug 7, 2015 at 3:40 AM, Sergi Vladykin sergi.vlady...@gmail.com
wrote:
Alexey
I've created respective Jira issue
https://issues.apache.org/jira/browse/IGNITE-1232
Sergi
2015-08-11 9:31 GMT+03:00 Dmitriy Setrakyan dsetrak...@apache.org:
On Mon, Aug 10, 2015 at 11:26 PM, Sergi Vladykin sergi.vlady...@gmail.com
wrote:
I was thinking about protecting users from doing
Sergi Vladykin created IGNITE-1232:
--
Summary: Support distributed SQL JOIN
Key: IGNITE-1232
URL: https://issues.apache.org/jira/browse/IGNITE-1232
Project: Ignite
Issue Type: Improvement
Igniters,
I'm going to start working on distributed SQL joins soon and want to put my
thoughts on this matter here.
To provide collocated and non-collocated joins we need to know affinity key
for each table.
For example we have a table `Organization(id int)` where `id` is affinity
key and
Alexey,
1. Yes, in my plan it should work exactly like that: if both keys in join
are affinity keys, then we are fully collocated, if only one then we can
run join remotely as described, if none of them we will fail to run the
query.
2. I mean we don't have values for these affinity keys in our
Sergi Vladykin created IGNITE-1197:
--
Summary: GridDhtInvalidPartitionException in
GridDhtLocalPartition.release
Key: IGNITE-1197
URL: https://issues.apache.org/jira/browse/IGNITE-1197
Project
.
Thoughts?
D.
On Mon, Aug 3, 2015 at 10:54 AM, Raul Kripalani ra...@apache.org wrote:
Inline.
On Mon, Aug 3, 2015 at 5:14 PM, Sergi Vladykin sergi.vlady...@gmail.com
wrote:
Raul,
Again, for the sake of unification I don't see why client will be OSGi
compliant but server
Sergi Vladykin created IGNITE-1193:
--
Summary: Improve thread pool selection logic for operations
Key: IGNITE-1193
URL: https://issues.apache.org/jira/browse/IGNITE-1193
Project: Ignite
2015-08-03 15:23 GMT+02:00 Sergi Vladykin sergi.vlady...@gmail.com:
Raul,
As far as I understand your main concern is that Ignite is incompatible
with OSGi (other points seem to be more about your personal feelings
about
right engineering practices than about real problems). I believe
and Android clients,
but this did not actually pay off..
Sergi
2015-08-03 18:40 GMT+03:00 Sergi Vladykin sergi.vlady...@gmail.com:
Gianfranco,
Honestly, I don't like that we allowing to run computations on clients,
because anyways in most cases it is meaningless, but now we must keep
Dmitriy,
I like the idea, lets better use Jira.
Sergi
2015-07-31 21:27 GMT+03:00 Dmitriy Setrakyan dsetrak...@apache.org:
Nick,
I have noticed that you and some others usually send notification emails
about starting or finishing work on some ticket.
My personal opinion is that moving
in old nodes to avoid complexity.
Sergi
On Jul 31, 2015 10:50 AM, Valentin Kulichenko
valentin.kuliche...@gmail.com wrote:
On Fri, Jul 31, 2015 at 12:30 AM, Dmitriy Setrakyan dsetrak...@apache.org
wrote:
On Fri, Jul 31, 2015 at 12:06 AM, Sergi Vladykin
sergi.vlady...@gmail.com
wrote
Guys,
We had a problem with thread starvation in PUBLIC pool because of queries
as described in https://issues.apache.org/jira/browse/IGNITE-1174
I switched it to SYSTEM pool but this can cause delays for other cache
operations like put/get if we have many long running queries.
I propose adding
:18, Sergi Vladykin wrote:
I meant this wiki page:
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
Sergi
2015-07-30 12:17 GMT+03:00 Sergi Vladykin sergi.vlady...@gmail.com:
Also a wiki page should contain instructions how to provide patch for
release branch
Sergi Vladykin created IGNITE-1174:
--
Summary: Switch default thread pool to SYSTEM for SQL queries.
Key: IGNITE-1174
URL: https://issues.apache.org/jira/browse/IGNITE-1174
Project: Ignite
and it is not that easy
=)
2015-07-30 12:07 GMT+03:00 Sergi Vladykin sergi.vlady...@gmail.com:
Also the page contains outdated instructions about sprints:
*The master branch contains the last released version. The sprint-N
branch contains the latest code for the Nth sprint*
Sergi
2015
I meant this wiki page:
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
Sergi
2015-07-30 12:17 GMT+03:00 Sergi Vladykin sergi.vlady...@gmail.com:
Also a wiki page should contain instructions how to provide patch for
release branch instead of master.
By the way since we
Guys,
Why don't we have instructions on how to create a patch here?
http://ignite.incubator.apache.org/community/contribute.html#contribute
Can someone fix?
Sergi
Also the page contains outdated instructions about sprints:
*The master branch contains the last released version. The sprint-N
branch contains the latest code for the Nth sprint*
Sergi
2015-07-30 12:05 GMT+03:00 Sergi Vladykin sergi.vlady...@gmail.com:
Guys,
Why don't we have
I don't think this will work in distributed environment correctly now. If
you want CSV export it must be implemented outside of SQL layer.
Sergi
2015-07-29 14:13 GMT+03:00 Alexey Kuznetsov akuznet...@gridgain.com:
Sergi Vladykin,
I remember that we have same issue with explain queries.
I
Guys,
I would say Ignite is quite a big and quite complex project. Also we have
really tough requirements for performance, stability, backward
compatibility, etc... Having said that it is really easy to break something
even with minor change like switching type of collection to another one.
And I
Guys,
I just merged to master bunch of SQL engine improvements related to
aggregate functions. Now we support any kind of expressions containing
aggregates (e.g. *MAX(x) - MIN(x) / COUNT(*)* ) in correct distributed
fashion.
Sergi
Sergi Vladykin created IGNITE-1140:
--
Summary: Find aggregate functions in HAVING clause or rewrite
query to put all aggregates to SELECT clause.
Key: IGNITE-1140
URL: https://issues.apache.org/jira/browse/IGNITE
Sergi Vladykin created IGNITE-1141:
--
Summary: Check if sorting is done over aggregated expression,
otherwise we can sort and use offset-limit.
Key: IGNITE-1141
URL: https://issues.apache.org/jira/browse/IGNITE
2015-07-21 10:01 GMT-07:00 Sergi Vladykin sergi.vlady...@gmail.com:
I think O(N) reasoning does not make a real sense here since N is
always
small, lets not fool ourselves.
To my mind operation cost of cache access (with all busy locks...),
hashCode/equals and stuff like that has
Sharma atri.j...@gmail.com:
Are you referring to JSONB here?
On Thu, Jul 16, 2015 at 1:10 PM, Sergi Vladykin sergi.vlady...@gmail.com
wrote:
Guys, specially Alexey G.
I've attended PostgreSQL conference and there was a talk about
unstructured
data format.
They had an interesting idea
+1
Sergi
2015-07-10 0:34 GMT+03:00 Alexey Goncharuk alexey.goncha...@gmail.com:
+1
2015-07-09 1:39 GMT-07:00 Dmitriy Setrakyan dsetrak...@apache.org:
I would like to start a vote on graduating Apache Ignite to TLP.
Status page: http://incubator.apache.org/projects/ignite.html
Yes, I think we should rename it.
Sergi
2015-07-01 2:58 GMT-07:00 Alexey Kuznetsov akuznet...@gridgain.com:
Hi!
As we planning to have various features in Web config: config, sql,
monitor, deploy,...
Why do we name it Web Config? I think that Web Control Center is a
better name?
Sergi Vladykin created IGNITE-1077:
--
Summary: SQL Query hangs.
Key: IGNITE-1077
URL: https://issues.apache.org/jira/browse/IGNITE-1077
Project: Ignite
Issue Type: Bug
Reporter
it downloadable in the easiest way.
D.
On Tue, Jun 30, 2015 at 7:52 AM, Sergi Vladykin sergi.vlady...@gmail.com
wrote:
Guys,
To be honest I don't know why we choose this stack which is completely
alien to java when our main product is java based. I'm sure in the future
we will need better
And there is nothing to do from scratch here, all the html and client side
js are the same, just switch backend.
Sergi
2015-06-30 8:17 GMT-07:00 Sergi Vladykin sergi.vlady...@gmail.com:
I think at current stage if it takes two days to switch things, then it
makes sense. We will not be able
Guys,
To be honest I don't know why we choose this stack which is completely
alien to java when our main product is java based. I'm sure in the future
we will need better level of integration between them not only for Ignite
SQL schema import.
Jetty it is a battle tested server, I think we can
at 8:18 AM, Sergi Vladykin
sergi.vlady...@gmail.com
wrote:
And there is nothing to do from scratch here, all the html and
client
side
js are the same, just switch backend.
Sergi
2015-06-30 8:17 GMT-07:00 Sergi Vladykin
sergi.vlady
Sergi Vladykin created IGNITE-1027:
--
Summary: Possible data loss in replicated cache on unstable
topology.
Key: IGNITE-1027
URL: https://issues.apache.org/jira/browse/IGNITE-1027
Project: Ignite
+1
2015-06-18 13:58 GMT+03:00 Atri Sharma atri.j...@gmail.com:
Not sure if my vote counts, but I have a +1
On 18 Jun 2015 16:25, Dmitriy Setrakyan dsetrak...@apache.org wrote:
Thanks Gianfranco!
Can we get more votes from other PPMC members?
D.
On Wed, Jun 17, 2015 at 12:55 AM,
sense here.
Sergi
2015-06-05 1:16 GMT+03:00 Dmitriy Setrakyan dsetrak...@apache.org:
Sergi,
I see you have plain index and then sorted index. Do we even have indexes
that are not sorted in Ignite?
D.
On Thu, Jun 4, 2015 at 1:00 AM, Sergi Vladykin sergi.vlady...@gmail.com
wrote:
I
{
SQLGeoSpatialIndex(String idxName, String fieldName)
}
class FulltextIndex extends Index {
void addField(String fieldName);
}
Sergi
2015-06-01 19:13 GMT+03:00 Sergi Vladykin sergi.vlady...@gmail.com:
I would do index creation/drop through custom messages in discovery. We
already use
On Mon, Jun 1, 2015 at 9:41 PM, Sergi Vladykin sergi.vlady...@gmail.com
wrote:
Yo guys!
I think it is time to start implementing this feature since it became
really relevant lately.
Currently we have static indexing configuration via either
CacheConfiguration.setIndexedTypes
How hard will it be to support both versions of Scala in the project?
Also what do you this about GridGain's Visor, will it work with both
versions? I don't think we should break known third party software based on
Apache Ignite.
Sergi
2015-06-01 13:50 GMT+03:00 Alexey Kuznetsov
+1
2015-05-21 12:22 GMT+03:00 Branko Čibej br...@apache.org:
On 20.05.2015 22:37, Yakov Zhdanov wrote:
Guys,
We have uploaded release candidate to
https://dist.apache.org/repos/dist/dev/incubator/ignite/1.1.0-rc7/
Tag name is
ignite-1.1.0-incubating-rc7
RC7 changes:
Fixed
Sergi Vladykin created IGNITE-930:
-
Summary: Primitive values do not get indexed.
Key: IGNITE-930
URL: https://issues.apache.org/jira/browse/IGNITE-930
Project: Ignite
Issue Type: Bug
Current workaround is to create separate class with single annotated
primitive field.
Created issue https://issues.apache.org/jira/browse/IGNITE-930
Will fix it soon.
Sergi
2015-05-21 4:25 GMT+03:00 Valentin Kulichenko valentin.kuliche...@gmail.com
:
Igniters (especially Sergi),
What
As I see we don't need to add any Zabbix related dependencies to the
product. It contains Java gateway which uses JMX.
Since Ignite already exposes majority of metrics to JMX all that we need is
to create Zabbix templates for monitoring screens with those metrics.
Sergi
2015-05-19 3:24 GMT+03:00
+1
Sergi
2015-05-15 3:14 GMT+03:00 Alexey Goncharuk alexey.goncha...@gmail.com:
+1, the release looks good to me.
2015-05-12 10:55 GMT-07:00 Yakov Zhdanov yzhda...@apache.org:
Guys,
We have uploaded release candidate to
Yes, we need to make sure that we will not get index snapshot in any random
state.
Sergi
2015-05-12 20:29 GMT+03:00 Yakov Zhdanov yzhda...@apache.org:
We need to make sure that partition is in the OWNING state on the node
processing the request. I don't see how your approach guarantees that.
.
I expect that take first 100 rows for scan query should be very
fast.
On Thu, May 7, 2015 at 10:19 PM, Sergi Vladykin
sergi.vlady...@gmail.com
wrote:
Alexey,
How did you come to this conclusion? I don't see anything like
that
in
our
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 akuznet...@gridgain.com:
Issue created:
Alexey,
How did you come to this conclusion? I don't see anything like that in our
code, we just take keySet or primaryKeySet iterator and fetch it page by
page.
Sergi
2015-05-07 9:58 GMT+03:00 Dmitriy Setrakyan dsetrak...@apache.org:
I have filed a ticket for this issue:
In 847 I think we can just ignore requests for which we can't find node in
discovery.
BTW, may be it does make sense for IoManager to drop such messages?
Sergi
2015-04-30 20:56 GMT+03:00 Yakov Zhdanov yzhda...@apache.org:
Guys,
We discovered two issues that seem not so critical, but I
Sergi Vladykin created IGNITE-757:
-
Summary: Use CacheObject in QueryProcessor and indexing
Key: IGNITE-757
URL: https://issues.apache.org/jira/browse/IGNITE-757
Project: Ignite
Issue Type
Guys,
I noticed that we have awaitPartitionMapExchange() call in
startGridsMultithreaded() in tests. This way we are hiding from ourselves
whole class of repartitioning problems. I would prefer having this call per
test if needed and not have it by default. What do you think?
Sergi
Guys,
I just noticed that multicast discovery does not work properly on my mac.
It seems to be IPv6 related issue again. I can workaround it by adding
-Djava.net.preferIPv4Stack=true option but it should work without it. Does
anyone experience the same problem?
Sergi
+1
Sergi
2015-03-30 11:51 GMT+03:00 Semyon Boikov sboi...@gridgain.com:
+1
On Mon, Mar 30, 2015 at 11:18 AM, Vladimir Ozerov voze...@gridgain.com
wrote:
+1, appears to be fine.
On Mon, Mar 30, 2015 at 9:41 AM, Valentin Kulichenko
valentin.kuliche...@gmail.com wrote:
Looks
Sweet!
Sergi
2015-03-25 11:35 GMT+03:00 Dmitriy Setrakyan dsetrak...@apache.org:
The first official Apache Ignite release (albeit release candidate) was
uploaded and the download page is updated:
https://ignite.incubator.apache.org/download.html
Congratulations to everyone!
D.
I agree with Vladimir. Extending Future and breaking its contract is the
same thing as if we were supporting JCache but in incompatible way. Why we
run TCK then?
I'm not sure about collections of different futures but I remember myself
writing utility methods like
getFutureResult(Future fut) {
+1 for RC3
Sergi
2015-03-16 0:19 GMT+03:00 Konstantin Boudnik c...@apache.org:
On Sun, Mar 15, 2015 at 09:46AM, Branko Čibej wrote:
On 15.03.2015 09:28, Konstantin Boudnik wrote:
On Sun, Mar 15, 2015 at 07:55AM, Branko Čibej wrote:
On 15.03.2015 07:15, Konstantin Boudnik wrote:
+1
[
https://issues.apache.org/jira/browse/IGNITE-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14363071#comment-14363071
]
Sergi Vladykin commented on IGNITE-483:
---
First of all I would recommend to check out
[
https://issues.apache.org/jira/browse/IGNITE-484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14362558#comment-14362558
]
Sergi Vladykin commented on IGNITE-484:
---
Uncomment
Sergi Vladykin created IGNITE-484:
-
Summary: Support node restarts in new SQL
(IgniteCacheQueryNodeRestartSelfTest)
Key: IGNITE-484
URL: https://issues.apache.org/jira/browse/IGNITE-484
Project
Sergi Vladykin created IGNITE-437:
-
Summary: Create test data model and testing framework for
distributed SQL.
Key: IGNITE-437
URL: https://issues.apache.org/jira/browse/IGNITE-437
Project: Ignite
Sergi Vladykin created IGNITE-392:
-
Summary: Remove VisorQueryConfiguration
VisorCacheQueryConfiguration
Key: IGNITE-392
URL: https://issues.apache.org/jira/browse/IGNITE-392
Project: Ignite
I think that having annotations only on public API is ok. @NotNull and
@Contract seem to be extra effort.
Sergi
2015-02-09 9:33 GMT+03:00 Dmitriy Setrakyan dsetrak...@apache.org:
I generally found myself suppressing IDE warnings whenever these
annotations are used. Personally, I would not,
[
https://issues.apache.org/jira/browse/IGNITE-190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergi Vladykin closed IGNITE-190.
-
Refactor query examples to use new API
--
Key
[
https://issues.apache.org/jira/browse/IGNITE-259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergi Vladykin resolved IGNITE-259.
---
Resolution: Fixed
Assignee: Ilya Suntsov (was: Sergi Vladykin)
Sql-benchmarks don't
[
https://issues.apache.org/jira/browse/IGNITE-212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergi Vladykin closed IGNITE-212.
-
CacheQueryExample: Failed to execute query on node
[
https://issues.apache.org/jira/browse/IGNITE-210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14322436#comment-14322436
]
Sergi Vladykin commented on IGNITE-210:
---
Fixed as part of IGNITE-212
[
https://issues.apache.org/jira/browse/IGNITE-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergi Vladykin closed IGNITE-210.
-
CacheQueryExample: Failed to execute query on node
Sergi Vladykin created IGNITE-246:
-
Summary: Need to add method boolean hasProperty(Object obj, String
ptyName) to protable processor
Key: IGNITE-246
URL: https://issues.apache.org/jira/browse/IGNITE-246
[
https://issues.apache.org/jira/browse/IGNITE-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergi Vladykin closed IGNITE-163.
-
Rename indexing spi
---
Key: IGNITE-163
URL
Sergi Vladykin created IGNITE-163:
-
Summary: Rename indexing spi
Key: IGNITE-163
URL: https://issues.apache.org/jira/browse/IGNITE-163
Project: Ignite
Issue Type: Bug
Reporter
[
https://issues.apache.org/jira/browse/IGNITE-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergi Vladykin reassigned IGNITE-132:
-
Assignee: Sergi Vladykin (was: Yakov Zhdanov)
Need to remove Hadoop methods from
[
https://issues.apache.org/jira/browse/IGNITE-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergi Vladykin updated IGNITE-163:
--
Fix Version/s: sprint-1
Rename indexing spi
---
Key: IGNITE
Mentors,
We have a LGPL dependency (we don't copy their code, only link with their
library). As far as I know we can ship our Apache 2.0 licensed binary
distribution with this library included while on the source code level it
is just a Maven dependency, right? Do we have any restrictions here? I
:
On 27.01.2015 08:57, Sergi Vladykin wrote:
Mentors,
We have a LGPL dependency (we don't copy their code, only link with
their
library). As far as I know we can ship our Apache 2.0 licensed binary
distribution with this library included while on the source code
level it
is just
[
https://issues.apache.org/jira/browse/IGNITE-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergi Vladykin updated IGNITE-140:
--
Assignee: Dmitriy Setrakyan (was: Sergi Vladykin)
Need to move TPS dependency into a separate
[
https://issues.apache.org/jira/browse/IGNITE-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergi Vladykin resolved IGNITE-134.
---
Resolution: Duplicate
IGNITE-140
Fix JTS dependency in indexing
[
https://issues.apache.org/jira/browse/IGNITE-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergi Vladykin updated IGNITE-132:
--
Assignee: Yakov Zhdanov (was: Sergi Vladykin)
Need to remove Hadoop methods from Ignite
[
https://issues.apache.org/jira/browse/IGNITE-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergi Vladykin resolved IGNITE-100.
---
Resolution: Fixed
merged to sprint-1
Get rid of JSON in Hadoop tests
May be its better to pass cache entry to predicate?
Also removeIf(key, val, IgniteBiPredicateK, V) signature looks weird to
me. Why pass value there?
regards,
Sergi Vladykin
2015-01-17 5:57 GMT+03:00 Dmitriy Setrakyan dsetrak...@apache.org:
I would like to propose adding 2 additional
Personally I prefer using Fabric fabfile.org for this kind of tasks. It is
in Python and Amazon has Python API as well, so creating such a tool should
be pretty straightforward.
regards,
Sergi Vladykin
2015-01-17 6:17 GMT+03:00 Dmitriy Setrakyan dsetrak...@apache.org:
I would like to start
I didn't notice that it goes to dev@ list. Then the only way is to filter
those emails on my side.
Thanks, Brane!
Sergi
2015-01-17 15:55 GMT+03:00 Branko Čibej br...@apache.org:
On 17.01.2015 12:54, Sergi Vladykin wrote:
Guys,
Can we somehow configure Jira not to send email notifications
In my view, using IngiteBiPredicateK, V instead of
IgnitePredicateCache.EntryK, Vl is easier to read and is more
Then it is better to introduce CachePredicateK,V for entry if readability
is your main concern.
consistent with EntryProcessorK,V design from JCache.
As far as I see
[
https://issues.apache.org/jira/browse/IGNITE-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergi Vladykin reassigned IGNITE-100:
-
Assignee: Sergi Vladykin
Get rid of JSON in Hadoop tests
91 matches
Mail list logo
