Igniters,
I noted that in our AtomicConfiguration we have PARTITIONED cache with
backups=0. This appears to be very unreliable configuration which do not
survive node crashes.
For example, if user create AtomicLong with this config and the kill a
node, he could receive error message "Failed to fin
"v1" or "v2" doesn't stand for Hadoop 1.x and Hadoop 2.x. Instead, this is
about either old "FileSystem" API or new "AbstractFileSystem" API. In your
stack trace I see that you use "FileSystem", so you should try setting "v1".
Vladimir.
On Thu, Mar 31, 2016 at 8:44 AM, pawanpawar wrote:
> Thank
Thanks for your reply, I am using Hadoop 2, so I used "v2". Is this for
hadoop version?
On Thu, Mar 31, 2016 at 11:11 AM, Vladimir Ozerov [via Apache Ignite
Developers] wrote:
> Hi,
>
> Please double-check that you set correct class name in *core-site.xml*. It
> seems to me that you should chang
Hi,
Please double-check that you set correct class name in *core-site.xml*. It
seems to me that you should change "v2" to "v1":
org.apache.ignite.hadoop.fs.*v1*.IgniteHadoopFileSystem
Vladimir.
On Thu, Mar 31, 2016 at 1:22 AM, pawanpawar wrote:
> Hi team I am getting error after configuring ig
Hi team I am getting error after configuring ignite with hadoop and hive.
when I try to run any hadoop cmd it show me this error.
pawanpawar@cloud:~$ hadoop fs -ls -R /
-ls: Fatal internal error
java.lang.RuntimeException: java.lang.NoSuchMethodException:
org.apache.ignite.hadoop.fs.v2.IgniteHadoo
Denis Magda created IGNITE-2921:
---
Summary: ScanQueries over local partitions are not optimal
Key: IGNITE-2921
URL: https://issues.apache.org/jira/browse/IGNITE-2921
Project: Ignite
Issue Type:
GitHub user isapego opened a pull request:
https://github.com/apache/ignite/pull/589
IGNITE-2920: IgniteError now derives from std::runtime_error.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/isapego/ignite ignite-2920
Altern
Igor Sapego created IGNITE-2920:
---
Summary: CPP: IgniteError should be derived from
std::runtime_error not from std::exception
Key: IGNITE-2920
URL: https://issues.apache.org/jira/browse/IGNITE-2920
Proj
Denis Magda created IGNITE-2919:
---
Summary: Visor CMD: Add ability to attach custom scripts to alerts
Key: IGNITE-2919
URL: https://issues.apache.org/jira/browse/IGNITE-2919
Project: Ignite
Issu
On Wed, Mar 30, 2016 at 2:20 PM, Roman wrote:
> Raul,
>
> Small comment from me.
>
> >* As a Flink sink => inject data directly into a cache via a DataStreamer.
> After reviews, IGNITE-813 is exactly this functionality.
>
>
That's cool, Roman! The idea would be to host these (richer) modules as
F
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/546
---
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 enab
Igor Sapego created IGNITE-2918:
---
Summary: CPP: Add C++ test suits to TeamCity.
Key: IGNITE-2918
URL: https://issues.apache.org/jira/browse/IGNITE-2918
Project: Ignite
Issue Type: Task
GitHub user vldpyatkov opened a pull request:
https://github.com/apache/ignite/pull/588
IGNITE-2668
MBean creation fails if cache name contains ':' character
Write attribute, which contains cache name, in quote
You can merge this pull request into a Git repository by running:
Raul,
Small comment from me.
>* As a Flink sink => inject data directly into a cache via a DataStreamer.
After reviews, IGNITE-813 is exactly this functionality.
-Roman
GitHub user ilantukh opened a pull request:
https://github.com/apache/ignite/pull/587
GG-10988 : GridCacheConcurrentMap redesign.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ilantukh/ignite ignite-gg-10988
Alternatively you
Vladimir Ozerov created IGNITE-2917:
---
Summary: ODBC: Add configuration validation.
Key: IGNITE-2917
URL: https://issues.apache.org/jira/browse/IGNITE-2917
Project: Ignite
Issue Type: Task
Vladimir Ozerov created IGNITE-2916:
---
Summary: ODBC: Merge host and port into a single property.
Key: IGNITE-2916
URL: https://issues.apache.org/jira/browse/IGNITE-2916
Project: Ignite
Issu
Vladimir Ozerov created IGNITE-2915:
---
Summary: ODBC: Remove fine-grained properties from
OdbcConfiguration.
Key: IGNITE-2915
URL: https://issues.apache.org/jira/browse/IGNITE-2915
Project: Ignite
GitHub user isapego opened a pull request:
https://github.com/apache/ignite/pull/586
IGNITE-2914: Removed MakeDate and MakeTimestamp.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/isapego/ignite ignite-2914
Alternatively you c
Hello from the Apache Ignite community!
Last year there was an interesting thread [1] about such integration.
Unfortunately there's been little follow-through, so let's try and fix that
in 2016 ;-)
I'm sure a lot has changed in the Flink community, with the recent
graduation and 1.0 release, so I
Igor Sapego created IGNITE-2914:
---
Summary: ODBC: QueriesTestSuite from odbc-test uses outdated
version of MakeDate and MakeTimestamp.
Key: IGNITE-2914
URL: https://issues.apache.org/jira/browse/IGNITE-2914
Sergi Vladykin created IGNITE-2913:
--
Summary: SQL query with EXISTS() expression fails on partitioned
cache.
Key: IGNITE-2913
URL: https://issues.apache.org/jira/browse/IGNITE-2913
Project: Ignite
I think this approach works unless user does not initiate number of
concurrent cache operations greater than MSG_QUEUE_SIZE. Where msg queue
size default is 1024, but still configurable.
Thanks!
--
Yakov Zhdanov, Director R&D
*GridGain Systems*
www.gridgain.com
2016-03-30 11:44 GMT+03:00 Vladimi
Dmitriyff created IGNITE-2912:
-
Summary: Implement support focus out to composite field
Key: IGNITE-2912
URL: https://issues.apache.org/jira/browse/IGNITE-2912
Project: Ignite
Issue Type: Sub-tas
Pavel Tupitsyn created IGNITE-2911:
--
Summary: ClusterGroup.forDaemons does not work
Key: IGNITE-2911
URL: https://issues.apache.org/jira/browse/IGNITE-2911
Project: Ignite
Issue Type: Bug
Does it mean that if cache update rate is greater than filter execution
rate, then at some point we will stop reading messages from socket? If yes,
then it seems we still cannot execute cache operations:
1) Filter starts cache operation for a key. Current node is backup for this
key.
2) Cache messa
Vladimir,
Communication should stop reading from connection is there are too many
unprocessed messages. Sender will be blocked on putting message to queue.
--Yakov
2016-03-30 11:11 GMT+03:00 Vladimir Ozerov :
> Guys,
>
> Can you explain how backpressure control is implemented? What if event
> a
Guys,
Can you explain how backpressure control is implemented? What if event
arrival speed is greater than filter processing speed?
On Wed, Mar 30, 2016 at 10:37 AM, Semyon Boikov
wrote:
> Andrey,
>
> I agree that current situation with threading in Ignite is very
> inconvenient when user callb
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/560
---
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 enab
Andrey,
I agree that current situation with threading in Ignite is very
inconvenient when user callbacks execute some non-trivial code. But
changing this to async dispatch is huge refactoring, even changing this
just for continuous queries callback is not so easy task.
We can start with https://i
Just checked and our spec jar passes sigtest. Not sure for this week
but think we can run a vote next one if nobody objects - don't
hesitate to ping if nothing happens ;).
Romain Manni-Bucau
@rmannibucau | Blog | Github | LinkedIn | Tomitriber
2016-03-30 9:20 GMT+02:00 Dmitriy Setrakyan :
> TCK
TCK does contain the sigtest:
https://github.com/jsr107/jsr107tck/tree/master/sigtest
Looking forward to getting the 1.0 version :)
D.
On Tue, Mar 29, 2016 at 11:12 PM, Romain Manni-Bucau
wrote:
> Le 30 mars 2016 01:45, "Dmitriy Setrakyan" a
> écrit :
> >
> > I just mention to mention that Ap
32 matches
Mail list logo
