ty.GridSecurityProcessor
>
>
> чт, 21 нояб. 2019 г. в 12:41, Pavel Tupitsyn :
>
>> Good points, Sergey.
>> Maybe you are right, and Java-based compute without peer deployment is a
>> good first step for thin clients.
>>
>> On Thu, Nov 21, 2019 at 12:32 PM Sergey Kozlo
be designed but without that we open the hole to
kill cluster.
>
> On Thu, Nov 21, 2019 at 11:21 AM Sergey Kozlov
> wrote:
>
> > Hi Alex
> >
> > The idea is great. But I have some concerns that probably should be taken
> > into account for desi
e useful
> only for java thin client. And even with java thin client we should whether
> implement peer-class-loading for thin clients (this also requires two-way
> client-server communication) or put classes with executed closures to the
> server locally.
>
> What do you think a
-driver
2. https://issues.apache.org/jira/browse/IGNITE-6296
3. https://issues.apache.org/jira/browse/IGNITE-12372
--
Sergey Kozlov
GridGain Systems
www.gridgain.com
Sergey Kozlov created IGNITE-12372:
--
Summary: Thin Jdbc driver with collocated=true return per node
results
Key: IGNITE-12372
URL: https://issues.apache.org/jira/browse/IGNITE-12372
Project: Ignite
ed write lock (exclusive for some of the internal Ignite
> > > > >> process) will be introduced? I think it will help to solve a batch
> > of
> > > > >> problems, like:
> > > > >>
> > > > >> 1. defragmentation of all ca
; > > > > > >> for
> > > > > > >> > > this.
> > > > > > >> >
> > > > > > >> > 5% may be a big drop for some use-cases, so I think we
> should
> > > look
> > > > > at
> > > > > > >> how
> > > > > > >> > to improve performance, not how to make it worse.
> > > > > > >> >
> > > > > > >> >
> > > > > > >> > >
> > > > > > >> > > >> it is hard to maintain a data structure to choose "page
> > > from
> > > > > > >> free-list
> > > > > > >> > > with enough space closest to the beginning of the file".
> > > > > > >> > > We can just split each free-list bucket to the couple and
> > use
> > > > > first
> > > > > > >> for
> > > > > > >> > > pages in the first half of the file and the second for the
> > > last.
> > > > > > >> > > Only two buckets required here since, during the file
> > shrink,
> > > > > first
> > > > > > >> > > bucket's window will be shrank too.
> > > > > > >> > > Seems, this give us the same price on put, just use the
> > first
> > > > > bucket
> > > > > > >> in
> > > > > > >> > > case it's not empty.
> > > > > > >> > > Remove price (with merge) will be increased, of course.
> > > > > > >> > >
> > > > > > >> > > The compromise solution is to have priority put (to the
> > first
> > > > path
> > > > > > of
> > > > > > >> the
> > > > > > >> > > file), with keeping removal as is, and schedulable
> per-page
> > > > > > migration
> > > > > > >> for
> > > > > > >> > > the rest of the data during the low activity period.
> > > > > > >> > >
> > > > > > >> > Free lists are large and slow by themselves, it is expensive
> > to
> > > > > > >> checkpoint
> > > > > > >> > and read them on start, so as a long-term solution I would
> > look
> > > > into
> > > > > > >> > removing them. Moreover, not sure if adding yet another
> > > background
> > > > > > >> process
> > > > > > >> > will improve the codebase reliability and simplicity.
> > > > > > >> >
> > > > > > >> > If we want to go the hard path, I would look at free page
> > > tracking
> > > > > > >> bitmap -
> > > > > > >> > a special bitmask page, where each page in an adjacent block
> > is
> > > > > marked
> > > > > > >> as 0
> > > > > > >> > if it has free space more than a certain configurable
> > threshold
> > > > > (say,
> > > > > > >> 80%)
> > > > > > >> > - free, and 1 if less (full). Some vendors have successfully
> > > > > > implemented
> > > > > > >> > this approach, which looks much more promising, but harder
> to
> > > > > > implement.
> > > > > > >> >
> > > > > > >> > --AG
> > > > > > >> >
> > > > > > >>
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > >
> > > > > > > Best regards,
> > > > > > > Alexei Scherbakov
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > >
> > > > > > Best regards,
> > > > > > Alexei Scherbakov
> > > > > >
> > > > >
> > > >
> > >
> >
>
--
Sergey Kozlov
GridGain Systems
www.gridgain.com
;
> [1]
>
> https://apacheignite-tools.readme.io/docs/control-script#section-verification-of-partition-checksums
> [2] https://issues.apache.org/jira/browse/IGNITE-10663
>
> On Thu, Apr 25, 2019 at 7:04 PM Sergey Kozlov
> wrote:
>
> > There's another point to improv
Sergey Kozlov wrote:
> Vyacheskav,
>
> You're right with the referring to MongoDB doc. In general the idea is
> very similar. Many vendors use such approach (1).
>
> [1]
> https://dev.mysql.com/doc/refman/8.0/en/replication-options-master.html#sysvar_rpl_semi_sync_master
oDB. It is used in the same
> way as you described.
>
> On the other hand, if you have such issues it should be investigated
> first: why it causes performance drops: network issues etc.
>
> [1] https://docs.mongodb.com/manual/reference/write-concern/
>
> On Thu, Apr 25, 2019 at 6
async backup partitions only for other
operations (reports, analytics)
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> чт, 25 апр. 2019 г. в 16:55, Sergey Kozlov :
>
> > Igniters
> >
> > I'm working with the wide range of cache configurations and found (from
&
e
IMO it will allow to make more flexible and consistent configurations
--
Sergey Kozlov
GridGain Systems
www.gridgain.com
so have suspend and resume operations.
> > I think we should support them
> >
> > вт, 26 марта 2019 г., 22:07 Sergey Kozlov :
> >
> > > Hi
> > >
> > > Looks like I missed something but why we need OP_TX_CLOSE operation?
> > >
> > &
; > but I
> > > > > did not hear anything about transactions support. Do we have some
> > draft
> > > > for
> > > > > this purpose?
> > > > >
> > > > > As I understand we have several problems:
> > > > >
> > > > >- thread and transaction have hard related (we use thread-local
> > > > variable
> > > > >and thread name)
> > > > >- we can process only one transaction at the same time in one
> > thread
> > > > (it
> > > > >mean we need hold thread per client. If connect 100 thin clients
> > to
> > > 1
> > > > >server node, then need to hold 100 thread on the server side)
> > > > >
> > > > > Let's discuss how we can implement transactions for the thin
> client.
> > > > >
> > > >
> > >
> >
>
--
Sergey Kozlov
GridGain Systems
www.gridgain.com
Sergey Kozlov created IGNITE-11588:
--
Summary: The wrong result for Query
Key: IGNITE-11588
URL: https://issues.apache.org/jira/browse/IGNITE-11588
Project: Ignite
Issue Type: Bug
Sergey Kozlov created IGNITE-11586:
--
Summary: Update platforms/cpp/DEVNOTES.txt
Key: IGNITE-11586
URL: https://issues.apache.org/jira/browse/IGNITE-11586
Project: Ignite
Issue Type: Bug
Sergey Kozlov created IGNITE-11501:
--
Summary: Build examples failed with Scala profile and Java11
Key: IGNITE-11501
URL: https://issues.apache.org/jira/browse/IGNITE-11501
Project: Ignite
Sergey Kozlov created IGNITE-11421:
--
Summary: There's no AI version in ODBC driver available for a
connection
Key: IGNITE-11421
URL: https://issues.apache.org/jira/browse/IGNITE-11421
Project
Sergey Kozlov created IGNITE-11363:
--
Summary: Document replicated cache performance degradation.
Key: IGNITE-11363
URL: https://issues.apache.org/jira/browse/IGNITE-11363
Project: Ignite
Sergey Kozlov created IGNITE-11328:
--
Summary: Ignite binary build is too big
Key: IGNITE-11328
URL: https://issues.apache.org/jira/browse/IGNITE-11328
Project: Ignite
Issue Type: Bug
Sergey Kozlov created IGNITE-11249:
--
Summary: Client failed to putAll/removeAll into mvcc cache during
server node restarts
Key: IGNITE-11249
URL: https://issues.apache.org/jira/browse/IGNITE-11249
Sergey Kozlov created IGNITE-11237:
--
Summary: GetAll may return less data during server node restart
Key: IGNITE-11237
URL: https://issues.apache.org/jira/browse/IGNITE-11237
Project: Ignite
Sergey Kozlov created IGNITE-11218:
--
Summary: COUNT(*) may return wrong value with PDS
Key: IGNITE-11218
URL: https://issues.apache.org/jira/browse/IGNITE-11218
Project: Ignite
Issue Type
Sergey Kozlov created IGNITE-11094:
--
Summary: Add SSL support for ignite zookeeper SPI
Key: IGNITE-11094
URL: https://issues.apache.org/jira/browse/IGNITE-11094
Project: Ignite
Issue Type
th older versions.
> >
> > -
> > Denis
> >
> >
> > On Thu, Jan 24, 2019 at 7:05 AM Sergey Kozlov
> > wrote:
> >
> > > Denis
> > >
> > > I'm not sure that visorcmd can be refactored without incompatible
> changes
> >
ion - instead of creating multiple
> > > scripts for different needs we incorporate all capabilities within
> > > visorcmd? Visor is an app/script that can be updated to meet the
> > > requirements of specific tools.
> > >
> > >
> > > -
>
> >
> > Let's collect comments and improvements and discuss them!
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-11045
> > [2] https://issues.apache.org/jira/browse/IGNITE-11046
> > [3] http://commons.apache.org/proper/commons-cli/
> > [4] https://issues.apache.org/jira/browse/IGNITE-10826
> > [5] https://issues.apache.org/jira/browse/IGNITE-11047
> > --
> > BR, Sergey Antonov
> >
> >
>
> --
> BR, Sergey Antonov
>
>
--
Sergey Kozlov
GridGain Systems
www.gridgain.com
Sergey Kozlov created IGNITE-11048:
--
Summary: Start node with TTL caches causes failure handler activity
Key: IGNITE-11048
URL: https://issues.apache.org/jira/browse/IGNITE-11048
Project: Ignite
Sergey Kozlov created IGNITE-10977:
--
Summary: Document unsupported clean() call for MVCC caches
Key: IGNITE-10977
URL: https://issues.apache.org/jira/browse/IGNITE-10977
Project: Ignite
ename --excludeCaches to --exclude-caches and
> define format for future options. How about linux like format i.e.
> --word1-word2?
>
> --
> BR, Sergey Antonov
>
--
Sergey Kozlov
GridGain Systems
www.gridgain.com
Sergey Kozlov created IGNITE-10892:
--
Summary: Add support JDK 10/11 for ignite.sh(.bat)
Key: IGNITE-10892
URL: https://issues.apache.org/jira/browse/IGNITE-10892
Project: Ignite
Issue Type
s of such
> ERRORs.
> > The error is returned to client but it is also tee'd to log.
> >
> > What we could do:
> > - Move log level from ERROR to WARN or even INFO.
> > - Handle REST user input validation errors differently from Ignite
> internal
> > errors by intr
Sergey Kozlov created IGNITE-10678:
--
Summary: Shell script unification
Key: IGNITE-10678
URL: https://issues.apache.org/jira/browse/IGNITE-10678
Project: Ignite
Issue Type: Improvement
Sergey Kozlov created IGNITE-10631:
--
Summary: examples/sql/world.sql doesn't work for IgniteJdbcDriver
Key: IGNITE-10631
URL: https://issues.apache.org/jira/browse/IGNITE-10631
Project: Ignite
Sergey Kozlov created IGNITE-10630:
--
Summary: Missed descriptions for ML packages
Key: IGNITE-10630
URL: https://issues.apache.org/jira/browse/IGNITE-10630
Project: Ignite
Issue Type: Bug
Sergey Kozlov created IGNITE-10608:
--
Summary: SpringDataExample fails with java.lang.AbstractMethodError
Key: IGNITE-10608
URL: https://issues.apache.org/jira/browse/IGNITE-10608
Project: Ignite
Sergey Kozlov created IGNITE-10521:
--
Summary: Creating table with datetime for PK leads to
j.l.IndexOutOfBoundsException on server node
Key: IGNITE-10521
URL: https://issues.apache.org/jira/browse/IGNITE-10521
Sergey Kozlov created IGNITE-10393:
--
Summary: DataStreamer failed with NPE for MVCC caches
Key: IGNITE-10393
URL: https://issues.apache.org/jira/browse/IGNITE-10393
Project: Ignite
Issue
Sergey Kozlov created IGNITE-10312:
--
Summary: Data streamer fails with CCE:
o.a.i.i.util.future.GridFinishedFuture cannot be cast to
o.a.i.i.p.cache.distributed.dht.GridDhtTopologyFuture
Key: IGNITE-10312
URL
Sergey Kozlov created IGNITE-10222:
--
Summary: CPP Thin: Examples for operations with multiple keys and
values
Key: IGNITE-10222
URL: https://issues.apache.org/jira/browse/IGNITE-10222
Project
Sergey Kozlov created IGNITE-10196:
--
Summary: Remove kafka-clients-*-test dependency
Key: IGNITE-10196
URL: https://issues.apache.org/jira/browse/IGNITE-10196
Project: Ignite
Issue Type
Sergey Kozlov created IGNITE-10136:
--
Summary: NPE in PartitionUpdateCountersMessage
Key: IGNITE-10136
URL: https://issues.apache.org/jira/browse/IGNITE-10136
Project: Ignite
Issue Type: Bug
Sergey Kozlov created IGNITE-10064:
--
Summary: Build examples project failed
Key: IGNITE-10064
URL: https://issues.apache.org/jira/browse/IGNITE-10064
Project: Ignite
Issue Type: Bug
Sergey Kozlov created IGNITE-10056:
--
Summary: Attemp to create MVCC cache with TTL causes full cluster
halt
Key: IGNITE-10056
URL: https://issues.apache.org/jira/browse/IGNITE-10056
Project: Ignite
Sergey Kozlov created IGNITE-10054:
--
Summary: sqlline hangs with concurrent operations
Key: IGNITE-10054
URL: https://issues.apache.org/jira/browse/IGNITE-10054
Project: Ignite
Issue Type
Sergey Kozlov created IGNITE-10052:
--
Summary: Restart node during TX causes vacuum error
Key: IGNITE-10052
URL: https://issues.apache.org/jira/browse/IGNITE-10052
Project: Ignite
Issue Type
Sergey Kozlov created IGNITE-10039:
--
Summary: Small data region may lead IgniteOOM
Key: IGNITE-10039
URL: https://issues.apache.org/jira/browse/IGNITE-10039
Project: Ignite
Issue Type: Bug
Sergey Kozlov created IGNITE-10036:
--
Summary: node_startup_by_ssh.sample.ini move to /config
Key: IGNITE-10036
URL: https://issues.apache.org/jira/browse/IGNITE-10036
Project: Ignite
Issue
Sergey Kozlov created IGNITE-10015:
--
Summary: Sprodic JVM crash due to restart nodes
Key: IGNITE-10015
URL: https://issues.apache.org/jira/browse/IGNITE-10015
Project: Ignite
Issue Type
Sergey Kozlov created IGNITE-10013:
--
Summary: Node restart may lead to NPE in
GridDhtPartitionsExchangeFuture
Key: IGNITE-10013
URL: https://issues.apache.org/jira/browse/IGNITE-10013
Project
Sergey Kozlov created IGNITE-10010:
--
Summary: Node halted if table was dropped
Key: IGNITE-10010
URL: https://issues.apache.org/jira/browse/IGNITE-10010
Project: Ignite
Issue Type: Bug
Sergey Kozlov created IGNITE-10007:
--
Summary: Deactivation hangs if an open transaction exists
Key: IGNITE-10007
URL: https://issues.apache.org/jira/browse/IGNITE-10007
Project: Ignite
Sergey Kozlov created IGNITE-10004:
--
Summary: Parse error leads to leave the transaction
Key: IGNITE-10004
URL: https://issues.apache.org/jira/browse/IGNITE-10004
Project: Ignite
Issue Type
Sergey Kozlov created IGNITE-9971:
-
Summary: MLPTrainer example failures
Key: IGNITE-9971
URL: https://issues.apache.org/jira/browse/IGNITE-9971
Project: Ignite
Issue Type: Bug
Affects
Sergey Kozlov created IGNITE-9918:
-
Summary: Default configuration missed
Key: IGNITE-9918
URL: https://issues.apache.org/jira/browse/IGNITE-9918
Project: Ignite
Issue Type: Bug
Sergey Kozlov created IGNITE-9871:
-
Summary: IgniteOOM on client is not clear
Key: IGNITE-9871
URL: https://issues.apache.org/jira/browse/IGNITE-9871
Project: Ignite
Issue Type: Bug
;
> 1.
> https://www.ibm.com/support/knowledgecenter/en/SSEPGG_10.
> 5.0/com.ibm.db2.luw.admin.dbobj.doc/doc/c0052331.html
> 2. https://github.com/apache/ignite/pull/4295
> 3.
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-
> 20%3A+Data+Compression+in+Ignite
>
> Regards,
>
> --
> Ilya Kasnacheev
>
--
Sergey Kozlov
GridGain Systems
www.gridgain.com
ust convert crc value returned by zip.CRC32 to old format (xor
> it) at runtime.
>
> 2018-08-21 0:12 GMT+03:00 Sergey Kozlov :
>
> > Dmitriy
> >
> > Due to significant improvement and to reduce the number supported
> > modes/options would be good to convert the da
automatically switch to the older implementation.
>
> On Mon, Aug 20, 2018 at 1:58 PM, Sergey Kozlov
> wrote:
>
> > Hi Igniters
> >
> > I suppose that'll break compatibility for LFS (PDS).
> >
> > Do we plan to provide a migration guide w/o data loss for upgrad
> > >> > > > > Evgeniy,
> > > > >> > > > >
> > > > >> > > > > Could you share benchmark code? And please share what
> > version
> > > of
> > > > >> JVM
> > > > >> > > > > you have used.
> > > > >> > > > >
> > > > >> > > > > On Mon, Aug 13, 2018 at 10:44 PM Zhenya
> > > > >> < arzamas...@mail.ru.invalid
> > > > >> >
> > > > >> > > > > wrote:
> > > > >> > > > >
> > > > >> > > > > > I think it would break backward compatibility, as
> Nikolay
> > > > >> mentioned
> > > > >> > > > above
> > > > >> > > > > > we would take exception here:
> > > > >> > > > > >
> > > > >> > > > > > [1]
> > > > >> > > > > >
> > > > >> > > > > > https://github.com/apache/ignite/blob/master/modules/
> > > > >> > > > > core/src/main/java/org/apache/ignite/internal/processors/
> > > > >> > > > > cache/persistence/file/FilePageStore.java#L372
> > > > >> > > > > >
> > > > >> > > > > > thats why i question for community thoughts here.
> > > > >> > > > > >
> > > > >> > > > > > > Hi Evgeniy,
> > > > >> > > > > > >
> > > > >> > > > > > > would you like to submit a patch with CRC32
> > implementation
> > > > >> > change?
> > > > >> > > > > > >
> > > > >> > > > > > > Sincerely,
> > > > >> > > > > > > Dmitriy Pavlov
> > > > >> > > > > > >
> > > > >> > > > > > > пн, 13 авг. 2018 г. в 22:08, Евгений Станиловский
> > > > >> > > > > > > < arzamas...@mail.ru.invalid >:
> > > > >> > > > > > >
> > > > >> > > > > > >> Hi, igniters, i wrote a simple bench, looks like
> > > > >> PureJavaCrc32
> > > > >> > has
> > > > >> > > > > > >> performance problems in compatible with zip.CRC32.
> > > > >> > > > > > >>
> > > > >> > > > > > >> Benchmark Mode Cnt Score Error Units
> > > > >> > > > > > >> BenchmarkCRC.Crc32 avgt 5 1088914.540 ± 368851.822
> > ns/op
> > > > >> > > > > > >> BenchmarkCRC.pureJavaCrc32 avgt 5 6619408.049 ±
> > > 3746712.210
> > > > >> > ns/op
> > > > >> > > > > > >>
> > > > >> > > > > > >> thoughts?
> > > > >> > > > > >
> > > > >> > > > >
> > > > >> > > >
> > > > >> > >
> > > > >> >
> > > >
> > > >
> > > > --
> > > > Евгений Станиловский
> > > >
> > >
> >
>
--
Sergey Kozlov
GridGain Systems
www.gridgain.com
Sergey Kozlov created IGNITE-9291:
-
Summary: IgniteJdbcThinDriver with SSL doesn't work for sqlline on
Windows
Key: IGNITE-9291
URL: https://issues.apache.org/jira/browse/IGNITE-9291
Project: Ignite
gt; > >
> > > It means that if we upgrade to newer H2 version all our users of
> spatial
> > > indexes feature will have compilation and/or linkage errors. This is a
> > > breaking change.
> > >
> > > I propose to implement it still in AI 2.7. We sti
dbcThinConnection.java#L646
> [6] https://github.com/apache/ignite/blob/master/modules/
> core/src/main/java/org/apache/ignite/internal/jdbc2/
> JdbcResultSet.java#L1026
> [7] https://docs.oracle.com/javase/tutorial/jdbc/basics/array.html
--
Sergey Kozlov
GridGain Systems
www.gridgain.com
Sergey Kozlov created IGNITE-9230:
-
Summary: Cannot use array fields in DML oprtations in sqlline
Key: IGNITE-9230
URL: https://issues.apache.org/jira/browse/IGNITE-9230
Project: Ignite
Sergey Kozlov created IGNITE-9173:
-
Summary: Null value for decimal column is shown as the empty
string in sqlline
Key: IGNITE-9173
URL: https://issues.apache.org/jira/browse/IGNITE-9173
Project
Sergey Kozlov created IGNITE-9167:
-
Summary: Wrong output for binary column in SELECT
Key: IGNITE-9167
URL: https://issues.apache.org/jira/browse/IGNITE-9167
Project: Ignite
Issue Type: Bug
Sergey Kozlov created IGNITE-9162:
-
Summary: Query returns ICE: org.h2.table.TableView cannot be cast
Key: IGNITE-9162
URL: https://issues.apache.org/jira/browse/IGNITE-9162
Project: Ignite
t;
> >
> > On 07/26/2018 01:46 AM, Igor Sapego wrote:
> >
> >> Well, at least name should be changed, IMO, as the API function name
> >> should say what we do, and not how we do it. For example, cache_id()
> >> looks better to me than hashcode().
> >>
> >> Best Regards,
> >> Igor
> >>
> >
>
--
Sergey Kozlov
GridGain Systems
www.gridgain.com
> > > don’t support native persistence:
> > > > >
> > > > > https://stackoverflow.com/questions/51511892/how-to-
> > > > configure-persistent-storage-for-apache-ignite-cache
> > > > > Having to ask ourselves “how does it play with LOCAL caches” every
> > time
> > > > we
> > > > > write any code in Ignite seems way to much for the benefits we gain
> > > from
> > > > it.
> > > > >
> > > > > Proposal
> > > > > Let’s deprecate LOCAL caches in 2.x and remove them in 3.0.
> > > > > As a part of deprecation let’s do the following:
> > > > > - Put @Deprecated on the CacheMode.LOCAL
> > > > > - Print a warning every time a LOCAL cache is created
> > > > > - Remove all mentions of LOCAL caches from readme.io, if any,
> except
> > > for
> > > > > the page about cache modes
> > > > > - On the page about cache modes explain that LOCAL is deprecated
> and
> > > can
> > > > > be replaced with a PARTITIONED cache with a node filter
> > > > >
> > > > > Thanks,
> > > > > Stan
> > > > >
> > > >
> > >
> >
>
--
Sergey Kozlov
GridGain Systems
www.gridgain.com
Sergey Kozlov created IGNITE-8918:
-
Summary: Redis examples don't work
Key: IGNITE-8918
URL: https://issues.apache.org/jira/browse/IGNITE-8918
Project: Ignite
Issue Type: Bug
torage
> > > > > and
> > > > > > > have the infinite possibility to scale it, while HDFS is
> bounded
> > by
> > > > > > > Namenode capacity and has big problems with keeping a large
> > number
> > > of
> > > > > > files
> > > > > > > in the system.
> > > > > > >
> > > > > > > We achieved very good experience with persistence when we
> > developed
> > > > our
> > > > > > > durable memory, and we can couple together it and experience
> with
> > > > > > services,
> > > > > > > binary protocol, I/O and start to design a new IEP.
> > > > > > >
> > > > > > > Use cases and features of the project:
> > > > > > > 1) Storing XML, JSON, BLOB, CLOB, images, videos, text, etc
> > without
> > > > > > > overhead and data loss possibility.
> > > > > > > 2) Easy, pluggable, fast and distributed file processing,
> > > > > transformation
> > > > > > > and analysis. (E.g. ImageMagick processor for images
> > > transformation,
> > > > > > > LuceneIndex for texts, whatever, it's bounded only by your
> > > > > imagination).
> > > > > > > 3) Scalability out of the box.
> > > > > > > 4) User-friendly API and minimal steps to start using this
> > storage
> > > in
> > > > > > > production.
> > > > > > >
> > > > > > > I repeated again, this project is not supposed to be a
> high-grade
> > > > > > > distributed file system with full file protocol support.
> > > > > > > This project should primarily focus on target users, which
> would
> > > like
> > > > > to
> > > > > > > use it without complex preparation.
> > > > > > >
> > > > > > > As for example, a user can deploy Ignite with such storage and
> > > > > web-server
> > > > > > > with REST API as Ignite service and get scalable, performant
> > image
> > > > > server
> > > > > > > out of the box which can be accessed using any programming
> > > language.
> > > > > > >
> > > > > > > As a far target goal, we should focus on storing and
> processing a
> > > > very
> > > > > > > large amount of the data like movies, streaming, which is the
> big
> > > > trend
> > > > > > > today.
> > > > > > >
> > > > > > > I would like to say special thanks to our community members
> > Alexey
> > > > > > Stelmak
> > > > > > > and Dmitriy Govorukhin which significantly helped me to put
> > > together
> > > > > all
> > > > > > > pieces of that puzzle.
> > > > > > >
> > > > > > > So, I want to hear your opinions about this proposal.
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
--
Sergey Kozlov
GridGain Systems
www.gridgain.com
Sergey Kozlov created IGNITE-8854:
-
Summary: !indexes and !primarykeys return nothing for
o.a.i.IgniteJdbcDriver
Key: IGNITE-8854
URL: https://issues.apache.org/jira/browse/IGNITE-8854
Project
>>>>> - Fix control.sh and visor-cmd, expose them too.
> >>>>
> >>>> 4. See p.2. Indeed they need to be fixes and exposes 'by the book’.
> >>>>
> >>>>
> >>>>> - Allow specifying of JDK implementation and JDK
Sergey Kozlov created IGNITE-8523:
-
Summary: Java and Scala spark examples are mixed
Key: IGNITE-8523
URL: https://issues.apache.org/jira/browse/IGNITE-8523
Project: Ignite
Issue Type: Bug
Sergey Kozlov created IGNITE-8520:
-
Summary: ignite-gce/ignite-shmem
Key: IGNITE-8520
URL: https://issues.apache.org/jira/browse/IGNITE-8520
Project: Ignite
Issue Type: Bug
Affects
Sergey Kozlov created IGNITE-8514:
-
Summary: Missed descriptions for a few package
Key: IGNITE-8514
URL: https://issues.apache.org/jira/browse/IGNITE-8514
Project: Ignite
Issue Type: Bug
Sergey Kozlov created IGNITE-8337:
-
Summary: Java ThinClient benchmark for yardstick
Key: IGNITE-8337
URL: https://issues.apache.org/jira/browse/IGNITE-8337
Project: Ignite
Issue Type
Sergey Kozlov created IGNITE-8244:
-
Summary: Sporadic ClusterTopologyCheckedException for the example
run
Key: IGNITE-8244
URL: https://issues.apache.org/jira/browse/IGNITE-8244
Project: Ignite
Sergey Kozlov created IGNITE-8217:
-
Summary: Example DbH2ServerStartup produces a huge annoying output
Key: IGNITE-8217
URL: https://issues.apache.org/jira/browse/IGNITE-8217
Project: Ignite
username
> and password. Once the user is authenticated and logged in, you should use
> the session token to perform all other commands. We should NOT be
> authenticating users on every command.
>
> If you follow this approach, then the command for adding a new user should
> require any authentication.
>
> Makes sense?
>
> D.
>
--
Sergey Kozlov
GridGain Systems
www.gridgain.com
ssary in this case.)
>
> Otherwise your suggestions look reasonable. The only thing I'll add, let's
> make it a configuration field and not IGNITE_ define for usability.
>
> Regards,
>
> --
> Ilya Kasnacheev
>
> 2018-04-04 12:55 GMT+03:00 Sergey Kozlov <skoz...@g
ved by other means, like a firewall
> for example. No objections on adding the compute API to thin clients from
> me.
>
--
Sergey Kozlov
GridGain Systems
www.gridgain.com
next release requirements? Vladimir as a 2.4
> > release
> > > manager, could you double check that we are in a good state?
> > >
> >
> > I think we do. We only provide SHA files for our releases.
> >
>
--
Sergey Kozlov
GridGain Systems
www.gridgain.com
please ;)
> > > > >
> > > > > As we see, there is Binary Client Protocol to communicate with
> Ignite
> > > > > cluster and a concept of Thin (lightweight) client.
> > > > >
> > > > > If there are no objections or duplicated plans, we would like to
> > > develop
> > > > > Thin Client libs for:
> > > > > - Node.js
> > > > > - Python
> > > > > - PHP
> > > > >
> > > > > Please add us as contributors and provide access to the Ignite Jira
> > > > > components.
> > > > >
> > > > > Usernames in the Apache Jira:
> > > > > alexey.kosenchuk
> > > > > ekaterina.vergizova
> > > > > pavel.petroshenko
> > > > >
> > > > > Thanks!
> > > > > -Alexey
> > > > >
> > > >
> > >
> >
>
--
Sergey Kozlov
GridGain Systems
www.gridgain.com
t; > > 2. Second, in binary metadata all names stored in upper case. So,
> binary
> > > object converted to JSON will be like: {"ID": 1, "NAME": "Alex",
> > "SALARY":
> > > 300}
> > >
> > > It is OK?
> > >
> > > 3. Should we handle circular references in binary objects? If yes, then
> > > how?
> > >
> > >
> > > [1] https://issues.apache.org/jira/browse/IGNITE-7803
> > >
> > >
> > >
> > > --
> > > Alexey Kuznetsov
> > >
> >
>
--
Sergey Kozlov
GridGain Systems
www.gridgain.com
Hi
Yes, I've a prototype of python client supporting cache operations only.
I plan to share that after official AI 2.4 release providing thin client
implementation.
On Tue, Feb 20, 2018 at 11:40 AM, Pavel Tupitsyn <ptupit...@apache.org>
wrote:
> Hi,
>
> As far as I know, Serg
t; > > > > >> D.
> > > > > > > > >>
> > > > > > > > >> On Fri, Feb 16, 2018 at 8:03 AM, Anton Vinogradov <
> > > > > > > > >> avinogra...@gridgain.com>
> > > > > > > > >> wrote:
> > > > > > > > >>
> > > > > > > > >> Log only mode: flushes application buffers.
> > > > > > > > >>> So, in synced mode without fsync guarantee. That's why I
> > > > propose
> > > > > to
> > > > > > > > >>> rename
> > > > > > > > >>> it as SYNC.
> > > > > > > > >>>
> > > > > > > > >>> On Fri, Feb 16, 2018 at 4:49 PM, Ilya Lantukh <
> > > > > > ilant...@gridgain.com
> > > > > > > >
> > > > > > > > >>> wrote:
> > > > > > > > >>>
> > > > > > > > >>> I am OK with either FSYNC or STRICT variant.
> > > > > > > > >>>>
> > > > > > > > >>>> LOG_ONLY name means "log without fsync".
> > > > > > > > >>>>
> > > > > > > > >>>> On Fri, Feb 16, 2018 at 4:05 PM, Dmitriy Setrakyan <
> > > > > > > > >>>>
> > > > > > > > >>> dsetrak...@apache.org>
> > > > > > > > >>>
> > > > > > > > >>>> wrote:
> > > > > > > > >>>>
> > > > > > > > >>>> On Fri, Feb 16, 2018 at 7:02 AM, Ivan Rakov <
> > > > > > ivan.glu...@gmail.com>
> > > > > > > > >>>>>
> > > > > > > > >>>> wrote:
> > > > > > > > >>>>
> > > > > > > > >>>>> Why create a new term to define something that has
> > already
> > > > been
> > > > > > > > >>>>>>
> > > > > > > > >>>>> defined?
> > > > > > > > >>>>
> > > > > > > > >>>>> That makes sense. I'm ok with FSYNC.
> > > > > > > > >>>>>> Anton, I don't understand why we should rename
> LOG_ONLY
> > to
> > > > > SYNC.
> > > > > > > We
> > > > > > > > >>>>>> started this discussion with bad naming of DEFAULT,
> but
> > > this
> > > > > has
> > > > > > > > >>>>>>
> > > > > > > > >>>>> nothing
> > > > > > > > >>>>
> > > > > > > > >>>>> to
> > > > > > > > >>>>>
> > > > > > > > >>>>>> do with LOG_ONLY (even though it may be scientific -
> but
> > > > SYNC
> > > > > > > sounds
> > > > > > > > >>>>>> scientific as well).
> > > > > > > > >>>>>>
> > > > > > > > >>>>>> I agree with Ivan, we should not go wild with
> renaming.
> > > > > > However, I
> > > > > > > > >>>>>
> > > > > > > > >>>> would
> > > > > > > > >>>
> > > > > > > > >>>> like to find out what is the meaning behind the LOG_ONLY
> > > name.
> > > > > Can
> > > > > > > > >>>>>
> > > > > > > > >>>> someone
> > > > > > > > >>>>
> > > > > > > > >>>>> explain?
> > > > > > > > >>>>>
> > > > > > > > >>>>> D.
> > > > > > > > >>>>>
> > > > > > > > >>>>>
> > > > > > > > >>>>
> > > > > > > > >>>> --
> > > > > > > > >>>> Best regards,
> > > > > > > > >>>> Ilya
> > > > > > > > >>>>
> > > > > > > > >>>>
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
--
Sergey Kozlov
GridGain Systems
www.gridgain.com
> >>>>>>>> +1б вуаштшеудн
> >>>>>>>>
> >>>>>>>> On Tue, Dec 19, 2017 at 2:34 AM, Valentin Kulichenko <
> >>>>>>>> valentin.kuliche...@gmail.com> wrote:
> >>>>>>>>
> >>>>>>>>> +1
> >>>>>>>>>
> >>>>>>>>> On Mon, Dec 18, 2017 at 12:24 PM, Dmitriy Setrakyan <
> >>>>>>>> dsetrak...@apache.org
> >>>>>>>>>>
> >>>>>>>>> wrote:
> >>>>>>>>>
> >>>>>>>>>> +1 (completely agree)
> >>>>>>>>>>
> >>>>>>>>>> On Mon, Dec 18, 2017 at 10:21 AM, Denis Magda <
> dma...@apache.org>
> >>>>>>>> wrote:
> >>>>>>>>>>
> >>>>>>>>>>> Igniters,
> >>>>>>>>>>>
> >>>>>>>>>>> Apache Ignite binary releases still include “fabric” word in
> >> their
> >>>>>>>>> names:
> >>>>>>>>>>> https://ignite.apache.org/download.cgi#binaries <
> >>>>>>>>>>> https://ignite.apache.org/download.cgi#binaries>
> >>>>>>>>>>>
> >>>>>>>>>>> For instance, this is a full name of the previous release -
> >>>>>>>>>>> apache-ignite-fabric-2.3.0-bin.
> >>>>>>>>>>> It’s a little oversight on our side because the project has not
> >> been
> >>>>>>>>>>> positioned as a fabric for a while.
> >>>>>>>>>>>
> >>>>>>>>>>> Proposal! Remove “fabric” from the name and have the binary
> >> releases
> >>>>>>>>>> named
> >>>>>>>>>>> as - apache-ignite-{version}-bin.
> >>>>>>>>>>>
> >>>>>>>>>>> If we’re in consensus then let’s make the change in 2.4.
> >>>>>>>>>>>
> >>>>>>>>>>> —
> >>>>>>>>>>> Denis
> >>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
> >>
>
>
--
Sergey Kozlov
GridGain Systems
www.gridgain.com
Sergey Kozlov created IGNITE-7613:
-
Summary: Unable to run example classes for JDK9 in IDEA
Key: IGNITE-7613
URL: https://issues.apache.org/jira/browse/IGNITE-7613
Project: Ignite
Issue Type
Sergey Kozlov created IGNITE-7599:
-
Summary: Missed licenses in apache-ignite-io module
Key: IGNITE-7599
URL: https://issues.apache.org/jira/browse/IGNITE-7599
Project: Ignite
Issue Type
Sergey Kozlov created IGNITE-7567:
-
Summary: ML example datasets should be moved in resoirce directory
Key: IGNITE-7567
URL: https://issues.apache.org/jira/browse/IGNITE-7567
Project: Ignite
Sergey Kozlov created IGNITE-7534:
-
Summary: ClusterGroupExample duplicate
Key: IGNITE-7534
URL: https://issues.apache.org/jira/browse/IGNITE-7534
Project: Ignite
Issue Type: Bug
Affects
, I guess, much later).
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> Ilya Kasnacheev wrote
> >>>>>>>>>>> * sqlline.sh fails to connect initially, needs to be specified
> >>>>>>>>>>> jdbc:ignite:thin://localhost, then it works. I think that
> sqlline
> >>>>>>>> should
> >>>>>>>>>>> become available as /usr/bin/apache-ignite-sqlline for example,
> >>>> to be
> >>>>>>>> in
> >>>>>>>>>>> $PATH. And figure out how to connect by itself.
> >>>>>>>>>>> * ignitevisorcmd.sh becomes confused. first it scans
> >>>>>>>>>>> /usr/share/apache-ignite for configs, then it fails to write to
> >>>>>>>>>>> /usr/share/apache-ignite/work. We should consider how it can be
> >>>> fixed
> >>>>>>>> (a
> >>>>>>>>>>> symlink from /usr/share/apache-ignite/config to
> >>>> /etc/apache-ignite,
> >>>>>>>>>>> perhaps, and work dir in /tmp?), and made available as
> >>>>>>>>>>> /usr/bin/apache-ignite-visorcmd.
> >>>>>>>>>>
> >>>>>>>>>> The problem exists mainly because of
> sqlline.sh|ignitevisorcmd.sh
> >>>>>>>>>> unaware-of-package design and I see the following 3-step way to
> >>>>>> overcome
> >>>>>>>>>> this limitation.
> >>>>>>>>>> At first we hide this executables file in examples (As Iliya
> >>>>>> proposed).
> >>>>>>>>>> Secondly, I can design a patch, which can be applied during
> package
> >>>>>>>> build,
> >>>>>>>>>> so that those executables work normally form the package
> >>>> installation.
> >>>>>>>>>> And lastly, redesign them to be universal and compatible with
> all
> >>>>>>>> delivery
> >>>>>>>>>> methods.
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> Ilya Kasnacheev wrote
> >>>>>>>>>>> Not everything should go into /usr/share. classpath libs
> belong to
> >>>>>>>>>>> /usr/lib.
> >>>>>>>>>>
> >>>>>>>>>> Moved libs to /usr/lib/apache-ignite and mapped to
> >>>>>>>>>> /usr/share/apache-ignite/libs (for backward compatibility). I
> guess
> >>>>>>>> later
> >>>>>>>>>> we
> >>>>>>>>>> have to think out of a solution to load libs directly from
> /usr/lib
> >>>>>>>> (along
> >>>>>>>>>> with configurations / logs / work / etc.)
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> Ilya Kasnacheev wrote
> >>>>>>>>>>> We are building from binary package and not from sources. If
> it is
> >>>>>>>> used
> >>>>>>>>>> by
> >>>>>>>>>>> internal RPM building this is tolerable, but any distro or
> >>>> repository
> >>>>>>>>>> will
> >>>>>>>>>>> want to build from source.
> >>>>>>>>>>
> >>>>>>>>>> It's not an ordinary task to create "100% honest" package, so I
> >>>> guess
> >>>>>> we
> >>>>>>>>>> definitely won't make to 2.4 release. So I purpose include in
> the
> >>>>>>>> nearest
> >>>>>>>>>> release our package built from binary archive and do not supply
> >>>>>> sources
> >>>>>>>>>> package (as it is currently done in apache.org/dist for
> cassandra
> >>>> /
> >>>>>>>> hadoop
> >>>>>>>>>> or alike). And later design package build procedure, which
> includes
> >>>>>>>> getting
> >>>>>>>>>> sources from sources distribution, or even from Apache Ignite
> Git
> >>>>>>>>>> repository
> >>>>>>>>>> tag.
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> Ilya Kasnacheev wrote
> >>>>>>>>>>> spec contains version (2.4.0) - will be needed to be changed
> for
> >>>>>> every
> >>>>>>>>>>> release. I'm not sure if it's possible to extract.
> >>>>>>>>>>
> >>>>>>>>>> Release procedure on TC is already has some task for project
> >>>> version
> >>>>>>>>>> update,
> >>>>>>>>>> so I guess it is not so difficult to update it accordingly (as
> it
> >>>> is
> >>>>>>>>>> currently done for C++ / .Net internal versions).
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> Ilya Kasnacheev wrote
> >>>>>>>>>>> Package description may be improved. service description lacks
> >>>> '-' in
> >>>>>>>> "In
> >>>>>>>>>>> Memory".
> >>>>>>>>>>
> >>>>>>>>>> Fixed.
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> So the only question to discuss (according Iliya's review) is
> >>>> whether
> >>>>>> to
> >>>>>>>>>> supply package with default-config.xml that has Multicast
> Discovery
> >>>>>>>> turned
> >>>>>>>>>> on or not?
> >>>>>>>>>>
> >>>>>>>>>> Also I'll appreciate any other comments concerning current
> package
> >>>>>>>> design.
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> --
> >>>>>>>>>> Sent from: http://apache-ignite-developers.2346864.n4.nabble.
> com/
> >>>>>>>>>>
> >>>>>>>>
> >>>>>>
> >>>>>>
> >>>>
> >>>>
> >>>
> >
>
--
Sergey Kozlov
GridGain Systems
www.gridgain.com
all non-latin symbols (e.g. using base64), while
> > leaving
> > > the rest as is? With this approach in most cases cache name will remain
> > the
> > > same, and only multibyte characters would be affected.
> > >
> >
> > Agree, if we can keep cache names in human readable form. Would be nice
> to
> > see some examples.
> >
>
--
Sergey Kozlov
GridGain Systems
www.gridgain.com
Sergey Kozlov created IGNITE-7234:
-
Summary: Optimize TC suites
Key: IGNITE-7234
URL: https://issues.apache.org/jira/browse/IGNITE-7234
Project: Ignite
Issue Type: Task
Components
is umbrella
> tickets (one for ML and the other for examples):
> https://issues.apache.org/jira/browse/IGNITE-7203 <
> https://issues.apache.org/jira/browse/IGNITE-7203>
>
> Don’t want this to be missed in the discussion.
>
> —
> Denis
>
> > On Dec 15,
Sergey Kozlov created IGNITE-7216:
-
Summary: Refactor examples project
Key: IGNITE-7216
URL: https://issues.apache.org/jira/browse/IGNITE-7216
Project: Ignite
Issue Type: Sub-task
.
>
> Yet, there is a situation that some classes in *.java.* and .*java8.*
> packages that share the name and policy of merging them is not quite clear.
> Should *.java.* classes be replace by .*java8.*?
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.
Sergey Kozlov created IGNITE-7110:
-
Summary: Javadoc package descriptions missed for ML
Key: IGNITE-7110
URL: https://issues.apache.org/jira/browse/IGNITE-7110
Project: Ignite
Issue Type
column called for instance "nullable")
- UUID type takes 16 bytes length
thanks
On Mon, Nov 27, 2017 at 4:37 PM, Sergey Kozlov <skoz...@gridgain.com> wrote:
> Pavel
>
> Thanks for explanations!
>
> On Mon, Nov 27, 2017 at 2:46 PM, Pavel Tupitsyn <ptupit...@apache.
1 - 100 of 332 matches
Mail list logo
