GitHub user ptupitsyn opened a pull request:
https://github.com/apache/ignite/pull/1255
IGNITE-4258 .NET: Fix BinaryReader to use current stream position
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ptupitsyn/ignite ignite-425
Pavel Tupitsyn created IGNITE-4258:
--
Summary: .NET: BinaryReader ignores current stream position
Key: IGNITE-4258
URL: https://issues.apache.org/jira/browse/IGNITE-4258
Project: Ignite
Issue
Alexey Kuznetsov created IGNITE-4257:
Summary: Web Console: Download project on Summary screen is broken
under Safari browser
Key: IGNITE-4257
URL: https://issues.apache.org/jira/browse/IGNITE-4257
Prachi, thanks, looks good to be.
BTW, I’ve started refining the overall SQL documentation. At the moment I’ve
created a new section named “SQL” located right below “Data Grid” and that
sections contains a dedicated page about the indexes. So the new link to the
page you’re referring to is the
Valentin Kulichenko created IGNITE-4256:
---
Summary: Support closure broadcast with locked cache partitions
Key: IGNITE-4256
URL: https://issues.apache.org/jira/browse/IGNITE-4256
Project: Ignite
I tend to agree with Denis. I see only these differences between Hadoop
Accelerator and Fabric builds (correct me if I miss something):
- Limited set of available modules and no optional modules in Hadoop
Accelerator.
- No ignite-hadoop module in Fabric.
- Additional scripts, configs a
Valentin Kulichenko created IGNITE-4255:
---
Summary: Improve IgniteCache.loadCache API
Key: IGNITE-4255
URL: https://issues.apache.org/jira/browse/IGNITE-4255
Project: Ignite
Issue Type:
Guys,
I created a ticket for this:
https://issues.apache.org/jira/browse/IGNITE-4255
Feel free to provide comments.
-Val
On Sat, Nov 19, 2016 at 6:56 AM, Yakov Zhdanov wrote:
> >
> >
> > Why not store the partition ID in the database and query only local
> > partitions? Whatever approach we d
> On the separate note, in the Bigtop, we start looking into changing the way we
> deliver Ignite and we'll likely to start offering the whole 'data fabric'
> experience instead of the mere "hadoop-acceleration”.
And you still will be using hadoop-accelerator libs of Ignite, right?
I’m thinking o
+1
On Nov 16, 2016 9:15 AM, "Denis Magda" wrote:
> +1
>
> —
> Denis
>
> > On Nov 16, 2016, at 2:08 AM, Pavel Tupitsyn
> wrote:
> >
> > Following the discussion on Upsource [1],
> > I would like to call a vote on accepting it as our official code review
> > tool.
> >
> > [ ] +1 approve
> > [ ]
Cos, I see your point, but I think this one falls under procedural issue,
no?
On Mon, Nov 21, 2016 at 12:21 PM, Konstantin Boudnik wrote:
> What are we voting for this?
>
> Fortunately, Apache isn't about democracy. [1]
>
> [1] https://www.apache.org/foundation/voting.html
>
> Cos
>
> On Wed, No
Fixed. Please review -
http://apacheignite.gridgain.org/v1.7/docs/sql-queries#off-heap-sql-indexes
-P
On Mon, Nov 7, 2016 at 9:36 AM, Denis Magda wrote:
> Sergi,
>
> May be you use
> some weird email client which renders >> signs wrong?
>
>
> Right, my Apple’s Mail agent omitted ‘>’ character f
Ok,
This was a great discussion, thanks for the deep insight, Roman!
looks like this thread has stewed for a while and it is time to [VOTE]. The
following candidates were put forward during the [DISCUSS] (in the order of
their appearance on the thread):
Dmitriy Setrakyan
Vladimir Ozerov
K
What are we voting for this?
Fortunately, Apache isn't about democracy. [1]
[1] https://www.apache.org/foundation/voting.html
Cos
On Wed, Nov 16, 2016 at 01:08PM, Pavel Tupitsyn wrote:
> Following the discussion on Upsource [1],
> I would like to call a vote on accepting it as our official code
What Denis said: spark has been added to the Hadoop accelerator as a way to
boost the performance of more than just MR compute of the Hadoop stack, IIRC.
For what it worth, Spark is considered a part of Hadoop at large.
On the separate note, in the Bigtop, we start looking into changing the way w
GitHub user isapego opened a pull request:
https://github.com/apache/ignite/pull/1254
IGNITE-4249: Sending request in one packet now.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-4249
Alternative
Val,
Ignite Hadoop module includes not only the map-reduce accelerator but Ignite
Hadoop File System component as well. The latter can be used in deployments
like HDFS+IGFS+Ignite Spark + Spark.
Considering this I’m for the second solution proposed by you: put both 2.10 and
2.11 ignite-spark
Denis Magda created IGNITE-4254:
---
Summary: Ignite Hadoop Distribution support Ignite Spark of 2.11
only
Key: IGNITE-4254
URL: https://issues.apache.org/jira/browse/IGNITE-4254
Project: Ignite
Have you tried to alter the code to check that the idea works? If it’s so, then
let’s wait for Vladimir Ozerov input. He should confirm that this is what’s
needed.
—
Denis
> On Nov 21, 2016, at 7:59 AM, Andrey Mashenkov
> wrote:
>
> I've found BinaryContext.mustDeserialize(Class cls) method
I've found BinaryContext.mustDeserialize(Class cls) method can prevent
serialization if it return true.
We can add a classname check against exclusions patterns, that can be found
in certain classpath, e.g. in "META/binary.context.excluded.classes". Then
file with exclusion patterns can be added t
GitHub user sboikov opened a pull request:
https://github.com/apache/ignite/pull/1253
ignite-1.7.4
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-1.7.4
Alternatively you can review and apply these
GitHub user tledkov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/1252
IGNITE-3961 IGFS: Support direct PROXY mode invocation in method: affinity
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/ap
I've added GridH2IndexingGeoBinarySelfTest (GridH2IndexingGeoSelfTest with
BinaryMarshaller). Test failed on cache configuration step due to
inconsistent types.
It seems, excluding should be done in BinaryMarshaller internals.
Caused by: org.h2.message.DbException: Feature not supported: "spatial
Github user tledkov-gridgain closed the pull request at:
https://github.com/apache/ignite/pull/1114
---
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 kdudkov closed the pull request at:
https://github.com/apache/ignite/pull/1233
---
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 feature is en
GitHub user tledkov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/1251
IGNITE-2356 IGFS client should be able to failover in case of server crash.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/
Github user tledkov-gridgain closed the pull request at:
https://github.com/apache/ignite/pull/1155
---
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 kdudkov closed the pull request at:
https://github.com/apache/ignite/pull/1229
---
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 feature is en
Semen Boikov created IGNITE-4253:
Summary: Use github branch approach for switching between tested
builds
Key: IGNITE-4253
URL: https://issues.apache.org/jira/browse/IGNITE-4253
Project: Ignite
GitHub user tledkov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/1250
IGNITE-4239 Public thread pool starvation is cause of deadlock when user's
jobs calls cache.size()
You can merge this pull request into a Git repository by running:
$ git pull https
Github user tledkov-gridgain closed the pull request at:
https://github.com/apache/ignite/pull/1242
---
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
Pavel Konstantinov created IGNITE-4252:
--
Summary: ClassCastException with local cache query
Key: IGNITE-4252
URL: https://issues.apache.org/jira/browse/IGNITE-4252
Project: Ignite
Issue
32 matches
Mail list logo
