[jira] [Created] (IGNITE-12215) Data region LRU offheap algo not working causes eventual memory crash
Rick Vincent created IGNITE-12215: - Summary: Data region LRU offheap algo not working causes eventual memory crash Key: IGNITE-12215 URL: https://issues.apache.org/jira/browse/IGNITE-12215 Project: Ignite Issue Type: Bug Components: cache Affects Versions: 2.7.5 Reporter: Rick Vincent Attachments: Ignite-dataregion.png, Ignite.log Please see the below for further details: [http://apache-ignite-users.70518.x6.nabble.com/Data-region-LRU-offheap-algo-not-working-td29280.html] Essentially LRU algo is not working for offheap data region where persistence is disabled. To reproduce, simply limit the data region size and inject data from clients at a fairly rapid pace until the oom message appears. [^Ignite.log]!Ignite-dataregion.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12214) Continuous query system view
[ https://issues.apache.org/jira/browse/IGNITE-12214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-12214: - Summary: Continuous query system view (was: Contionuous query system view) > Continuous query system view > > > Key: IGNITE-12214 > URL: https://issues.apache.org/jira/browse/IGNITE-12214 > Project: Ignite > Issue Type: Sub-task >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Labels: IEP-35 > > IGNITE-12145 finished > We should add continuous query system views. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-9410) Add transactions support to thin clients
[ https://issues.apache.org/jira/browse/IGNITE-9410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16935612#comment-16935612 ] Aleksey Plekhanov commented on IGNITE-9410: --- [~ptupitsyn], [~Pavlukhin], [~isapego], [~agoncharuk] thanks for review! Merged to master. > Add transactions support to thin clients > > > Key: IGNITE-9410 > URL: https://issues.apache.org/jira/browse/IGNITE-9410 > Project: Ignite > Issue Type: Task > Components: mvcc, thin client >Reporter: Vladimir Ozerov >Assignee: Aleksey Plekhanov >Priority: Major > Labels: iep-34 > Fix For: 2.8 > > Time Spent: 3h 20m > Remaining Estimate: 0h > > Currently only ODBC and JDBC drivers support transactions and in not very > efficient way. We need to add transactional API to .NET, Java, CPP, NodeJS > and Python clients. > Key pieces: > # Add API to relevant clients > # Review listener logic - currently we create separate threads. But is it > really needed? > ## If there is an implicit operation and no ongoing transaction, then > operation might be executed right away > ## If cache operations are decoupled from threads, then we can resort to > reactive approach, when multiple transactions could be executed from the same > thread -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12209) Transaction system view
[ https://issues.apache.org/jira/browse/IGNITE-12209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16935614#comment-16935614 ] Nikolay Izhikov commented on IGNITE-12209: -- Hello. [~ascherbakov] [~alex_pl] Can you take a look at this patch? It's add transactions system view to the product. > Transaction system view > --- > > Key: IGNITE-12209 > URL: https://issues.apache.org/jira/browse/IGNITE-12209 > Project: Ignite > Issue Type: Sub-task >Affects Versions: 2.7.6 >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Labels: IEP-35 > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > IGNITE-12145 finished > We should add transactions to the system views. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-11868) GridClient#data() should be deprecated/removed.
[
https://issues.apache.org/jira/browse/IGNITE-11868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16935670#comment-16935670
]
Vyacheslav Koptilin commented on IGNITE-11868:
--
Hi [~kcheng.mvp],
In general, the change looks good to me. I triggered 'RunAll' for this pull
request and got a visa from the Teamcity bot.
(I think the following page will be useful to understand how it works:
[https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+Teamcity+Bot])
Could you please change the state of the ticket from "In progress" to "Patch
available"
Also, take into account my comment
[https://github.com/apache/ignite/pull/6894#discussion_r327007694]
Thank you!
> GridClient#data() should be deprecated/removed.
> ---
>
> Key: IGNITE-11868
> URL: https://issues.apache.org/jira/browse/IGNITE-11868
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7
>Reporter: Vyacheslav Koptilin
>Assignee: kcheng.mvp
>Priority: Minor
> Labels: newbie
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> It seems that {{GridClient#data()}} does not make sense after IGNITE-3488 and
> therefore it can be removed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-11868) GridClient#data() should be deprecated/removed.
[
https://issues.apache.org/jira/browse/IGNITE-11868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16935671#comment-16935671
]
Ignite TC Bot commented on IGNITE-11868:
{panel:title=Branch: [pull/6894/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4624628&buildTypeId=IgniteTests24Java8_RunAll]
> GridClient#data() should be deprecated/removed.
> ---
>
> Key: IGNITE-11868
> URL: https://issues.apache.org/jira/browse/IGNITE-11868
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7
>Reporter: Vyacheslav Koptilin
>Assignee: kcheng.mvp
>Priority: Minor
> Labels: newbie
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> It seems that {{GridClient#data()}} does not make sense after IGNITE-3488 and
> therefore it can be removed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12216) [ML][Umbrella]Advanced support of categorical features
[ https://issues.apache.org/jira/browse/IGNITE-12216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Zinoviev updated IGNITE-12216: -- Summary: [ML][Umbrella]Advanced support of categorical features (was: [ML][Umbrella]) > [ML][Umbrella]Advanced support of categorical features > -- > > Key: IGNITE-12216 > URL: https://issues.apache.org/jira/browse/IGNITE-12216 > Project: Ignite > Issue Type: New Feature > Components: ml >Affects Versions: 2.8 >Reporter: Aleksey Zinoviev >Assignee: Aleksey Zinoviev >Priority: Minor > Fix For: 2.8 > > > Discussion here > [http://apache-ignite-developers.2346864.n4.nabble.com/ML-DISCUSSION-Big-Double-problem-td42262.html#a42267] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12216) [ML][Umbrella]
Aleksey Zinoviev created IGNITE-12216: - Summary: [ML][Umbrella] Key: IGNITE-12216 URL: https://issues.apache.org/jira/browse/IGNITE-12216 Project: Ignite Issue Type: New Feature Components: ml Affects Versions: 2.8 Reporter: Aleksey Zinoviev Assignee: Aleksey Zinoviev Fix For: 2.8 Discussion here [http://apache-ignite-developers.2346864.n4.nabble.com/ML-DISCUSSION-Big-Double-problem-td42262.html#a42267] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12217) [ML] Add support for label encoding
Aleksey Zinoviev created IGNITE-12217: - Summary: [ML] Add support for label encoding Key: IGNITE-12217 URL: https://issues.apache.org/jira/browse/IGNITE-12217 Project: Ignite Issue Type: Sub-task Affects Versions: 2.8 Reporter: Aleksey Zinoviev Assignee: Aleksey Zinoviev Fix For: 2.8 Support handling of training on Mushroom dataset See part of the discussion: "My dataset is Mushrooms <[https://www.kaggle.com/uciml/mushroom-classification]> dataset from Kaggle. There are only categorial features and categorical labels." -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12218) [ML] Add support for Strings in Vectorizer
Aleksey Zinoviev created IGNITE-12218: - Summary: [ML] Add support for Strings in Vectorizer Key: IGNITE-12218 URL: https://issues.apache.org/jira/browse/IGNITE-12218 Project: Ignite Issue Type: Sub-task Affects Versions: 2.8 Reporter: Aleksey Zinoviev Assignee: Aleksey Zinoviev Fix For: 2.8 Currently the signatures of vectorizers are limited, should extend for Strings support -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12032) Server node prints exception when ODBC driver disconnects
[
https://issues.apache.org/jira/browse/IGNITE-12032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16935727#comment-16935727
]
Ignite TC Bot commented on IGNITE-12032:
{panel:title=Branch: [pull/6897/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4626227&buildTypeId=IgniteTests24Java8_RunAll]
> Server node prints exception when ODBC driver disconnects
> -
>
> Key: IGNITE-12032
> URL: https://issues.apache.org/jira/browse/IGNITE-12032
> Project: Ignite
> Issue Type: Bug
> Components: thin client
>Affects Versions: 2.7.5
>Reporter: Evgenii Zhuravlev
>Assignee: Lev Agafonov
>Priority: Minor
> Labels: newbie, usability
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Whenever a process using ODBC clients is finished, it's printing in the
> node logs this exception:
> {code:java}
> *[07:45:19,559][SEVERE][grid-nio-worker-client-listener-1-#30][ClientListenerProcessor]
>
> Failed to process selector key [s
> es=GridSelectorNioSessionImpl [worker=ByteBufferNioClientWorker
> [readBuf=java.nio.HeapByteBuffer[pos=0 lim=8192 cap=8192
> ], super=AbstractNioClientWorker [idx=1, bytesRcvd=0, bytesSent=0,
> bytesRcvd0=0, bytesSent0=0, select=true, super=GridWo
> rker [name=grid-nio-worker-client-listener-1, igniteInstanceName=null,
> finished=false, heartbeatTs=1564289118230, hashCo
> de=1829856117, interrupted=false,
> runner=grid-nio-worker-client-listener-1-#30]]], writeBuf=null,
> readBuf=null, inRecove
> ry=null, outRecovery=null, super=GridNioSessionImpl
> [locAddr=/0:0:0:0:0:0:0:1:10800, rmtAddr=/0:0:0:0:0:0:0:1:63697, cre
> ateTime=1564289116225, closeTime=0, bytesSent=1346, bytesRcvd=588,
> bytesSent0=0, bytesRcvd0=0, sndSchedTime=156428911623
> 5, lastSndTime=1564289116235, lastRcvTime=1564289116235, readsPaused=false,
> filterChain=FilterChain[filters=[GridNioAsyn
> cNotifyFilter, GridNioCodecFilter [parser=ClientListenerBufferedParser,
> directMode=false]], accepted=true, markedForClos
> e=false]]]
> java.io.IOException: An existing connection was forcibly closed by the
> remote host
> at sun.nio.ch.SocketDispatcher.read0(Native Method)
> at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:43)
> at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223)
> at sun.nio.ch.IOUtil.read(IOUtil.java:197)
> at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$ByteBufferNioClientWorker.processRead(GridNioServer.java:11
>
> 04)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNi
>
> oServer.java:2389)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:215
>
> 6)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1797)
>
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.java:748)*
> {code}
> It's absolutely normal behavior when ODBC client disconnects from the node,
> so, we shouldn't print exception in the log. We should replace it with
> something like INFO message about ODBC client disconnection.
> Thread from user list:
> http://apache-ignite-users.70518.x6.nabble.com/exceptions-in-Ignite-node-when-a-thin-client-process-ends-td28970.html
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12211) Client connections system view
[ https://issues.apache.org/jira/browse/IGNITE-12211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16935742#comment-16935742 ] Nikolay Izhikov commented on IGNITE-12211: -- [~alex_pl] Can you take a look at my patch? > Client connections system view > -- > > Key: IGNITE-12211 > URL: https://issues.apache.org/jira/browse/IGNITE-12211 > Project: Ignite > Issue Type: Sub-task >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Labels: IEP-35 > Time Spent: 10m > Remaining Estimate: 0h > > IGNITE-12145 finished > We should add client connections to the system views. > System view should track JDBC, ODBC and thin connections. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12219) Cache operations histogram
Nikolay Izhikov created IGNITE-12219: Summary: Cache operations histogram Key: IGNITE-12219 URL: https://issues.apache.org/jira/browse/IGNITE-12219 Project: Ignite Issue Type: Improvement Reporter: Nikolay Izhikov We need to provide cache operations histogram metrics Next API and its variants should be covered: * get * getEntry * getAll * put * remove * replace * lock * invoke * containsKey -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12219) Cache operations histogram
[ https://issues.apache.org/jira/browse/IGNITE-12219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-12219: - Priority: Major (was: Minor) > Cache operations histogram > -- > > Key: IGNITE-12219 > URL: https://issues.apache.org/jira/browse/IGNITE-12219 > Project: Ignite > Issue Type: Improvement >Reporter: Nikolay Izhikov >Priority: Major > Labels: IEP-35 > > We need to provide cache operations histogram metrics > Next API and its variants should be covered: > * get > * getEntry > * getAll > * put > * remove > * replace > * lock > * invoke > * containsKey -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12199) WAL record with data entries doesn't flushes on backups for transactional cache
[
https://issues.apache.org/jira/browse/IGNITE-12199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Gura updated IGNITE-12199:
-
Ignite Flags: Release Notes Required (was: Docs Required,Release Notes
Required)
> WAL record with data entries doesn't flushes on backups for transactional
> cache
> ---
>
> Key: IGNITE-12199
> URL: https://issues.apache.org/jira/browse/IGNITE-12199
> Project: Ignite
> Issue Type: Improvement
>Reporter: Andrey Gura
>Assignee: Andrey Gura
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> WAL record with data entries doesn't flushes on backups for transactional
> cache.
> This issue can be reproduced for example by
> {{TxPartitionCounterStateConsistencyTest.testSingleThreadedUpdateOrder}} test
> with disabled MMAP mode.
> Problem place in code is {{GridDistributedTxRemoteAdapter#commitIfLocked}}
> where {{wal.log()}} doesn't assign returned file pointer to the {{ptr}}
> variable.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-11723) IgniteSpark integration should support skipStore option for internal dataStreamer (IgniteRdd and Ignite DataFrame)
[ https://issues.apache.org/jira/browse/IGNITE-11723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Zinoviev updated IGNITE-11723: -- Priority: Critical (was: Major) > IgniteSpark integration should support skipStore option for internal > dataStreamer (IgniteRdd and Ignite DataFrame) > -- > > Key: IGNITE-11723 > URL: https://issues.apache.org/jira/browse/IGNITE-11723 > Project: Ignite > Issue Type: Improvement > Components: spark >Affects Versions: 2.7 >Reporter: Andrey Aleksandrov >Assignee: Aleksey Zinoviev >Priority: Critical > Fix For: 2.8 > > > At the moment this option can't be set. But this integrations could be used > for initial data loading also for the caches with cache stores > implementation. > With skipStore option, we could avoid write-through behavior during this > initial data loading. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12203) Rebalance is loading partitions already loading after cancellation without WAL
[
https://issues.apache.org/jira/browse/IGNITE-12203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16935912#comment-16935912
]
Ignite TC Bot commented on IGNITE-12203:
{panel:title=Branch: [pull/6892/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4618218&buildTypeId=IgniteTests24Java8_RunAll]
> Rebalance is loading partitions already loading after cancellation without WAL
> --
>
> Key: IGNITE-12203
> URL: https://issues.apache.org/jira/browse/IGNITE-12203
> Project: Ignite
> Issue Type: Bug
>Reporter: Vladislav Pyatkov
>Assignee: Vladislav Pyatkov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I have seen from log partition miss warnings and after that rebelance was
> canceled and was forcibly restarted but already over another suppliers. In
> case when added nodes without a storage in persistent cluster it can lead to
> several times fully rebalance. It seem to bee because we have not updated
> partitions state until rebalance finished.
> Should to prevent partition eviction until rebalance on all nodes completed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-8296) Move Spark Scala DataFrames code examples to correct directory and prefix with "Scalar" to follow convention used with other Scala examples
[ https://issues.apache.org/jira/browse/IGNITE-8296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Zinoviev updated IGNITE-8296: - Description: # The Spark Scala DataFrames code examples are in the wrong directory. They should be moved to the correct directory structure. # The Spark Scala DataFrames code examples should follow the naming convention used for other Scala code examples and be prefixed with "Scalar". or move SparkScalar example and its logic to the appropriate folder in spark folder was: # The Spark Scala DataFrames code examples are in the wrong directory. They should be moved to the correct directory structure. # The Spark Scala DataFrames code examples should follow the naming convention used for other Scala code examples and be prefixed with "Scalar". > Move Spark Scala DataFrames code examples to correct directory and prefix > with "Scalar" to follow convention used with other Scala examples > > > Key: IGNITE-8296 > URL: https://issues.apache.org/jira/browse/IGNITE-8296 > Project: Ignite > Issue Type: Improvement > Components: spark >Affects Versions: 2.4 >Reporter: Akmal Chaudhri >Assignee: Aleksey Zinoviev >Priority: Minor > > # The Spark Scala DataFrames code examples are in the wrong directory. They > should be moved to the correct directory structure. > # The Spark Scala DataFrames code examples should follow the naming > convention used for other Scala code examples and be prefixed with "Scalar". > or move SparkScalar example and its logic to the appropriate folder in spark > folder -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-11008) JDBC Metadata: redundant spaces IS_GENERATEDCOLUMN & BUFFER_LENGTH
[ https://issues.apache.org/jira/browse/IGNITE-11008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16936016#comment-16936016 ] Maxim Muzafarov commented on IGNITE-11008: -- [~kcheng.mvp], Can you check the PR with TC.Bot visa? https://mtcga.gridgain.com/ If you think that the issue is ready for a review, can you set it to the `Patch Available` status? > JDBC Metadata: redundant spaces IS_GENERATEDCOLUMN & BUFFER_LENGTH > -- > > Key: IGNITE-11008 > URL: https://issues.apache.org/jira/browse/IGNITE-11008 > Project: Ignite > Issue Type: Bug > Components: jdbc >Affects Versions: 2.7 >Reporter: Stepan Pilschikov >Assignee: kcheng.mvp >Priority: Minor > Fix For: 2.8 > > > Found redundant spaces in > org.apache.ignite.internal.jdbc.thin.JdbcThinDatabaseMetadata#getColumns > "IS_GENERATEDCOLUMN " > "BUFFER_LENGTH " -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12220) Allow to use cache-related permissions both at system and per-cache levels
Andrey Kuznetsov created IGNITE-12220:
-
Summary: Allow to use cache-related permissions both at system and
per-cache levels
Key: IGNITE-12220
URL: https://issues.apache.org/jira/browse/IGNITE-12220
Project: Ignite
Issue Type: Task
Components: security
Affects Versions: 2.7.6
Reporter: Andrey Kuznetsov
Assignee: Andrey Kuznetsov
Fix For: 2.8
Currently, {{CACHE_CREATE}} and {{CACHE_DESTROY}} permissions are enforced to
be system-level permissions, see for instance
{{SecurityPermissionSetBuilder#appendCachePermissions}}. This looks inflexible:
Ignite Security implementations are not able to manage cache creation and
deletion permissions on per-cache basis (unlike get/put/remove permissions).
All such limitations should be found and removed on order to allow all
{{CACHE_*}} permissions to be set both at system and per-cache levels.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-12220) Allow to use cache-related permissions both at system and per-cache levels
[
https://issues.apache.org/jira/browse/IGNITE-12220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Kuznetsov reassigned IGNITE-12220:
-
Assignee: (was: Andrey Kuznetsov)
> Allow to use cache-related permissions both at system and per-cache levels
> --
>
> Key: IGNITE-12220
> URL: https://issues.apache.org/jira/browse/IGNITE-12220
> Project: Ignite
> Issue Type: Task
> Components: security
>Affects Versions: 2.7.6
>Reporter: Andrey Kuznetsov
>Priority: Major
> Fix For: 2.8
>
>
> Currently, {{CACHE_CREATE}} and {{CACHE_DESTROY}} permissions are enforced to
> be system-level permissions, see for instance
> {{SecurityPermissionSetBuilder#appendCachePermissions}}. This looks
> inflexible: Ignite Security implementations are not able to manage cache
> creation and deletion permissions on per-cache basis (unlike get/put/remove
> permissions). All such limitations should be found and removed on order to
> allow all {{CACHE_*}} permissions to be set both at system and per-cache
> levels.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12221) Javadoc generation fail
Nikolay Izhikov created IGNITE-12221:
Summary: Javadoc generation fail
Key: IGNITE-12221
URL: https://issues.apache.org/jira/browse/IGNITE-12221
Project: Ignite
Issue Type: Sub-task
Reporter: Nikolay Izhikov
javadoc generation command fails
{{code}}
System view SPI
org.apache.ignite.spi.systemview*
{{code}}
should be added to the parent pom.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-12221) Javadoc generation fail
[
https://issues.apache.org/jira/browse/IGNITE-12221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolay Izhikov reassigned IGNITE-12221:
Assignee: Nikolay Izhikov
> Javadoc generation fail
> ---
>
> Key: IGNITE-12221
> URL: https://issues.apache.org/jira/browse/IGNITE-12221
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Major
>
> javadoc generation command fails
> {{code}}
>
> System view SPI
>
> org.apache.ignite.spi.systemview*
>
> {{code}}
> should be added to the parent pom.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (IGNITE-12221) Javadoc generation fail
[
https://issues.apache.org/jira/browse/IGNITE-12221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolay Izhikov resolved IGNITE-12221.
--
Resolution: Fixed
Fixed.
> Javadoc generation fail
> ---
>
> Key: IGNITE-12221
> URL: https://issues.apache.org/jira/browse/IGNITE-12221
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Major
>
> javadoc generation command fails
> {{code}}
>
> System view SPI
>
> org.apache.ignite.spi.systemview*
>
> {{code}}
> should be added to the parent pom.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12221) Javadoc generation fail
[
https://issues.apache.org/jira/browse/IGNITE-12221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolay Izhikov updated IGNITE-12221:
-
Description:
javadoc generation command fails
{code}
System view SPI
org.apache.ignite.spi.systemview*
{code}
should be added to the parent pom.
was:
javadoc generation command fails
{{code}}
System view SPI
org.apache.ignite.spi.systemview*
{{code}}
should be added to the parent pom.
> Javadoc generation fail
> ---
>
> Key: IGNITE-12221
> URL: https://issues.apache.org/jira/browse/IGNITE-12221
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Major
>
> javadoc generation command fails
> {code}
>
> System view SPI
>
> org.apache.ignite.spi.systemview*
>
> {code}
> should be added to the parent pom.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-12220) Allow to use cache-related permissions both at system and per-cache levels
[
https://issues.apache.org/jira/browse/IGNITE-12220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergei Ryzhov reassigned IGNITE-12220:
--
Assignee: Sergei Ryzhov
> Allow to use cache-related permissions both at system and per-cache levels
> --
>
> Key: IGNITE-12220
> URL: https://issues.apache.org/jira/browse/IGNITE-12220
> Project: Ignite
> Issue Type: Task
> Components: security
>Affects Versions: 2.7.6
>Reporter: Andrey Kuznetsov
>Assignee: Sergei Ryzhov
>Priority: Major
> Fix For: 2.8
>
>
> Currently, {{CACHE_CREATE}} and {{CACHE_DESTROY}} permissions are enforced to
> be system-level permissions, see for instance
> {{SecurityPermissionSetBuilder#appendCachePermissions}}. This looks
> inflexible: Ignite Security implementations are not able to manage cache
> creation and deletion permissions on per-cache basis (unlike get/put/remove
> permissions). All such limitations should be found and removed on order to
> allow all {{CACHE_*}} permissions to be set both at system and per-cache
> levels.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Reopened] (IGNITE-11008) JDBC Metadata: redundant spaces IS_GENERATEDCOLUMN & BUFFER_LENGTH
[ https://issues.apache.org/jira/browse/IGNITE-11008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kcheng.mvp reopened IGNITE-11008: - > JDBC Metadata: redundant spaces IS_GENERATEDCOLUMN & BUFFER_LENGTH > -- > > Key: IGNITE-11008 > URL: https://issues.apache.org/jira/browse/IGNITE-11008 > Project: Ignite > Issue Type: Bug > Components: jdbc >Affects Versions: 2.7 >Reporter: Stepan Pilschikov >Assignee: kcheng.mvp >Priority: Minor > Fix For: 2.8 > > > Found redundant spaces in > org.apache.ignite.internal.jdbc.thin.JdbcThinDatabaseMetadata#getColumns > "IS_GENERATEDCOLUMN " > "BUFFER_LENGTH " -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-11008) JDBC Metadata: redundant spaces IS_GENERATEDCOLUMN & BUFFER_LENGTH
[ https://issues.apache.org/jira/browse/IGNITE-11008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kcheng.mvp resolved IGNITE-11008. - Resolution: Fixed > JDBC Metadata: redundant spaces IS_GENERATEDCOLUMN & BUFFER_LENGTH > -- > > Key: IGNITE-11008 > URL: https://issues.apache.org/jira/browse/IGNITE-11008 > Project: Ignite > Issue Type: Bug > Components: jdbc >Affects Versions: 2.7 >Reporter: Stepan Pilschikov >Assignee: kcheng.mvp >Priority: Minor > Fix For: 2.8 > > > Found redundant spaces in > org.apache.ignite.internal.jdbc.thin.JdbcThinDatabaseMetadata#getColumns > "IS_GENERATEDCOLUMN " > "BUFFER_LENGTH " -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-11008) JDBC Metadata: redundant spaces IS_GENERATEDCOLUMN & BUFFER_LENGTH
[ https://issues.apache.org/jira/browse/IGNITE-11008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16936313#comment-16936313 ] kcheng.mvp commented on IGNITE-11008: - [~spilschikov] Seems that I dont have privilege to change *Status* > JDBC Metadata: redundant spaces IS_GENERATEDCOLUMN & BUFFER_LENGTH > -- > > Key: IGNITE-11008 > URL: https://issues.apache.org/jira/browse/IGNITE-11008 > Project: Ignite > Issue Type: Bug > Components: jdbc >Affects Versions: 2.7 >Reporter: Stepan Pilschikov >Assignee: kcheng.mvp >Priority: Minor > Fix For: 2.8 > > > Found redundant spaces in > org.apache.ignite.internal.jdbc.thin.JdbcThinDatabaseMetadata#getColumns > "IS_GENERATEDCOLUMN " > "BUFFER_LENGTH " -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12222) Lacking Ignite C++ functionality or examples to store byte arrays
Jesus H created IGNITE-1: Summary: Lacking Ignite C++ functionality or examples to store byte arrays Key: IGNITE-1 URL: https://issues.apache.org/jira/browse/IGNITE-1 Project: Ignite Issue Type: Improvement Environment: Ignite 2.7.5 Reporter: Jesus H Ignite C++ lacks sufficient information or functionality to store byte buffers as values. >From the doc, I understand users can specialize BInaryType template to add >functionality to an existing byte buffer class, but I believe that being able >to store a byte buffer should be something basic that should be part of Ignite. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12222) Lacking Ignite C++ functionality or examples to store byte arrays
[ https://issues.apache.org/jira/browse/IGNITE-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesus H updated IGNITE-1: - Description: I'd like to use Ignite as an in memory database that uses a std::string as a key, and a byte buffer as a value (could be char*, std::vector, std::vector or something more appropriate). Ignite C++ lacks sufficient information or functionality to store byte buffers as values. >From the doc, I understand users can specialize BinaryType template to add >functionality to an existing byte buffer class, but I believe that being able >to store a byte buffer should be something basic that should be part of Ignite. was: Ignite C++ lacks sufficient information or functionality to store byte buffers as values. >From the doc, I understand users can specialize BInaryType template to add >functionality to an existing byte buffer class, but I believe that being able >to store a byte buffer should be something basic that should be part of Ignite. > Lacking Ignite C++ functionality or examples to store byte arrays > - > > Key: IGNITE-1 > URL: https://issues.apache.org/jira/browse/IGNITE-1 > Project: Ignite > Issue Type: Improvement > Environment: Ignite 2.7.5 >Reporter: Jesus H >Priority: Major > > I'd like to use Ignite as an in memory database that uses a std::string as a > key, and a byte buffer as a value (could be char*, std::vector, > std::vector or something more appropriate). > Ignite C++ lacks sufficient information or functionality to store byte > buffers as values. > From the doc, I understand users can specialize BinaryType template to add > functionality to an existing byte buffer class, but I believe that being able > to store a byte buffer should be something basic that should be part of > Ignite. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-11312) JDBC: Thin driver doesn't reports incorrect property names
[ https://issues.apache.org/jira/browse/IGNITE-11312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16936453#comment-16936453 ] Lev Agafonov commented on IGNITE-11312: --- Hello, Igniters! I investigated the issue and prepared PR. Could you please assign this ticket on me? > JDBC: Thin driver doesn't reports incorrect property names > -- > > Key: IGNITE-11312 > URL: https://issues.apache.org/jira/browse/IGNITE-11312 > Project: Ignite > Issue Type: Improvement > Components: jdbc >Reporter: Stanislav Lukyanov >Assignee: Suraj Singh >Priority: Major > Labels: newbie > Time Spent: 10m > Remaining Estimate: 0h > > JDBC driver reports the properties it supports via getPropertyInfo method. It > currently reports the property names as simple strings, like > "enforceJoinOrder". However, when the properties are processed on connect > they are looked up with prefix "ignite.jdbc", e.g. > "ignite.jdbc.enforceJoinOrder". > Because of this UI tools like DBeaver can't properly pass the properties to > Ignite. For example, when "enforceJoinOrder" is set to true in "Connection > settings" -> "Driver properties" menu of DBeaver it has no effect. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-11312) JDBC: Thin driver doesn't reports incorrect property names
[ https://issues.apache.org/jira/browse/IGNITE-11312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lev Agafonov updated IGNITE-11312: -- Fix Version/s: 2.8 > JDBC: Thin driver doesn't reports incorrect property names > -- > > Key: IGNITE-11312 > URL: https://issues.apache.org/jira/browse/IGNITE-11312 > Project: Ignite > Issue Type: Improvement > Components: jdbc >Reporter: Stanislav Lukyanov >Assignee: Suraj Singh >Priority: Major > Labels: newbie > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > JDBC driver reports the properties it supports via getPropertyInfo method. It > currently reports the property names as simple strings, like > "enforceJoinOrder". However, when the properties are processed on connect > they are looked up with prefix "ignite.jdbc", e.g. > "ignite.jdbc.enforceJoinOrder". > Because of this UI tools like DBeaver can't properly pass the properties to > Ignite. For example, when "enforceJoinOrder" is set to true in "Connection > settings" -> "Driver properties" menu of DBeaver it has no effect. -- This message was sent by Atlassian Jira (v8.3.4#803005)
