Test
push eventorientechnologies/orientdb
commit sha 951b63ac85c5726e954f272ead5d3367c127d08a
Update views management
push time in 2 days
push eventorientechnologies/orientdb
commit sha 9137fe65be85f2776799ebed93262e9d97f64a36
Update views management
push time in 2 days
push eventorientechnologies/orientdb
commit sha e9043530db106097f46fc31b3e4b1de64e91d25e
Implement DROP CLASS with parameter Resolves #9627
push time in 2 days
issue closedorientechnologies/orientdb
ODatabaseSession().command(String query, Object... args) unsupport for DROP?
OrientDB Version: 3.2.0
Java Version: 8
maven dependency: orientdb-client 3.2.0
i want to drop class named "zzz"
can work:
ODatabaseSession session = pool.acquire();
OResultSet rs = session.command("drop class zzz");
rs.close();
not work:
ODatabaseSession session = pool.acquire();
OResultSet rs = session.command("drop class ?" ,"zzz");
rs.close();
is it unsupported ?
Exception in thread "main" com.orientechnologies.orient.core.sql.OCommandSQLParsingException: Error parsing query:
drop class ?
^
Encountered " <DROP> "drop "" at line 1, column 1.
Was expecting one of:
<SELECT> ...
<TRAVERSE> ...
<MATCH> ...
<INSERT> ...
<RETURN> ...
<FIND> ...
<REBUILD> ...
<OPTIMIZE> ...
<GRANT> ...
<REVOKE> ...
<BEGIN> ...
<COMMIT> ...
<ROLLBACK> ...
<IF> ...
<SLEEP> ...
<CONSOLE> ...
<MOVE> ...
<SELECT> ...
<SELECT> ...
<TRAVERSE> ...
<MATCH> ...
<FIND> ...
<INSERT> ...
<MOVE> ...
DB name="cmdb"
Error Code="1"
DB name="cmdb"
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:78)
at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:499)
at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:480)
at com.orientechnologies.orient.client.binary.OChannelBinaryAsynchClient.handleException(OChannelBinaryAsynchClient.java:355)
at com.orientechnologies.orient.client.binary.OChannelBinaryAsynchClient.handleStatus(OChannelBinaryAsynchClient.java:303)
at com.orientechnologies.orient.client.binary.OChannelBinaryAsynchClient.handleStatus(OChannelBinaryAsynchClient.java:325)
at com.orientechnologies.orient.client.binary.OChannelBinaryAsynchClient.beginResponse(OChannelBinaryAsynchClient.java:209)
at com.orientechnologies.orient.client.binary.OChannelBinaryAsynchClient.beginResponse(OChannelBinaryAsynchClient.java:167)
at com.orientechnologies.orient.client.remote.OStorageRemote.beginResponse(OStorageRemote.java:2006)
at com.orientechnologies.orient.client.remote.OStorageRemote.lambda$networkOperationRetryTimeout$2(OStorageRemote.java:390)
at com.orientechnologies.orient.client.remote.OStorageRemote.baseNetworkOperation(OStorageRemote.java:455)
at com.orientechnologies.orient.client.remote.OStorageRemote.networkOperationRetryTimeout(OStorageRemote.java:370)
at com.orientechnologies.orient.client.remote.OStorageRemote.networkOperation(OStorageRemote.java:410)
at com.orientechnologies.orient.client.remote.OStorageRemote.query(OStorageRemote.java:1098)
at com.orientechnologies.orient.core.db.document.ODatabaseDocumentRemote.query(ODatabaseDocumentRemote.java:379)
at com.example.orientdbclient.OrientDBController.main(OrientDBController.java:27)
closed time in 2 days
tonglshpush eventorientechnologies/orientdb
commit sha bfe34dee1565e484da353f90b65a71db425932d4
Implement DROP CLASS with parameter Resolves #9627
push time in 2 days
issue commentorientechnologies/orientdb
ODatabaseSession().command(String query, Object... args) unsupport for DROP?
got it ,thank you.
comment created time in 2 days
issue commentorientechnologies/orientdb
ODatabaseSession().command(String query, Object... args) unsupport for DROP?
Oh yes, sorry, I got it... The problem is the parameter. No, it's not supported for DROP CLASS in the new SQL executor, but I can implement it right away, it's pretty easy. It will be in v 3.2.1
Thanks
Luigi
comment created time in 2 days
issue commentorientechnologies/orientdb
ODatabaseSession().command(String query, Object... args) unsupport for DROP?
@luigidellaquila
comment created time in 2 days
issue commentorientechnologies/orientdb
ODatabaseSession().command(String query, Object... args) unsupport for DROP?
wait please... db.command(String query, Object... args) throw the exception too.
comment created time in 2 days
issue closedorientechnologies/orientdb
ODatabaseSession().command(String query, Object... args) unsupport for DROP?
OrientDB Version: 3.2.0
Java Version: 8
maven dependency: orientdb-client 3.2.0
i want to drop class named "zzz"
can work:
ODatabaseSession session = pool.acquire();
OResultSet rs = session.query("drop class zzz");
rs.close();
not work:
ODatabaseSession session = pool.acquire();
OResultSet rs = session.query("drop class ?" ,"zzz");
rs.close();
is it unsupported ?
Exception in thread "main" com.orientechnologies.orient.core.sql.OCommandSQLParsingException: Error parsing query:
drop class ?
^
Encountered " <DROP> "drop "" at line 1, column 1.
Was expecting one of:
<SELECT> ...
<TRAVERSE> ...
<MATCH> ...
<INSERT> ...
<RETURN> ...
<FIND> ...
<REBUILD> ...
<OPTIMIZE> ...
<GRANT> ...
<REVOKE> ...
<BEGIN> ...
<COMMIT> ...
<ROLLBACK> ...
<IF> ...
<SLEEP> ...
<CONSOLE> ...
<MOVE> ...
<SELECT> ...
<SELECT> ...
<TRAVERSE> ...
<MATCH> ...
<FIND> ...
<INSERT> ...
<MOVE> ...
DB name="cmdb"
Error Code="1"
DB name="cmdb"
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:78)
at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:499)
at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:480)
at com.orientechnologies.orient.client.binary.OChannelBinaryAsynchClient.handleException(OChannelBinaryAsynchClient.java:355)
at com.orientechnologies.orient.client.binary.OChannelBinaryAsynchClient.handleStatus(OChannelBinaryAsynchClient.java:303)
at com.orientechnologies.orient.client.binary.OChannelBinaryAsynchClient.handleStatus(OChannelBinaryAsynchClient.java:325)
at com.orientechnologies.orient.client.binary.OChannelBinaryAsynchClient.beginResponse(OChannelBinaryAsynchClient.java:209)
at com.orientechnologies.orient.client.binary.OChannelBinaryAsynchClient.beginResponse(OChannelBinaryAsynchClient.java:167)
at com.orientechnologies.orient.client.remote.OStorageRemote.beginResponse(OStorageRemote.java:2006)
at com.orientechnologies.orient.client.remote.OStorageRemote.lambda$networkOperationRetryTimeout$2(OStorageRemote.java:390)
at com.orientechnologies.orient.client.remote.OStorageRemote.baseNetworkOperation(OStorageRemote.java:455)
at com.orientechnologies.orient.client.remote.OStorageRemote.networkOperationRetryTimeout(OStorageRemote.java:370)
at com.orientechnologies.orient.client.remote.OStorageRemote.networkOperation(OStorageRemote.java:410)
at com.orientechnologies.orient.client.remote.OStorageRemote.query(OStorageRemote.java:1098)
at com.orientechnologies.orient.core.db.document.ODatabaseDocumentRemote.query(ODatabaseDocumentRemote.java:379)
at com.example.orientdbclient.OrientDBController.main(OrientDBController.java:27)
closed time in 2 days
tonglshissue commentorientechnologies/orientdb
ODatabaseSession().command(String query, Object... args) unsupport for DROP?
Hi @tonglsh
db.query() is only for queries that do not modify the state (ie. SELECT, TRAVERSE, MATCH...).
For DROP you have to use db.command()
Thanks
Luigi
comment created time in 2 days
issue openedorientechnologies/orientdb
ODatabaseSession().command(String query, Object... args) unsupport for DROP?
OrientDB Version: 3.2.0
Java Version: 8
maven dependency: orientdb-client 3.2.0
i want to drop class named "zzz"
can work:
ODatabaseSession session = pool.acquire();
OResultSet rs = session.query("drop class zzz");
rs.close();
not work:
ODatabaseSession session = pool.acquire();
OResultSet rs = session.query("drop class ?" ,"zzz");
rs.close();
is it unsupported ?
Exception in thread "main" com.orientechnologies.orient.core.sql.OCommandSQLParsingException: Error parsing query:
drop class ?
^
Encountered " <DROP> "drop "" at line 1, column 1.
Was expecting one of:
<SELECT> ...
<TRAVERSE> ...
<MATCH> ...
<INSERT> ...
<RETURN> ...
<FIND> ...
<REBUILD> ...
<OPTIMIZE> ...
<GRANT> ...
<REVOKE> ...
<BEGIN> ...
<COMMIT> ...
<ROLLBACK> ...
<IF> ...
<SLEEP> ...
<CONSOLE> ...
<MOVE> ...
<SELECT> ...
<SELECT> ...
<TRAVERSE> ...
<MATCH> ...
<FIND> ...
<INSERT> ...
<MOVE> ...
DB name="cmdb"
Error Code="1"
DB name="cmdb"
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:78)
at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:499)
at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:480)
at com.orientechnologies.orient.client.binary.OChannelBinaryAsynchClient.handleException(OChannelBinaryAsynchClient.java:355)
at com.orientechnologies.orient.client.binary.OChannelBinaryAsynchClient.handleStatus(OChannelBinaryAsynchClient.java:303)
at com.orientechnologies.orient.client.binary.OChannelBinaryAsynchClient.handleStatus(OChannelBinaryAsynchClient.java:325)
at com.orientechnologies.orient.client.binary.OChannelBinaryAsynchClient.beginResponse(OChannelBinaryAsynchClient.java:209)
at com.orientechnologies.orient.client.binary.OChannelBinaryAsynchClient.beginResponse(OChannelBinaryAsynchClient.java:167)
at com.orientechnologies.orient.client.remote.OStorageRemote.beginResponse(OStorageRemote.java:2006)
at com.orientechnologies.orient.client.remote.OStorageRemote.lambda$networkOperationRetryTimeout$2(OStorageRemote.java:390)
at com.orientechnologies.orient.client.remote.OStorageRemote.baseNetworkOperation(OStorageRemote.java:455)
at com.orientechnologies.orient.client.remote.OStorageRemote.networkOperationRetryTimeout(OStorageRemote.java:370)
at com.orientechnologies.orient.client.remote.OStorageRemote.networkOperation(OStorageRemote.java:410)
at com.orientechnologies.orient.client.remote.OStorageRemote.query(OStorageRemote.java:1098)
at com.orientechnologies.orient.core.db.document.ODatabaseDocumentRemote.query(ODatabaseDocumentRemote.java:379)
at com.example.orientdbclient.OrientDBController.main(OrientDBController.java:27)
created time in 2 days
issue commentorientechnologies/orientdb
Hi! I had the same problem using orient 3.1.5. Any news about this?
DWL:database: block size = 4096 bytes, maximum segment size = 347 MB [DoubleWriteLogGL]Exception `18748728` in storage `plocal:/path/to/database`: 3.1.5 - Veloce (build 846eeb77dcb175a9fbd7ed534e039424322f44a7, branch 3.1.x)
com.orientechnologies.orient.core.exception.OStorageException: Exception during execution of atomic operation inside of storage database
at com.orientechnologies.orient.core.storage.impl.local.paginated.atomicoperations.OAtomicOperationsManager.executeInsideAtomicOperation(OAtomicOperationsManager.java:195)
at com.orientechnologies.orient.core.storage.impl.local.OAbstractPaginatedStorage.open(OAbstractPaginatedStorage.java:422)
at com.orientechnologies.orient.core.db.OrientDBEmbedded.open(OrientDBEmbedded.java:483)
at com.orientechnologies.orient.core.db.OrientDBEmbedded.open(OrientDBEmbedded.java:418)
at com.orientechnologies.orient.server.OServer.openDatabase(OServer.java:979)
at com.orientechnologies.orient.server.OServer.openDatabase(OServer.java:947)
at com.orientechnologies.orient.server.OConnectionBinaryExecutor.executeDatabaseOpen37(OConnectionBinaryExecutor.java:1369)
at com.orientechnologies.orient.client.remote.message.OOpen37Request.execute(OOpen37Request.java:75)
at com.orientechnologies.orient.server.network.protocol.binary.ONetworkProtocolBinary.sessionRequest(ONetworkProtocolBinary.java:355)
at com.orientechnologies.orient.server.network.protocol.binary.ONetworkProtocolBinary.execute(ONetworkProtocolBinary.java:239)
at com.orientechnologies.common.thread.OSoftThread.run(OSoftThread.java:67)
Caused by: com.orientechnologies.orient.core.exception.OStorageException: Exception during execution of component operation inside component config.cd in storage database
at com.orientechnologies.orient.core.storage.impl.local.paginated.atomicoperations.OAtomicOperationsManager.executeInsideComponentOperation(OAtomicOperationsManager.java:221)
at com.orientechnologies.orient.core.storage.impl.local.paginated.atomicoperations.OAtomicOperationsManager.executeInsideComponentOperation(OAtomicOperationsManager.java:206)
at com.orientechnologies.orient.core.storage.impl.local.paginated.base.ODurableComponent.executeInsideComponentOperation(ODurableComponent.java:102)
at com.orientechnologies.orient.core.storage.cluster.v2.OPaginatedClusterV2.open(OPaginatedClusterV2.java:211)
at com.orientechnologies.orient.core.storage.config.OClusterBasedStorageConfiguration.load(OClusterBasedStorageConfiguration.java:250)
at com.orientechnologies.orient.core.storage.disk.OLocalPaginatedStorage.initConfiguration(OLocalPaginatedStorage.java:558)
at com.orientechnologies.orient.core.storage.impl.local.OAbstractPaginatedStorage.lambda$open$1(OAbstractPaginatedStorage.java:433)
at com.orientechnologies.orient.core.storage.impl.local.paginated.atomicoperations.OAtomicOperationsManager.executeInsideAtomicOperation(OAtomicOperationsManager.java:189)
... 10 more
Caused by: com.orientechnologies.orient.core.exception.OStorageException: File with name config.cd does not exist in storage database
at com.orientechnologies.orient.core.storage.cache.local.OWOWCache.loadFile(OWOWCache.java:760)
at com.orientechnologies.orient.core.storage.impl.local.paginated.atomicoperations.OAtomicOperationBinaryTracking.loadFile(OAtomicOperationBinaryTracking.java:372)
at com.orientechnologies.orient.core.storage.impl.local.paginated.base.ODurableComponent.openFile(ODurableComponent.java:193)
at com.orientechnologies.orient.core.storage.cluster.v2.OPaginatedClusterV2.lambda$open$1(OPaginatedClusterV2.java:216)
at com.orientechnologies.orient.core.storage.impl.local.paginated.atomicoperations.OAtomicOperationsManager.executeInsideComponentOperation(OAtomicOperationsManager.java:214)
... 17 more
comment created time in 3 days
issue commentorientechnologies/orientdb
File with name config.cd does not exist in <dbname>
Hi! I had the same problem using orient 3.1.5. Any news about this?
DWL:database: block size = 4096 bytes, maximum segment size = 347 MB [DoubleWriteLogGL]Exception `18748728` in storage `plocal:/path/to/database`: 3.1.5 - Veloce (build 846eeb77dcb175a9fbd7ed534e039424322f44a7, branch 3.1.x)
com.orientechnologies.orient.core.exception.OStorageException: Exception during execution of atomic operation inside of storage database
at com.orientechnologies.orient.core.storage.impl.local.paginated.atomicoperations.OAtomicOperationsManager.executeInsideAtomicOperation(OAtomicOperationsManager.java:195)
at com.orientechnologies.orient.core.storage.impl.local.OAbstractPaginatedStorage.open(OAbstractPaginatedStorage.java:422)
at com.orientechnologies.orient.core.db.OrientDBEmbedded.open(OrientDBEmbedded.java:483)
at com.orientechnologies.orient.core.db.OrientDBEmbedded.open(OrientDBEmbedded.java:418)
at com.orientechnologies.orient.server.OServer.openDatabase(OServer.java:979)
at com.orientechnologies.orient.server.OServer.openDatabase(OServer.java:947)
at com.orientechnologies.orient.server.OConnectionBinaryExecutor.executeDatabaseOpen37(OConnectionBinaryExecutor.java:1369)
at com.orientechnologies.orient.client.remote.message.OOpen37Request.execute(OOpen37Request.java:75)
at com.orientechnologies.orient.server.network.protocol.binary.ONetworkProtocolBinary.sessionRequest(ONetworkProtocolBinary.java:355)
at com.orientechnologies.orient.server.network.protocol.binary.ONetworkProtocolBinary.execute(ONetworkProtocolBinary.java:239)
at com.orientechnologies.common.thread.OSoftThread.run(OSoftThread.java:67)
Caused by: com.orientechnologies.orient.core.exception.OStorageException: Exception during execution of component operation inside component config.cd in storage database
at com.orientechnologies.orient.core.storage.impl.local.paginated.atomicoperations.OAtomicOperationsManager.executeInsideComponentOperation(OAtomicOperationsManager.java:221)
at com.orientechnologies.orient.core.storage.impl.local.paginated.atomicoperations.OAtomicOperationsManager.executeInsideComponentOperation(OAtomicOperationsManager.java:206)
at com.orientechnologies.orient.core.storage.impl.local.paginated.base.ODurableComponent.executeInsideComponentOperation(ODurableComponent.java:102)
at com.orientechnologies.orient.core.storage.cluster.v2.OPaginatedClusterV2.open(OPaginatedClusterV2.java:211)
at com.orientechnologies.orient.core.storage.config.OClusterBasedStorageConfiguration.load(OClusterBasedStorageConfiguration.java:250)
at com.orientechnologies.orient.core.storage.disk.OLocalPaginatedStorage.initConfiguration(OLocalPaginatedStorage.java:558)
at com.orientechnologies.orient.core.storage.impl.local.OAbstractPaginatedStorage.lambda$open$1(OAbstractPaginatedStorage.java:433)
at com.orientechnologies.orient.core.storage.impl.local.paginated.atomicoperations.OAtomicOperationsManager.executeInsideAtomicOperation(OAtomicOperationsManager.java:189)
... 10 more
Caused by: com.orientechnologies.orient.core.exception.OStorageException: File with name config.cd does not exist in storage database
at com.orientechnologies.orient.core.storage.cache.local.OWOWCache.loadFile(OWOWCache.java:760)
at com.orientechnologies.orient.core.storage.impl.local.paginated.atomicoperations.OAtomicOperationBinaryTracking.loadFile(OAtomicOperationBinaryTracking.java:372)
at com.orientechnologies.orient.core.storage.impl.local.paginated.base.ODurableComponent.openFile(ODurableComponent.java:193)
at com.orientechnologies.orient.core.storage.cluster.v2.OPaginatedClusterV2.lambda$open$1(OPaginatedClusterV2.java:216)
at com.orientechnologies.orient.core.storage.impl.local.paginated.atomicoperations.OAtomicOperationsManager.executeInsideComponentOperation(OAtomicOperationsManager.java:214)
... 17 more
comment created time in 3 days
issue closedorientechnologies/orientdb
Socket Read time out REST API batch push using thread in java
OrientDB Version: <3.2.0>
Java Version: <1.8>
OS: <mac os 11.3.1>
Expected behavior
Am pushing batch of vertex through REST API from java via Thread.It results in Socket java.net.SocketTimeoutException: Read timed out .Am i missing any configuration here ?I've tried configuring NETWORK_SOCKET_TIMEOUT,still same exists.Kindly help me on this. Request details : Content-Type - application/json Authorization header has been set
Exception trace Suppressed: java.net.SocketTimeoutException: Read timed out| at java.net.SocketInputStream.socketRead0(Native Method)| at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)| at java.net.SocketInputStream.read(SocketInputStream.java:171)| at java.net.SocketInputStream.read(SocketInputStream.java:141)| at java.io.BufferedInputStream.fill(BufferedInputStream.java:246)| at java.io.BufferedInputStream.read1(BufferedInputStream.java:286)| at java.io.BufferedInputStream.read(BufferedInputStream.java:345)| at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:735)| at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:678)| at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1587)| at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1492)| at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480)|
closed time in 3 days
KirubakaranSPissue commentorientechnologies/orientdb
Socket Read time out REST API batch push using thread in java
It all depends on how big is each vertex. How many properties? Do you have binary or long strings? If you can compute that amount in terms of total Kb sent it would be helpful.
Generally speaking, if you're sending big packets concurrently, OrientDB's web socket could having hard time to process the requests.
Try reducing the parallel threads from 10 to 3 and see how it goes. Also from 1000 vertices, try with 300.
Try to play around those numbers to see a good configuration based on your data and hw/sw available.
comment created time in 3 days
issue commentorientechnologies/orientdb
Socket Read time out REST API batch push using thread in java
I am inserting 1000 vertices as JSON through rest API from java.
On Wed, Jun 16, 2021 at 6:57 PM Luca Garulli ***@***.***> wrote:
1,000 operations or 1,000 bytes? How big is the packet in Kb/Mb?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/orientechnologies/orientdb/issues/9624#issuecomment-862379734, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJRKU3ETJMS6K4UIVTYLOD3TTCRFJANCNFSM46OXQHPA .
comment created time in 4 days
issue commentorientechnologies/orientdb
Socket Read time out REST API batch push using thread in java
1,000 operations or 1,000 bytes? How big is the packet in Kb/Mb?
comment created time in 4 days
issue commentorientechnologies/orientdb
Socket Read time out REST API batch push using thread in java
The size of the packet is 1000 and parallely running 10 threads.
On Wed, Jun 16, 2021 at 12:15 AM Luca Garulli ***@***.***> wrote:
What's the size of the packet you're sending?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/orientechnologies/orientdb/issues/9624#issuecomment-861746257, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJRKU3BUHDR6XJFAYM36Y53TS6NVFANCNFSM46OXQHPA .
comment created time in 4 days
issue commentorientechnologies/orientdb
Socket Read time out REST API batch push using thread in java
What's the size of the packet you're sending?
comment created time in 4 days
issue commentorientechnologies/orientdb
how to save a database so I can recover from : Id of WAL operation can not be duplicated?
3.1.7 also works. I cant go beyond this.
comment created time in 4 days
PR opened orientechnologies/orientdb
pr created time in 5 days
issue commentorientechnologies/orientdb
[3.2.0] JS function invocation issues
Hi Luca, Can you please check this https://github.com/orientechnologies/orientdb/issues/9624 issue?As it is very urgent,kindly update me on this. Thanks and Regards Kirubakaran S P
On Tue, Jun 15, 2021 at 11:05 AM Luca Garulli ***@***.***> wrote:
Closed #9596 https://github.com/orientechnologies/orientdb/issues/9596.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/orientechnologies/orientdb/issues/9596#event-4889292525, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJRKU3A6SH6BCRYU5XKI5MDTS3RDDANCNFSM432SXCKA .
comment created time in 5 days
issue openedorientechnologies/orientdb
Reached maximum number of concurrent connections with single script
OrientDB Version: 3.2.0
Java Version: openjdk version "11.0.11"
OS: Ubuntu 21.04
Expected behavior
To run a batch script with lot of inserts or updates without consuming all available connections.
Actual behavior
When running a batch script through the console, it seems like each insert or update is consuming one "connection", so the limit is reached and no new connections can be made (although the script is still executing fine). The server logs Reached maximum number of concurrent connections (max=1000, current=213837), reject incoming connection from /127.0.0.1:52756 [OServerNetworkListener].
Steps to reproduce
I can reproduce it with a fresh install of 3.2.0. Unzip zip and start server.
Create a script with thousand lines like this: create vertex V set num = 1; ...
In console:
orientdb> connect remote:localhost/demodb admin admin;
Connecting to database [remote:localhost/demodb] with user 'admin'...OK
orientdb {db=demodb}> load script script.sql;
Try to connect to server (i.e. opening Studio) while the script is executing, the connection is rejected and logs:
Reached maximum number of concurrent connections (max=1000, current=3779), reject incoming connection from /127.0.0.1:57932 [OServerNetworkListener] ("current" is an increasing number).
created time in 5 days
push eventorientechnologies/orientdb
commit sha 0f7e589a9da0eabbda19c7f86ff89169371baf88
Fix index space consumption: refactoring of the deletion of non-leaf entries.
commit sha ec10c2f092d9c7b2a1e8070694cabca6fbf43efd
Fix index space consumption: recursive removal of parent entries has been implemented.
commit sha c221a5627ac19cde360979028007c73dfe4b84cd
Fix index space consumption: bug fixing in key removal.
commit sha 50591067fa11e2d9c84942761de93a36059c8b7a
Fix index space consumption: all pages which are removed from tree are added into free list.
commit sha 203fbbbfa4e2c80bfab8e9522cfe8c678af2d77e
Errors in space management of indexes were fixed.
commit sha 61ae7d39e760f009e275aef168f19552cb89ded4
Merge branch '3.1.x' into laa_btree_space
push time in 5 days
push eventorientechnologies/orientdb
commit sha a3c006635c8a92137bbdc3c16071251a7a9a1892
Reload all the shared context after db restore
commit sha e2f352db6bdc5df7f8a7283418a545b7277613de
Implement specific List for tx index changes (to be optimized to reduce the effort of adding/removing entries based OTransactionIndexChangesPerKey logics
commit sha f0029b16205f734d5853d1005d787428e788800b
Optimise predicate security checks on property validation
commit sha 4b98092c095d2e8c89f1c8f0d70d141fffc8cb09
Allow concurrent access to active queries stats
commit sha 17fc0104c868d84f1f56cd84973b3ebfda9a0404
Optimise OTxIndexChangesList and enable it for index tx management
commit sha 4e739d194f10699692452ad3c27fd674c4e100d4
Merge pull request #9611 from orientechnologies/index_changes_optimization_2 Index changes optimization
commit sha 1353ae81d1c518fa29c12a2f29f51ea3a4c99300
Allow binary connections without session token disabled by default for security reasons it can be enabled with global config network.binary.allowNoToken
commit sha e1660dede78b68a33087336c47e5b29e027fffe0
Update history for v 3.1.12
commit sha b225e767a05a41efa9279a0084ade3fdcec8ab92
releasing OrientDB 3.1.12
commit sha 153ac6951e80c40d7245940efaf9232d7b85032f
version bumped to 3.1.13-SNAPSHOT
commit sha 0cbfa2f0a828d7a399ee47ee80aec5eab4af6a48
Add security check on cached sequences
commit sha 659d78eec6ad1e65ed2954db16cdf88860c3b861
Optimise security checks canUpdate()
commit sha 29db198e3c56ca2b5c0a3067cae3422e3b88633e
Optimise security checks
commit sha d9cfb3d2e0c13742e43db9679d56a081d4e45cef
Optimise record save
commit sha 43860b882387b3a21eff23f0ad45d027c5736c4f
Optimise access to cluster name
commit sha b37139f66761b285fd17a38bf01a0a8bdf1df0e4
Optimise field conversion
commit sha 867fb9b65ede9386fb0cf0dbba479e71f90c75ec
Optimise query execution planning in distributed
commit sha 61ae7d39e760f009e275aef168f19552cb89ded4
Merge branch '3.1.x' into laa_btree_space
push time in 5 days
push eventorientechnologies/orientdb
commit sha 50591067fa11e2d9c84942761de93a36059c8b7a
Fix index space consumption: all pages which are removed from tree are added into free list.
commit sha 203fbbbfa4e2c80bfab8e9522cfe8c678af2d77e
Errors in space management of indexes were fixed.
push time in 5 days
issue closedorientechnologies/orientdb
[3.2.0] JS function invocation issues
OrientDB Version: 3.2.0 (docker)
Errors are produced when executing custom JS functions that call documented "built-in" functions such as orient.getDatabase().
Setting script.polyglot.useGraal = false does not make a difference.
Errors
The following error is seen in Studio:
Error on parsing script at position #0: Error on execution of the script Script: test ------^
org.graalvm.polyglot.PolyglotException: TypeError: invokeMember (getDatabase) on com.orientechnologies.orient.core.command.script.OScriptOrientWrapper@2db24b13 failed due to: Unknown identifier: getDatabase
Executing a similar function from a SQL batch script causes the same error:
Error on parsing script at position #0: Error on execution of the script
... as well as this stack trace:
orientdb_1 | java.lang.IllegalArgumentException: object is not an instance of declaring class
orientdb_1 | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
orientdb_1 | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
orientdb_1 | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
orientdb_1 | at java.lang.reflect.Method.invoke(Method.java:498)
orientdb_1 | at com.orientechnologies.orient.core.command.script.OCommandExecutorUtility.transformResult(OCommandExecutorUtility.java:63)
orientdb_1 | at com.orientechnologies.orient.core.command.script.OCommandExecutorFunction.executeInContext(OCommandExecutorFunction.java:106)
orientdb_1 | at com.orientechnologies.orient.core.metadata.function.OFunction.executeInContext(OFunction.java:161)
orientdb_1 | at com.orientechnologies.orient.core.metadata.function.ODatabaseFunction.execute(ODatabaseFunction.java:46)
orientdb_1 | at com.orientechnologies.orient.core.sql.parser.OFunctionCall.execute(OFunctionCall.java:131)
orientdb_1 | at com.orientechnologies.orient.core.sql.parser.OFunctionCall.execute(OFunctionCall.java:82)
orientdb_1 | at com.orientechnologies.orient.core.sql.parser.OLevelZeroIdentifier.execute(OLevelZeroIdentifier.java:52)
orientdb_1 | at com.orientechnologies.orient.core.sql.parser.OBaseIdentifier.execute(OBaseIdentifier.java:62)
orientdb_1 | at com.orientechnologies.orient.core.sql.parser.OBaseExpression.execute(OBaseExpression.java:111)
orientdb_1 | at com.orientechnologies.orient.core.sql.parser.OExpression.execute(OExpression.java:102)
orientdb_1 | at com.orientechnologies.orient.core.sql.parser.OLetStatement.executeSimple(OLetStatement.java:29)
orientdb_1 | at com.orientechnologies.orient.core.sql.executor.OSingleOpExecutionPlan.executeInternal(OSingleOpExecutionPlan.java:95)
orientdb_1 | at com.orientechnologies.orient.core.sql.executor.ScriptLineStep.syncPull(ScriptLineStep.java:37)
orientdb_1 | at com.orientechnologies.orient.core.sql.executor.OScriptExecutionPlan.executeFull(OScriptExecutionPlan.java:208)
orientdb_1 | at com.orientechnologies.orient.core.sql.executor.ForEachStep.syncPull(ForEachStep.java:53)
orientdb_1 | at com.orientechnologies.orient.core.sql.executor.OSelectExecutionPlan.fetchNext(OSelectExecutionPlan.java:34)
orientdb_1 | at com.orientechnologies.orient.core.sql.executor.OUpdateExecutionPlan.executeInternal(OUpdateExecutionPlan.java:41)
orientdb_1 | at com.orientechnologies.orient.core.sql.executor.ScriptLineStep.syncPull(ScriptLineStep.java:33)
orientdb_1 | at com.orientechnologies.orient.core.sql.executor.OScriptExecutionPlan.executeFull(OScriptExecutionPlan.java:208)
orientdb_1 | at com.orientechnologies.orient.core.sql.parser.WhileStep.syncPull(WhileStep.java:45)
orientdb_1 | at com.orientechnologies.orient.core.sql.executor.OSelectExecutionPlan.fetchNext(OSelectExecutionPlan.java:34)
orientdb_1 | at com.orientechnologies.orient.core.sql.executor.OUpdateExecutionPlan.executeInternal(OUpdateExecutionPlan.java:41)
orientdb_1 | at com.orientechnologies.orient.core.sql.executor.ScriptLineStep.syncPull(ScriptLineStep.java:33)
orientdb_1 | at com.orientechnologies.orient.core.sql.executor.OScriptExecutionPlan.executeUntilReturn(OScriptExecutionPlan.java:180)
orientdb_1 | at com.orientechnologies.orient.core.sql.executor.OScriptExecutionPlan.doExecute(OScriptExecutionPlan.java:75)
orientdb_1 | at com.orientechnologies.orient.core.sql.executor.OScriptExecutionPlan.fetchNext(OScriptExecutionPlan.java:39)
orientdb_1 | at com.orientechnologies.orient.core.sql.parser.OLocalResultSet.fetchNext(OLocalResultSet.java:36)
orientdb_1 | at com.orientechnologies.orient.core.sql.parser.OLocalResultSet.<init>(OLocalResultSet.java:27)
orientdb_1 | at com.orientechnologies.orient.core.command.OSqlScriptExecutor.executeInternal(OSqlScriptExecutor.java:126)
orientdb_1 | at com.orientechnologies.orient.core.command.OSqlScriptExecutor.execute(OSqlScriptExecutor.java:65)
orientdb_1 | at com.orientechnologies.orient.core.db.document.ODatabaseDocumentEmbedded.execute(ODatabaseDocumentEmbedded.java:786)
orientdb_1 | at com.orientechnologies.orient.server.OConnectionBinaryExecutor.executeQuery(OConnectionBinaryExecutor.java:1358)
orientdb_1 | at com.orientechnologies.orient.client.remote.message.OQueryRequest.execute(OQueryRequest.java:143)
orientdb_1 | at com.orientechnologies.orient.server.network.protocol.binary.ONetworkProtocolBinary.sessionRequest(ONetworkProtocolBinary.java:355)
orientdb_1 | at com.orientechnologies.orient.server.network.protocol.binary.ONetworkProtocolBinary.execute(ONetworkProtocolBinary.java:239)
orientdb_1 | at com.orientechnologies.common.thread.OSoftThread.run(OSoftThread.java:67)
Steps to reproduce
Create a JS function containing the following line, and execute it.
var db = orient.getDatabase();
closed time in 5 days
MarttiR