Re: [orientdb] [Newbie Question][Web Development] Where should I extract OrientDB ?

[Luigi Dell'Aquila]

Hi Peter,

I'm afraid there is no way to decide the path per single DB, the
configuration is at server level, so you can change the place when you put
all the databases (a symbolic link is enough on Linux), but it's all or
nothing.
All this applies to the stand-alone installation of course. If the
application uses OrientDB in embedded mode, each DB can easily be stored in
a different path (you just create different OrientDB instances with
different paths).

Thanks

Luigi


Il giorno sab 14 mar 2020 alle ore 02:21 Just Peter <
cochondindedesarden...@gmail.com> ha scritto:

> Hi !
>
> I am a regular MySQL user and for a new project I'd like to try OrientDB !
> I already had the opportunity to test it, so I already know the basics of
> how it works (thanks to the course on udemy - a little outdated but still
> relevant).
>
> Unlike MySQL, I haven't figured out how to create a database in a specific
> location on my hard drive. Whenever I create a database, OrientDB places it
> in the ORIENTDB_HOME/databases folder.
> I do not know if it is possible, I imagine so, but I did not find a
> well-defined guide to carry out this operation.
>
> I plan to use OrientDB on my website, should I then extract OrientDB to
> the root folder of my site?
> And what about deployment?
>
> The last question may be specific to the host we are using, so I don't
> know if an answer can be given. If someone could at least answer the first
> it would suit me a lot!
>
> Thanks
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/orient-database/976190b3-6b84-4c12-94f1-43a69d185fb1%40googlegroups.com
> 
> .
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/orient-database/CAFZLH8mEj7uvE-3%3DOTeLrcV%3DKE2mzgpwXnmYOZywe_7VM_kDaw%40mail.gmail.com.

Re: [orientdb] Can I upsert an Edge instead of just grah.addVertex

[Luigi Dell'Aquila]

Hi Tia,

OrientDB has UPSERT for edges, but with limited support, ie. it only checks
if the edge already exists between the two vertices and it needs a unique
index.
See https://orientdb.org/docs/3.0.x/sql/SQL-Create-Edge.html

I hope it helps

Thanks

Luigi

Il giorno dom 23 feb 2020 alle ore 21:14 ODBUser19 <
anooprathi.j...@gmail.com> ha scritto:

> Hi,
>
> I am trying to run a batch to create vertex and have Unique Index on one
> of the property. Is there any way I can update the record if the vertex was
> already present? I am precisely looking for Upsert command. Does OrientDB
> has something like this or is there any way I could achieve this.
>
> TIA!
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/orient-database/e06383c3-e8ac-435f-9c2b-c92702c33152%40googlegroups.com
> 
> .
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/orient-database/CAFZLH8m%3D24HUrkSrB3y%2BCNH9QGXX6nb5g6BQxGCNzNYRdydKBg%40mail.gmail.com.

Re: [orientdb] Price of Orient DB Enterprise edition

[Luigi Dell'Aquila]

Hi Neerav,

Glad to know you are interested in OrientDB an in our Enterprise services.
I suggest you to contact the email address orientdb_enquir...@sap.com for
all the commercial details

Thanks

Luigi


Il giorno gio 10 ott 2019 alle ore 14:46 Neerav Singh 
ha scritto:

> Hello
>
> I am speaking on behalf of my organization. We are looking to purchase
> Orient DB enterprise edition license. We make data management products for
> our automotive clients and for that we want to use it. Customers use
> in-premises servers for the deployment.
>
> Requesting you all for the help or pointers.
>
> Thank you
> Cheers,
> Neerav
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/orient-database/5872ddcc-93bf-4e63-b5dd-c9fe8b53dd77%40googlegroups.com
> 
> .
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/orient-database/CAFZLH8%3DkX-VDX-mPYL1kCFCSYZUFJRrxo3ZbpmJsFTSUGRd0Ng%40mail.gmail.com.

Re: [orientdb] Query on edge property gives unexplicable results

[Luigi Dell'Aquila]

Hi,

Please use back-ticks when you refer to property names, and use the new SQL
executor (you are using the legacy one), I'm pretty sure it all works fine
;-)

db.query("SELECT expand("
   + "both('Distance').bothE()[`Entity similarity` > 1 ]"
   + ") FROM " + v.getIdentity());

Thanks

Luigi

Il giorno gio 29 ago 2019 alle ore 14:58 Maverick 
ha scritto:

> Can somebody here explain why the code below produces 1 result (while it
> should give zero, because the condition >1 is not matched)?
> If I query 'Entity similarity' < 1 it gives zero records. The same if I
> use backticks instead of apex.
> I'm using version 3.0.19
>
> package odbtest; import
> com.orientechnologies.orient.core.db.ODatabasePool; import
> com.orientechnologies.orient.core.db.ODatabaseType; import
> com.orientechnologies.orient.core.db.OrientDB; import
> com.orientechnologies.orient.core.db.OrientDBConfig; import
> com.orientechnologies.orient.core.db.document.ODatabaseDocument; import
> com.orientechnologies.orient.core.db.record.OIdentifiable; import
> com.orientechnologies.orient.core.record.OEdge; import
> com.orientechnologies.orient.core.record.OVertex; import
> com.orientechnologies.orient.core.record.impl.ODocument; import
> com.orientechnologies.orient.core.sql.query.OSQLSynchQuery; public class
> ODBTest { public static void main( String[] args ) { new ODBTest().run(); }
> ODatabaseDocument session; public void run() { OrientDBConfig dbConfig =
> OrientDBConfig.defaultConfig(); String dbname = "test"; OrientDB orientDB =
> new OrientDB("memory:", dbConfig); orientDB.createIfNotExists( dbname,
> ODatabaseType.MEMORY ); session = new ODatabasePool( orientDB, dbname,
> "admin", "admin" ).acquire(); session.createVertexClass( "Entry" );
> session.createEdgeClass( "Distance" ); OVertex v1 = addVertex( "Vertex 1"
> ); OVertex v2 = addVertex( "Vertex 2" ); addEdge( v1, v2, 0.2 ); query( v1
> ); } private OVertex addVertex( String prop ) { OVertex v =
> session.newVertex( "Entry" ); v.setProperty( "myProp", prop ); v.save();
> session.commit(); return v; } public void addEdge( OVertex v1, OVertex v2,
> double distance ) { OEdge edge = session.newEdge( v1, v2, "Distance" );
> edge.setProperty( "Entity similarity", distance ); edge.save();
> session.commit(); } public void query( OVertex v ) { for( OIdentifiable id
> : new OSQLSynchQuery( "SELECT expand(" +
> "both('Distance').bothE()['Entity similarity' > 1 ]" + ") FROM " +
> v.getIdentity() )) { ODocument doc = session.getRecord( id );
> System.out.println( doc ); } } }
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/orient-database/5823785e-3843-4253-9bf6-a281be7c06d2%40googlegroups.com
> 
> .
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/orient-database/CAFZLH8ntEzsoKoMEimYTSGMXsw%3DMhpfzm72QU-ynt9fVvnn0Jg%40mail.gmail.com.

Re: [orientdb] Orient DB Server unreachable frequently - Urgent - Severe business impact

[Luigi Dell'Aquila]

Hi Ram,

Thank you very much for the detailed information.
The only strange thing I see in the logs is the following

--> com.orientechnologies.orient.core.exception.OCommandExecutionException:
Class 'NULL' was not found in current database [ONetworkProtocolHttpDb]
2019-08-21 12:03:39:675 SEVERE Internal server error:
com.orientechnologies.orient.core.exception.OQueryParsingException: Error
on parsing query at position #5: Error on parsing query
Query:  null timeout 5000
--^


but it seems more like a wrong query than a problem with the server, so
it's unlikely to be the reason for your problem.

There is one thing that could give us more information on what's
actually happening: could you please take a thread dump when the server is
stuck?

Thanks

Luigi

Il giorno mer 21 ago 2019 alle ore 18:35 Ram Karthik <
ramkarthik.m...@gmail.com> ha scritto:

> To add more details the problem,
>
> We have more than 500+ queries/API built on 200+ vertex based schema. All
> the query were written optimally with right indexes so that at any normal
> condition the response time of the queries will be under 50 ms. Most of the
> query response in less than 20 ms. You can refer the screenshot shared
> before.
>
> All of the sudden one of these query freeze at the database indefinitely
> and all the subsequent queries fired from application also start to freeze
> indefinitely. This leads to an increase in concurrent connections to the
> database, with none of the query responding back. This leads to the maximum
> connection limit at the database level and the database stop accepting new
> connections. Looking at the database, the CPU, Memory remains stable. There
> is a very slight increase in CPU (due to too high concurrent connection).
> This indicates the query is not executed in the database and are waiting
> for resource/lock.
>
> To bring the server back to normal, we have to stop the database (thus
> kill the connections), bounce back again to access. This happens very
> frequently and sometime during restart the index crashes. So we have to
> restore the database from backup.
>
> We log every query being executed. After bouncing the server, we tried to
> run the frozen queries (same query with same parameter), they executed
> normally as usual and responded in usual latency (10 - 20 ms). We tried
> running all the queries (first query, some random query from all frozen
> query set), all executed as expected.
>
> When the database goes to freeze mode, even simple query that supposes
> pick single record by primary Id also freezes. We have no clue why the
> database goes to freeze state all of sudden.
>
> We have been using OrientDb for last 5 years and never faced such a
> situation.
>
> We tried passing timeout argument along with all the read query (with
> timeout as 5000 ms), we reduced record.locktimeout, network level various
> timeout to lower the number, session time out, connection timeout, etc.
> None of them helped. The queries are not timing out. The connection breaks
> and application is getting SocketTimeoutException, but connection/query
> seems to be staying in frozen/lock state in the database side and not
> allowing the new connection.
>
> We tried to kill the connection using Command "Kill", "interrupt", both
> have failed, the command just hangs in waiting to get the response from the
> server for the first connections.
>
>
> We are currently rebuilding the index for the entire database on one go as
> last resort.
>
> We are a startup, built the entire product using OrientDB. Due to this,
> our service is down for the last 5 days and we are losing our customer
> trust and we are having big crisis.
>
> Help us identify the root cause and overcome the issue.
>
> Regards,
> Ram
>
>
>
>
>
>
>
> On Wed, Aug 21, 2019 at 7:36 PM Ram Karthik 
> wrote:
>
>> Hi  Luigi,
>>
>> Thanks for your reply.
>>
>> Database size 40GB
>>
>> Typical workload  - 50 TPS
>>
>> Added Server logs and sample schema below
>> we have around 200+ schema
>>
>> Thanks in advance.
>>
>>
>> On Wed, Aug 21, 2019 at 6:58 PM Luigi Dell'Aquila <
>> luigi.dellaqu...@gmail.com> wrote:
>>
>>> Hi Ram
>>>
>>> It's hard to give you a quick solution with so few information.
>>> V 2.0 is EOL so we will hardly release a community patch, but we can try
>>> to troubleshoot the problem and see if we can work around it.
>>> Can you provide a bit more information, eg. server logs, typical
>>> workload, some information about DB size and schema...
>>>
>>> Thanks
>>>
>>> Lui

Re: [orientdb] Orient DB Server unreachable frequently - Urgent

[Luigi Dell'Aquila]

Hi Ram

It's hard to give you a quick solution with so few information.
V 2.0 is EOL so we will hardly release a community patch, but we can try to
troubleshoot the problem and see if we can work around it.
Can you provide a bit more information, eg. server logs, typical workload,
some information about DB size and schema...

Thanks

Luigi


Il giorno mer 21 ago 2019 alle ore 14:57 Ram Karthik <
ramkarthik.m...@gmail.com> ha scritto:

> We are using OrientDB ver 2.0.18, and we are facing a critical issue for
> the past 5 days. The following issues we are facing
>
>1. Orient DB server is unreachable frequently
>2. We cannot able to shut down the server. We are forced to kill the DB
>3. Sometimes the Index gets crashed.
>
> The above issues occur when we open the traffic to use our application.
>
> This is a very critical issue, many users are unable to use the
> application due to this issue. We depend on the OrientDB, due to this we
> are facing many issues.
>
> Please help us to resolve this issue soon.
>
> Thanks,
> Ram
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/orient-database/80c7ea2d-4214-432a-9679-5e09a4a1cc99%40googlegroups.com
> 
> .
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/orient-database/CAFZLH8kGV%3Di1O1BWhtmSG4YKKXLW4x6DXEu88N%2B55QJf19opkA%40mail.gmail.com.

Re: [orientdb] Automatic daily backups

[Luigi Dell'Aquila]

Hi Tiziano,

If you check orientdb-server-config.xml you'll find the following:









In the Community Edition it is a blocking full bacup, that means that the
DB will be in read-only mode during the backup operation.

In the Enterprise Edition you also have non-blocking and incremental
backup, with a much more user-friendly GUI in Studio to schedule it
https://orientdb.com/orientdb-enterprise/version-3-0/

Thanks

Luigi

Il giorno dom 18 ago 2019 alle ore 11:50 Tiziano Fortin <
tiz.for...@gmail.com> ha scritto:

> Hi guys,
> there is a way for performing ad automatic backup every day without
> stopping the server?
>
> P.s. my ubuntu does not support LVM
>
> thank you
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/orient-database/74547a94-30c2-4544-941d-9331b7a2b6de%40googlegroups.com
> 
> .
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/orient-database/CAFZLH8kxzO3%2BXW8HzXh36AdAkz%3Dyv%3DyT37u1TMXdbgQi3%2B5wnw%40mail.gmail.com.

Re: [orientdb] Query compatibility

[Luigi Dell'Aquila]

Hi Tiziano,

Can you please post a simple dataset to reproduce the problem?

Thanks

Luigi

Il giorno lun 5 ago 2019 alle ore 00:30 Tiziano Fortin 
ha scritto:

> Hey guys please help me...
>
> with orient 2.0.11 I used to run this query with success:
>
> SELECT expand(both('').inE('')[index=0].inV())
> FROM #12:1
>
> now I passed at orient 3.0.22 and the same query return empty (but the
> data is there)
>
> please can you explain me why this don't work anymore? how I can solve?
>
> thank you guys
>
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/orient-database/6a749733-ea23-4237-8d9f-e4926d8dcc95%40googlegroups.com
> 
> .
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/orient-database/CAFZLH8mmAVDsDJytBb3T3a9kq%3DXhsVbZftuO_8XZS1Pnr9KmLQ%40mail.gmail.com.

Re: [orientdb] OrientDB 3 & Tinkerpops

[Luigi Dell'Aquila]

Hi Rafa,

That's exactly the point: TinkerPop has advantages when you use it as a
standard, ie through the Gremlin server, but it's also a sub-optimal
solution both in terms of performance/optimization and in terms of full
control on the DB capabilities (eg. it does not have Document concepts).

If you need full control on the DB and you want to exploit all its
capabilities with the best performance, then you should definitely go with
the Multi-Model API.
On the other hand, if portability and compliance to broader standards is a
must for you, then TinkerPop is definitely a good alternative.

Thanks

Luigi


Il giorno lun 10 giu 2019 alle ore 15:55 Rafael Santodomingo <
rafasantodomi...@gmail.com> ha scritto:

> Many thanks Luigi,
>
> *"If you need to use TinkerPop API for some reason (eg. because you need
> compliance to standards) then I'd suggest to connect to the Gremlin server
> directly, this will guarantee that you are really using it in a standard
> way"*
>
> I'm afraid I didn't quite get that. Do you mean we should use the
> gremlin-server.sh (or .bat) & access the database via the gremlin console
> (as in the examples given in
> http://orientdb.com/docs/3.1.x/tinkerpop3/OrientDB-TinkerPop3.html)?
> But how can we integrate this with our java code if it isn't through the
> OrientDB-TP3 Graph API? Besides we're also using embedded documents, which
> don't comply with the gremlin standard as far as I now.
>
> We've got java "business application" modules that need to access OrientDB
> and we'll prefer to use the Tinkerpops standard as much as we can - as we
> did with OrientDB 2.2.12.
>
> What I understand is that now the main focus is on the Multi-Model API,
> which is the recommended API to access OrientDB via Java as it is more
> complete and optimised, isn't?
>
> Regards,
> Rafa
>
> On Monday, 10 June 2019 08:42:45 UTC+1, Luigi Dell'Aquila wrote:
>>
>> Hi Rafa,
>>
>> Apache TinkerPop is still fully supported, there is a specific OrientDB
>> distribution that includes a Gremlin server and all the TP APIs.
>>
>> The Muti-Model API in v3.0 is a logical step in the direction of making
>> OrientDB API as simple and complete as possible; in previous versions there
>> was no way to manipulate documents and graphs in a consistent manner with a
>> single API, TinkerPop 2.6 did not have natural Document capabilities and
>> the ODatabase API did not have graph concepts, it was definitely not a nice
>> situation for the end-user usability.
>>
>> If you are connecting to OrientDB directly, I'd suggest to use the
>> Multi-Model API, that is more optimised and complete.
>>
>> If you need to use TinkerPop API for some reason (eg. because you need
>> compliance to standards) then I'd suggest to connect to the Gremlin server
>> directly, this will guarantee that you are really using it in a standard way
>>
>> Thanks
>>
>> Luigi
>>
>>
>>
>> Il giorno ven 7 giu 2019 alle ore 14:19 Rafael Santodomingo <
>> rafasant...@gmail.com> ha scritto:
>>
>>> Hi All,
>>>
>>> I just wanted to ask what is the plan re Tinkerpops interface. As
>>> opposed to OrientDB 2, OrientDB 3 does not include Tinkerpops
>>> implementation in the core package. It's true that it does add extra
>>> packages with Tinkerpops 3 implementation (and Tinkerpops 2.6 for backward
>>> compatibility), but my general feeling is that OrientDB is focusing more
>>> now on the Multi-Model API.
>>>
>>> We need to decide which alternative we use (Graph API with Tinkerpops 3
>>> or Multi-Model API). It seems to me that there's more support and
>>> documentation on the Multi-Model API and also that historically is more
>>> aligned with the core OrientDB solution - the Mutli-Model API being an
>>> extension of the original Document API.
>>>
>>> What do you suggest? I like the idea of working with the Tinkerpops
>>> interface, but having carried out some throrough tests with OrientDB 3.0.17
>>> Tinkerpops 3 I'm not sure about its performance and support at all.
>>>
>>> Regards,
>>> Rafa
>>>
>>> --
>>>
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "OrientDB" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to orient-...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/or

Re: [orientdb] OrientDB 3 & Tinkerpops

[Luigi Dell'Aquila]

Hi Rafa,

Apache TinkerPop is still fully supported, there is a specific OrientDB
distribution that includes a Gremlin server and all the TP APIs.

The Muti-Model API in v3.0 is a logical step in the direction of making
OrientDB API as simple and complete as possible; in previous versions there
was no way to manipulate documents and graphs in a consistent manner with a
single API, TinkerPop 2.6 did not have natural Document capabilities and
the ODatabase API did not have graph concepts, it was definitely not a nice
situation for the end-user usability.

If you are connecting to OrientDB directly, I'd suggest to use the
Multi-Model API, that is more optimised and complete.

If you need to use TinkerPop API for some reason (eg. because you need
compliance to standards) then I'd suggest to connect to the Gremlin server
directly, this will guarantee that you are really using it in a standard way

Thanks

Luigi



Il giorno ven 7 giu 2019 alle ore 14:19 Rafael Santodomingo <
rafasantodomi...@gmail.com> ha scritto:

> Hi All,
>
> I just wanted to ask what is the plan re Tinkerpops interface. As opposed
> to OrientDB 2, OrientDB 3 does not include Tinkerpops implementation in the
> core package. It's true that it does add extra packages with Tinkerpops 3
> implementation (and Tinkerpops 2.6 for backward compatibility), but my
> general feeling is that OrientDB is focusing more now on the Multi-Model
> API.
>
> We need to decide which alternative we use (Graph API with Tinkerpops 3 or
> Multi-Model API). It seems to me that there's more support and
> documentation on the Multi-Model API and also that historically is more
> aligned with the core OrientDB solution - the Mutli-Model API being an
> extension of the original Document API.
>
> What do you suggest? I like the idea of working with the Tinkerpops
> interface, but having carried out some throrough tests with OrientDB 3.0.17
> Tinkerpops 3 I'm not sure about its performance and support at all.
>
> Regards,
> Rafa
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/orient-database/2123e025-1069-4754-ae2c-2792bc763904%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/orient-database/CAFZLH8kmRrv_9Cyn0YeA1GNMrdtOgh6JPeqPXoBvyuxrQHXNDw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] OrientDB query to receive last vertex before a given date

[Luigi Dell'Aquila]

Hi Jon,

It seems correct, there is no additional ORDER BY in the execution plan and
the fetch from index is correct, so I'd say the problem is probably related
to the index size or to some caching.
In general, I'd say you can expect the performance to remain more or less
constant around these values

Thanks

Luigi


Il giorno mar 7 mag 2019 alle ore 13:03 'Jon' via OrientDB <
orient-database@googlegroups.com> ha scritto:

> Hi Luigi,
>
> for query:
> SELECT FROM ANYVERTEX WHERE date < 999 ORDER BY date DESC
> LIMIT 3
>
> please find the describe below.
>
> + FETCH FROM INDEX ANYVERTEX.date_targetId
>   date < 999
> + EXTRACT VALUE FROM INDEX ENTRY
>   filtering clusters [95,96,94,97,98,87,75,79,80,77,78,76,91,90,89,88,92,93]
> + FILTER ITEMS BY CLASS
>   ANYVERTEX
> + LIMIT ( LIMIT 3)
>
> Thanks
> Jon
>
>
> On Tuesday, May 7, 2019 at 12:11:52 PM UTC+2, Luigi Dell'Aquila wrote:
>>
>> Hi Jon,
>>
>> Could you please post an EXPLAIN of that query?
>>
>> Thanks
>>
>> Luigi
>>
>> Il giorno mar 7 mag 2019 alle ore 11:23 'Jon' via OrientDB <
>> orient-...@googlegroups.com> ha scritto:
>>
>>>
>>> Hi Luigi,
>>>
>>> thanks for your fast reply. I' am doing performance tests in OrientDB
>>> 3.0.18 locally and 3.0.3 in our test environment. The index type is
>>> UNIQUE(SBTREE). The index is a composite key composed of an id and the
>>> timestamp. From the logs I can definitely confirm that the query above
>>> takes the most of the time (per attached vertex) of all remaining
>>> operations (like attaching edge etc.).  In orient studio if I execute:
>>>
>>> SELECT FROM ANYVERTEX WHERE t < 999 AND id=... ORDER BY t DESC 
>>> LIMIT 1
>>>
>>>
>>> it takes 0.133 sec (which improves with caching) and with
>>>
>>> SELECT FROM ANYVERTEX WHERE t < 1 AND id=... ORDER BY t DESC LIMIT 1
>>>
>>>
>>> only 0.054.
>>>
>>>
>>> On Tuesday, May 7, 2019 at 8:44:54 AM UTC+2, Luigi Dell'Aquila wrote:
>>>
>>>> Hi Jon
>>>>
>>>> Using an index should definitely solve the problem, so it's strange
>>>> that it didn't work in your case.
>>>> Which OrientDB version are you using? And what kind of index did you
>>>> define?
>>>>
>>>> Thanks
>>>>
>>>> Luigi
>>>>
>>>> Il giorno lun 6 mag 2019 alle ore 13:44 'Jon' via OrientDB <
>>>> orient-...@googlegroups.com> ha scritto:
>>>>
>>>>> Let's say I have the following list of vertices (connected by edges)
>>>>> in the orient database:
>>>>>
>>>>>
>>>>>  [t=1] --> [t=2] --> [t=3] --> [t=4] --> [t=5] --> [t=6] --> [t=7]
>>>>>
>>>>>
>>>>> Each vertex has a timestamp t. I now want to receive the last vertex
>>>>> before a given date. Example: give me the last vertex before t=5, which is
>>>>> t=4.
>>>>>
>>>>> Currently I'am using the following query to do this:
>>>>>
>>>>>
>>>>>  SELECT FROM ANYVERTEX WHERE t < 5 ORDER BY t DESC LIMIT 1
>>>>>
>>>>>
>>>>> This is working fine when having up to let's say 1000 elements but the
>>>>> performance of that query drops with the number of elements inserted in 
>>>>> the
>>>>> list. I already tried using an index, which improved the overall
>>>>> performance, but the problem, that the performance drops with the amount 
>>>>> of
>>>>> elements still persists.
>>>>>
>>>>> --
>>>>>
>>>>> ---
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups "OrientDB" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>>> an email to orient-...@googlegroups.com.
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>
>>>> --
>>>
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "OrientDB" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to orient-...@googlegroups

Re: [orientdb] OrientDB query to receive last vertex before a given date

[Luigi Dell'Aquila]

Hi Jon,

Could you please post an EXPLAIN of that query?

Thanks

Luigi

Il giorno mar 7 mag 2019 alle ore 11:23 'Jon' via OrientDB <
orient-database@googlegroups.com> ha scritto:

>
> Hi Luigi,
>
> thanks for your fast reply. I' am doing performance tests in OrientDB
> 3.0.18 locally and 3.0.3 in our test environment. The index type is
> UNIQUE(SBTREE). The index is a composite key composed of an id and the
> timestamp. From the logs I can definitely confirm that the query above
> takes the most of the time (per attached vertex) of all remaining
> operations (like attaching edge etc.).  In orient studio if I execute:
>
> SELECT FROM ANYVERTEX WHERE t < 999 AND id=... ORDER BY t DESC LIMIT 1
>
>
> it takes 0.133 sec (which improves with caching) and with
>
> SELECT FROM ANYVERTEX WHERE t < 1 AND id=... ORDER BY t DESC LIMIT 1
>
>
> only 0.054.
>
>
> On Tuesday, May 7, 2019 at 8:44:54 AM UTC+2, Luigi Dell'Aquila wrote:
>
>> Hi Jon
>>
>> Using an index should definitely solve the problem, so it's strange that
>> it didn't work in your case.
>> Which OrientDB version are you using? And what kind of index did you
>> define?
>>
>> Thanks
>>
>> Luigi
>>
>> Il giorno lun 6 mag 2019 alle ore 13:44 'Jon' via OrientDB <
>> orient-...@googlegroups.com> ha scritto:
>>
>>> Let's say I have the following list of vertices (connected by edges) in
>>> the orient database:
>>>
>>>
>>>  [t=1] --> [t=2] --> [t=3] --> [t=4] --> [t=5] --> [t=6] --> [t=7]
>>>
>>>
>>> Each vertex has a timestamp t. I now want to receive the last vertex
>>> before a given date. Example: give me the last vertex before t=5, which is
>>> t=4.
>>>
>>> Currently I'am using the following query to do this:
>>>
>>>
>>>  SELECT FROM ANYVERTEX WHERE t < 5 ORDER BY t DESC LIMIT 1
>>>
>>>
>>> This is working fine when having up to let's say 1000 elements but the
>>> performance of that query drops with the number of elements inserted in the
>>> list. I already tried using an index, which improved the overall
>>> performance, but the problem, that the performance drops with the amount of
>>> elements still persists.
>>>
>>> --
>>>
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "OrientDB" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to orient-...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/orient-database/05b6c195-9738-41fd-bf63-487336da4041%40googlegroups.com
> <https://groups.google.com/d/msgid/orient-database/05b6c195-9738-41fd-bf63-487336da4041%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/orient-database/CAFZLH8nxMH0v7O7Q6ybBjqKMB-k48SKRauFSBbVhm92c4pgLSg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] OrientDB query to receive last vertex before a given date

[Luigi Dell'Aquila]

Hi Jon

Using an index should definitely solve the problem, so it's strange that it
didn't work in your case.
Which OrientDB version are you using? And what kind of index did you define?

Thanks

Luigi

Il giorno lun 6 mag 2019 alle ore 13:44 'Jon' via OrientDB <
orient-database@googlegroups.com> ha scritto:

> Let's say I have the following list of vertices (connected by edges) in
> the orient database:
>
>
>  [t=1] --> [t=2] --> [t=3] --> [t=4] --> [t=5] --> [t=6] --> [t=7]
>
>
> Each vertex has a timestamp t. I now want to receive the last vertex
> before a given date. Example: give me the last vertex before t=5, which is
> t=4.
>
> Currently I'am using the following query to do this:
>
>
>  SELECT FROM ANYVERTEX WHERE t < 5 ORDER BY t DESC LIMIT 1
>
>
> This is working fine when having up to let's say 1000 elements but the
> performance of that query drops with the number of elements inserted in the
> list. I already tried using an index, which improved the overall
> performance, but the problem, that the performance drops with the amount of
> elements still persists.
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/orient-database/CAFZLH8kJT%2BnJZ0Uq1NnmyHfAPjuzc3%3DK0fmGOoNmg6pAwSo7%3Dg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] Orientdb 2.0.18 automattically stopped

[Luigi Dell'Aquila]

Hi Ram,

OrientDB v 2.0 is not supported anymore, I strongly suggest you to upgrade
to latest version.
About the specific problem, do you have any error in the logs? It could
also be the OS who stopped the process because of low system resources, in
this case you won't see any errors, but OrientDB cannot do much for this...

Thanks

Luigi


Il giorno lun 18 mar 2019 alle ore 13:12 Ram Karthik <
ramkarthik.m...@gmail.com> ha scritto:

> Hi,
>
>We are using orientdb 2.0.18 version. The
> orientdb automatically stopped please give me an idea of preventing this
> and do not increase CPU. but why it stopped?
>
> Please help me it's urgent.
>
>
> Thanks,
>   Ram
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] Is this concat possible?

[Luigi Dell'Aquila]

SELECT
DriverID, DriverName, list(CarCost)
FROM ( ... )
GROUP BY  DriverID, DriverName

Il giorno gio 7 mar 2019 alle ore 12:27 Luigi Dell'Aquila <
luigi.dellaqu...@gmail.com> ha scritto:

> oh, sorry, I didn't scroll the screen :D
>
> You have to use a set() or list() aggregation on CarCost and do a GROUP BY
> on the other columns
>
> Thanks
>
> Luigi
>
> Il giorno gio 7 mar 2019 alle ore 12:26 Luigi Dell'Aquila <
> luigi.dellaqu...@gmail.com> ha scritto:
>
>> Hi Michael,
>>
>> Just add a DISTINCT to the RETURN, ie
>>
>> RETURN DISTINCT driver.@rid AS DriverID, driver.name AS DriverName,
>> car.cost AS CarCost
>>
>> Thanks
>>
>> Luigi
>>
>> Il giorno mer 6 mar 2019 alle ore 22:46 Michael Faughn <
>> m.fau...@prometheuscomputing.com> ha scritto:
>>
>>> SELECT * FROM (MATCH {Class: Person, as: driver, where:(name='Bob')}-
>>> Driving->{Class: Vehicle, as:car} RETURN driver.@rid AS DriverID, driver
>>> .name AS DriverName, car.cost AS CarCost)
>>>
>>> results in the following:
>>>
>>> DriverID
>>> DriverName
>>> CarCost
>>> #332:0
>>> <http://localhost:2480/studio/index.html#/database/test/browse/edit/332:0>
>>> Bob
>>> 222
>>> #332:0
>>> <http://localhost:2480/studio/index.html#/database/test/browse/edit/332:0>
>>> Bob
>>> 111
>>>
>>> I would instead like the following:
>>>
>>> DriverID
>>> DriverName
>>> CarCost
>>> #332:0
>>> <http://localhost:2480/studio/index.html#/database/test/browse/edit/332:0>
>>> Bob
>>> [222, 111]
>>>
>>> Is there a way to write the query so that this can happen?
>>>
>>> --
>>>
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "OrientDB" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to orient-database+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] Is this concat possible?

[Luigi Dell'Aquila]

oh, sorry, I didn't scroll the screen :D

You have to use a set() or list() aggregation on CarCost and do a GROUP BY
on the other columns

Thanks

Luigi

Il giorno gio 7 mar 2019 alle ore 12:26 Luigi Dell'Aquila <
luigi.dellaqu...@gmail.com> ha scritto:

> Hi Michael,
>
> Just add a DISTINCT to the RETURN, ie
>
> RETURN DISTINCT driver.@rid AS DriverID, driver.name AS DriverName,
> car.cost AS CarCost
>
> Thanks
>
> Luigi
>
> Il giorno mer 6 mar 2019 alle ore 22:46 Michael Faughn <
> m.fau...@prometheuscomputing.com> ha scritto:
>
>> SELECT * FROM (MATCH {Class: Person, as: driver, where:(name='Bob')}-
>> Driving->{Class: Vehicle, as:car} RETURN driver.@rid AS DriverID, driver.name
>> AS DriverName, car.cost AS CarCost)
>>
>> results in the following:
>>
>> DriverID
>> DriverName
>> CarCost
>> #332:0
>> <http://localhost:2480/studio/index.html#/database/test/browse/edit/332:0>
>> Bob
>> 222
>> #332:0
>> <http://localhost:2480/studio/index.html#/database/test/browse/edit/332:0>
>> Bob
>> 111
>>
>> I would instead like the following:
>>
>> DriverID
>> DriverName
>> CarCost
>> #332:0
>> <http://localhost:2480/studio/index.html#/database/test/browse/edit/332:0>
>> Bob
>> [222, 111]
>>
>> Is there a way to write the query so that this can happen?
>>
>> --
>>
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "OrientDB" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to orient-database+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] Is this concat possible?

[Luigi Dell'Aquila]

Hi Michael,

Just add a DISTINCT to the RETURN, ie

RETURN DISTINCT driver.@rid AS DriverID, driver.name AS DriverName,
car.cost AS CarCost

Thanks

Luigi

Il giorno mer 6 mar 2019 alle ore 22:46 Michael Faughn <
m.fau...@prometheuscomputing.com> ha scritto:

> SELECT * FROM (MATCH {Class: Person, as: driver, where:(name='Bob')}-
> Driving->{Class: Vehicle, as:car} RETURN driver.@rid AS DriverID, driver.name
> AS DriverName, car.cost AS CarCost)
>
> results in the following:
>
> DriverID
> DriverName
> CarCost
> #332:0
> 
> Bob
> 222
> #332:0
> 
> Bob
> 111
>
> I would instead like the following:
>
> DriverID
> DriverName
> CarCost
> #332:0
> 
> Bob
> [222, 111]
>
> Is there a way to write the query so that this can happen?
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] Properties typed as an interface?

[Luigi Dell'Aquila]

Hi Michael,

OrientDB supports multiple inheritance, so it's not a problem ;-)

Thanks

Luigi


Il giorno mar 26 feb 2019 alle ore 17:01 Michael Faughn <
m.fau...@prometheuscomputing.com> ha scritto:

> Thanks Luigi.  Creating an abstract class to represent an interface won't
> work*.  If you did this then the interface implementers would have to
> inherit from the interface class, which it turn would mean they could not
> inherit from any erstwhile superclasses.  Reference the small class diagram
> image I included earlier.  If Zapper where made a class then, in order to
> create an edge between an instance of Foo and an instance of Baz, class Baz
> would have to inherit from class Zapper.  This is not possible if class Baz
> already inherits from class Bar.
>
> For now I'm substituting all interfaces with class V and implementing
> additional type checking in the application layer.  I'm still really
> excited to finally be given the go ahead to try to replace our use of RDBMS
> with OrientDB and I'm forging ahead.
>
> * Note -- I'm entirely wrong about this if OrientDB supports multiple
> inheritance.  I can't find any indication that it does.  Please let me know
> if I'm wrong because it will make things much easier for me.
>
> It would be really nice to have ability to have the storage model (i.e.
> OrientDB) more closely represent the classifiers used to implement a
> problem domain in the application layer.  While I'm not a fan of multiple
> inheritance for classes, interfaces are a very good idea and multiple
> inheritance for interfaces (i.e. interfaces can extend multiple interfaces)
> is quite acceptable.  This is quite normal in Java (and lots of other
> languages).  Consider this a feature request ;-)
>
> Thanks,
> Michael
>
>
>
> On Tuesday, February 26, 2019 at 2:27:58 AM UTC-5, Luigi Dell'Aquila wrote:
>>
>> Hi Michael,
>>
>> OrientDB does not have a concept for interfaces, but you can use abstract
>> classes and make them extends V (so that you can then create edges between
>> them)
>>
>> I hope it helps
>>
>> Thanks
>>
>> Luigi
>>
>> Il giorno lun 25 feb 2019 alle ore 16:17 Michael Faughn <
>> m.fa...@prometheuscomputing.com> ha scritto:
>>
>>> I'm having a go at implementing an OGM for Ruby.  More precisely, an OGM
>>> that is driven by UML class diagrams.  Is there a good way to handle
>>> properties that are typed as interfaces?
>>>
>>> Referencing the image below, how can I create a property for class Foo
>>> that is typed as a link to a Zapper?  How can I create an edge to a Zapper?
>>>
>>>
>>>
>>>
>>>
>>> [image: orient_iface_example.jpg]
>>>
>>> --
>>>
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "OrientDB" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to orient-databa...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] Properties typed as an interface?

[Luigi Dell'Aquila]

Hi Michael,

OrientDB does not have a concept for interfaces, but you can use abstract
classes and make them extends V (so that you can then create edges between
them)

I hope it helps

Thanks

Luigi

Il giorno lun 25 feb 2019 alle ore 16:17 Michael Faughn <
m.fau...@prometheuscomputing.com> ha scritto:

> I'm having a go at implementing an OGM for Ruby.  More precisely, an OGM
> that is driven by UML class diagrams.  Is there a good way to handle
> properties that are typed as interfaces?
>
> Referencing the image below, how can I create a property for class Foo
> that is typed as a link to a Zapper?  How can I create an edge to a Zapper?
>
>
>
>
>
> [image: orient_iface_example.jpg]
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] Gremlin vs SQL?

[Luigi Dell'Aquila]

Hi Michael,

As an OrientDB maintainer, I can tell you that SQL is much more optimized
than Gremlin, so if you need good performance I strongly suggest you to use
SQL.
Tinkerpop (and Gremlin) is intended to be a standard, so it allows easier
migration from a product to another; this said, TinkerPop also has slightly
different extensions on different products, so the migration still requires
some effort.

Thanks

Luigi

Il giorno gio 14 feb 2019 alle ore 23:31 Michael Faughn <
m.fau...@prometheuscomputing.com> ha scritto:

> I'm trying to determine the feasibility of switching to a graph database
> for my company's toolchain.  I've already mostly settled on OrientDB as the
> most likely candidate.  We would likely be looking at writing a Ruby OGM
> for OrientDB if we do move forward*.  I'm looking for an analysis of the
> pros and cons of SQL and Gremlin. My conclusions so far are rudimentary and
> amount to, 1) Gremlin is more universal, 2) SQL looks more facile and easy
> to get going with.  Any links to articles or blogs or forum posts would be
> most welcome.  Leaving an opinion here would be great too.
>
>
> * Note -- I'm aware of Active-Orient.  Having looked at it, I doubt we
> would want to go with that.
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] RAM Usgae

[Luigi Dell'Aquila]

Hi,

Which OrientDB version are you referring to?

Thanks

Luigi

Il giorno ven 14 dic 2018 alle ore 09:53 Praveenkumar K <
krishmi...@gmail.com> ha scritto:

> Hi All,
>
>  OrientDB consume high RAM usage while inset and select query
> execute concurrently.
>
> How I can resolve this?
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] kill select query

[Luigi Dell'Aquila]

Hi Praveenkumar,

How are you running the query? From Studio? Which OrientDB version?

Thanks

Luigi

Il giorno mer 12 dic 2018 alle ore 11:38 Praveenkumar K <
krishmi...@gmail.com> ha scritto:

> Hi,
>
>  How I can stop or kill long running query in OrientDB?
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] Indexed queries on 2.2.26

[Luigi Dell'Aquila]

Hi Erik,

Let's say that there are possible work-arounds. In particular, instead of
using LIKE operator, you can use LUCENE or FULLTEXT indexes.

Thanks

Luigi

Il giorno mar 11 dic 2018 alle ore 13:45 Erik T  ha
scritto:

> I'm unable to upgrade to v3 at this point some I'm stuck trying to figure
> out what actually happens in the lower levels.
>
> Are there exceptions to the rules you gave?
> Erik
>
>
> On Tue, Dec 11, 2018 at 2:46 AM Luigi Dell'Aquila <
> luigi.dellaqu...@gmail.com> wrote:
>
>> Hi Erik,
>>
>> In general:
>> - queries with NOT are not indexed
>> - LIKE operator cannot be used with indexes in general
>> - AND operations can be indexed if you have a multi-property index, but
>> not on multiple indexes on the same query
>> - the new SQL executor in v 3.0 is much smarter at query optimization and
>> index usage, so if you have a chance to upgrade I strongly suggest you to
>> do so
>>
>> Thanks
>>
>> Luigi
>>
>> Il giorno lun 10 dic 2018 alle ore 20:38 Erik T 
>> ha scritto:
>>
>>> I'm trying to create some indexed queries and I want to make sure I
>>> understand the documentation. What happens when an AND or OR is used with
>>> NOT or LIKE? Does the NOT force the whole query to avoid an index? Does a
>>> LIKE force the index to need a ranged query for everything?
>>>
>>> --
>>>
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "OrientDB" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to orient-database+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
>>
>> ---
>> You received this message because you are subscribed to a topic in the
>> Google Groups "OrientDB" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/orient-database/LWH9pAlhWJs/unsubscribe
>> .
>> To unsubscribe from this group and all its topics, send an email to
>> orient-database+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] Export single class

[Luigi Dell'Aquila]

Hi,

You can use -includeClass option in EXPORT DATABASE, see
https://orientdb.com/docs/3.0.x/console/Console-Command-Export.html

Thanks

Luigi

Il giorno mar 11 dic 2018 alle ore 13:47 Praveenkumar K <
krishmi...@gmail.com> ha scritto:

> Hi All,
>
> How to export single class from OrientDB? Kindly explain If
> anybody have exploring
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] Indexed queries on 2.2.26

[Luigi Dell'Aquila]

Hi Erik,

In general:
- queries with NOT are not indexed
- LIKE operator cannot be used with indexes in general
- AND operations can be indexed if you have a multi-property index, but not
on multiple indexes on the same query
- the new SQL executor in v 3.0 is much smarter at query optimization and
index usage, so if you have a chance to upgrade I strongly suggest you to
do so

Thanks

Luigi

Il giorno lun 10 dic 2018 alle ore 20:38 Erik T  ha
scritto:

> I'm trying to create some indexed queries and I want to make sure I
> understand the documentation. What happens when an AND or OR is used with
> NOT or LIKE? Does the NOT force the whole query to avoid an index? Does a
> LIKE force the index to need a ranged query for everything?
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] Create relationship between vertex

[Luigi Dell'Aquila]

Hi,

What do you mean exactly?
You can use a

CREATE EDGE XXX FROM (SELECT FROM V WHERE )
TO (SELECT FROM V WHERE )

the conditions can match multiple vertices, so multiple edges will be
created.

If you need a manual iteration, you can use WHILE and FOREACH loops in
batch scripts https://orientdb.com/docs/3.0.x/sql/SQL-batch.html#loops

I hope it helps

Thanks

Luigi

Il giorno ven 7 dic 2018 alle ore 10:18 axon musthaq 
ha scritto:

> I have two vertex
>
> A and B
>
> I didn't  create relationship while inserting values in respective vertex.
>
>
> Now i want to create relationship between two vertex A and B which has
> thousand of rows.
>
> For that i need to create edge as loop.
>
>
> How can i do that in orientdb query without using java/api
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] Issues with using while and where in a match clause

[Luigi Dell'Aquila]

Hi Petra,

First of all, are you using v 2.2. or v 3.0?

Thanks

Luigi


Il giorno mer 5 dic 2018 alle ore 20:33 Petra Geigenfeind <
petra.geigenfe...@gmail.com> ha scritto:

> Hello everybody,
>
> I've built a litte social network based on some characters from the
> Simpsons. There's Lisa, Bart, Maggie, Homer, Marge and their grandparents
> Abe and Jackie. I set up the characters as nodes in the graph, they have
> tha class "figure", there a differnt types of edges for each kind of
> relationship, in thes example it is the edge class "parent". Marge and
> Homer are parents of Lisa, Bart and Maggie. Abe is the parent of Homer and
> Jackie the parent of Marge. So all together we get a little family tree.
>
> Now I want to find out who Lisa's grandparents are. So I'm matching Lisa
> and two traversals of the parent type in reverse direction or if you want
> so I'm looking for the parents of Lisa's parents.
>
> Works fine using this syntax:
>
> MATCH {class:figure, as: lisa, where: (name= "Lisa Simpson")}
> .in("parent"){class: figure}
> .in("parent"){class: figure, as: person}
> RETURN person.name
>
> But now if I try with just one Edge definded and using the while condition
> to loop traversals I get:
>
> MATCH {class:figure, as: lisa, where: (name= "Lisa Simpson")}
> .in("parent"){class: figure, as: person, while: ($matched.depth < 2),
> where:(matched.depth != 0 AND $matched.depth != 1) }
> RETURN person.name
>
> If I get it right how this works, Lisa is at depth level 0 as initial
> node, her parents have to be at level 1 and her grandparents at level 2.
>
> The while condition seems to work like a do while loop. I figured this out
> by quering Lisas parents using "$matched.depth < 1" and it still return
> Lisa and her parents and not just Lisa. So $matched.depth < 2 should be
> fine.
>
> In the where clause I have to write "matched.depth != 0 AND $matched.depth
> != 1" because it doesn't return anything if I write "$matched.depth == 2"
> or "$matched.depth > 1" and I don't get why. Does anyone know why?
>
> Also returning the depth of each ancestor using $depth in the return
> statement doesn't work. It gets me a depth of 2 for all. Am I missing
> anything or what is this behaviour?
>
> Another thing I still don't clearly get is the difference between matched
> and currentMatch. Using matched.depth, currentMatch.depth or depth gets me
> the same results.
>
> Thank you!
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] select query in graph database

[Luigi Dell'Aquila]

Hi John,

You have a few alternatives here:

the easiest one:

SELECT unionAll($a, $b)
LET
$a = (SELECT expand(out("provides")) FROM Employee WHERE name =
:employeeName),
$b = (SELECT expand(out("belongs_to").out("provides")) FROM Employee WHERE
name = :employeeName)

With a TRAVERSE (it will also traverse hierarchies, in case a company
belongs to another company and so on...)

SELECT FROM (
   TRAVERSE out("provides", "belongs_to") FROM (
   SELECT FROM Employee WHERE name = :employeeName
   )
WHERE @class = 'Insurance'


I hope it helps

Thanks

Luigi

Il giorno mer 5 dic 2018 alle ore 09:05 axon musthaq 
ha scritto:

>
> 1.I have a vertex class employee which contain employee_details
> 2.I have a vertex class organization which contain organization_details
> 3.I have a vertex class insurance which contain insurance_details
>
> following are the relationship
>
> employee-out('belongs_to')->organization-out('provides')->insurance
>
> eg:sam-out('belongs_to')->'XXX'-out('provides')->medical
>
> but some employee have direct relationship with insurance class without
> organization
>
> employee-out('provides')->insurance
>
> eg:john-out('provides')->health
>
> i need to write a query to show employee with their insurance irrespective
> of organization
>
> output:
>
> EmployeeName   Organization  Insurance
>
> sam   XXX medical
> johnhealth
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] how to unwind multiple collection

[Luigi Dell'Aquila]

I'm not sure you can do it, just because there is no deterministic way to
do it.
It is not even guaranteed that the second and third collection have the
same number of items, so in general it is not a consistent operation.
Perhaps you can consider to review your domain?

Thanks

Luigi

Il giorno sab 17 nov 2018 alle ore 16:25 axon musthaq 
ha scritto:

>
> my query returns rows of the form:
>
> node | {node1, node2, node3} | {float1, float2, float3}
>
> i would like to unwind the two collections which always have the same
> number of elements, so that i will get rows of the form:
>
> node | node1 | float1
> node | node2 | float2
> node | node3 | float3
>
> i tried to unwind both collections but that will return all permutations
> of the elements, so in this case 9 rows.
>
> is there a simple way to achieve this using orientdb?
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] InvolvedIndex issue when executing Explain query

[Luigi Dell'Aquila]

Hi

I'm not sure I got the point, could you please provide a full SQL script to
reproduce the problem?

Thanks

Luigi

Il giorno sab 17 nov 2018 alle ore 06:29 axon musthaq 
ha scritto:

> i have created several indexes in an vertex class
>
> example
>
> VERTEX
> 1.employee as an index firstname
> 2.class employee_details as an index company
>
> EDGE
>
> employee_belongs_company
>
> i wrote a query
>
> select firstname,out('employee_belongs_company').company from employee
>
> when i execute above query through
>
> Explain
>
> it does not contain any involved_index property.
>
> kindly suggest how to add involved_indexes if there is no index
>
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] Remove special character from the attribute

[Luigi Dell'Aquila]

Hi

You can use replace() method:

SELECT ip.replace(".", "") FROM V

Thanks

Luigi

Il giorno ven 16 nov 2018 alle ore 19:50 axon musthaq 
ha scritto:

> I have an property called ip in an vertex class
> example
>
> ip:127.0.0.1 i need get the value as 127001 by removing dot(.) special
> character
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] Match Two Vertex Class without creating edge

[Luigi Dell'Aquila]

Hi,

Are you talking about some kind of JOIN operation without edges?
OrientDB is a graph database and is explicitly designed to avoid such kind
of operations.
What is the purpose of using a graph database if you don't want to use edge?

Thanks

Luigi


Il giorno gio 15 nov 2018 alle ore 15:01 axon musthaq 
ha scritto:

> I have two vertex class say example Employee and EmployeeDetails. In
> Employee class Following below are the properties 1.FirstName 2.LastName
>
> In EmployeeDetails class Following below are the properties
> 1.FirstName(same value as in Employee class) 2.OrganizationName 3.Salary
> 4.Department
>
> I want to retrieve data like FirstName(Employee class) LastName(Employee
> class) OrganizationName (EmployeeDetails class) Salary(EmployeeDetails
> class) Department(EmployeeDetails class)
>
> without creating any EDGE between (Employee class) and (EmployeeDetails
> class) i want generate report like above.is that possible in orientdb?
>
> please reply if you need any further clarification.
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] OutOfMemoryError

[Luigi Dell'Aquila]

That's pretty strange, I cannot exclude it's a bug.
The first thing I can suggest is to upgrade to v 2.2.37 (or plan a
migration to 3.0), that has a lot of fixes compared to 2.2.30 and has a
more fine grained memory management.
Then, if you have a chance to share some logs from the server, probably we
can find some more information about this problem

Thanks

Luigi

Il giorno ven 26 ott 2018 alle ore 11:46 C L  ha
scritto:

> I use the version 2.2.30
> And I don't think it comes from the query because it happens on multiple
> projects and they don't have much data.
>
> Le vendredi 26 octobre 2018 11:17:18 UTC+2, Luigi Dell'Aquila a écrit :
>>
>> Hi,
>>
>> Which OrientDB version are you using? Perhaps your dataset is now bigger
>> and the query is returning a bigger result set?
>>
>> Thanks
>>
>> Luigi
>>
>> Il giorno ven 26 ott 2018 alle ore 11:10 C L  ha
>> scritto:
>>
>>> Hello,
>>> Recently a new problem appeared on my server :
>>>
>>> com.orientechnologies.orient.core.exception.OJVMErrorException: JVM
>>> error 'OutOfMemoryError : Java heap space' occurred during data processing,
>>> storage is switched to 'read-only' mode. To prevent this exception please
>>> restart the JVM and check data consistency by calling of 'check database'
>>> command from database console. DB name="taxi"
>>>
>>> It perfectly worked for months and now I have this, but I didn't change
>>> anything, the queries are the same.
>>> I tried restarted the database but the error is still happening.
>>>
>>> Any idea on how to fix that ?
>>>
>>> --
>>>
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "OrientDB" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to orient-databa...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] OutOfMemoryError

[Luigi Dell'Aquila]

Hi,

Which OrientDB version are you using? Perhaps your dataset is now bigger
and the query is returning a bigger result set?

Thanks

Luigi

Il giorno ven 26 ott 2018 alle ore 11:10 C L  ha
scritto:

> Hello,
> Recently a new problem appeared on my server :
>
> com.orientechnologies.orient.core.exception.OJVMErrorException: JVM error
> 'OutOfMemoryError : Java heap space' occurred during data processing,
> storage is switched to 'read-only' mode. To prevent this exception please
> restart the JVM and check data consistency by calling of 'check database'
> command from database console. DB name="taxi"
>
> It perfectly worked for months and now I have this, but I didn't change
> anything, the queries are the same.
> I tried restarted the database but the error is still happening.
>
> Any idea on how to fix that ?
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] Installation

[Luigi Dell'Aquila]

Hi Rony,

I think this problem is related to Java itself, not to OrientDB.
See
https://stackoverflow.com/questions/22489398/unsupported-major-minor-version-52-0

Thanks

Luigi

Il giorno ven 19 ott 2018 alle ore 19:18 Rony Armon 
ha scritto:

> Hello, I'm trying to install the server on my Mac (High Sierra, Version
> 10.13.3) after downloading Java ( Version 8 Update 191) but I'm getting
> "Unsupported major.minor version 52.0" error.  Can anyone help with this
> issue?
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] Dynamic record fieled update on every update of that record data.

[Luigi Dell'Aquila]

Hi Peter,

I just answered here
https://github.com/orientechnologies/orientdb/issues/8596

Thanks

Luigi

Il giorno gio 11 ott 2018 alle ore 23:00 Peter V  ha
scritto:

>
> I just need to update the timestamp field every time somebody update the
> data in record. Does anyone know how to do this please ? Thanks.
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] OrientDB3.0.2 create embeddedList via console or Java results into incompatible type

[Luigi Dell'Aquila]

Hi David,

Is it in latest 3.0.8? I tried the query in Studio and it seems to work fine

Thanks

Luigi

Il giorno lun 8 ott 2018 alle ore 04:25  ha
scritto:

> When executing a query just like the one below, but on a Document class
> rather than a vertex class, using the JSON list bracket notation results in
> the following error:
>
> *orientdb {db=foo}> insert into inspection_reports set extension="pdf",
> filehash="somehash", notes=[{"@type":"d", "content":"some content",
> "date":"datestring"}]*
> *Error: com.orientechnologies.orient.core.sql.OCommandSQLParsingException:
> Error parsing query:*
> *insert into inspection_reports set extension="pdf", filehash="somehash",
> notes=[{"@class":"note", "@type":"d", "content":"some content",
> "date":"datestring"}*
>
> *Encountered " "[" "[ "" at line 1, column 80.*
>
> This is from the console while attached to remote:localhost. *notes *is
> an *embeddedlist *type within *inspection_reports*
>
> I've tried more than a few permutations of @class, @type, with brackets,
> without brackets. Any got any pointers?
>
> On Wednesday, July 11, 2018 at 2:32:08 AM UTC-4, Luigi Dell'Aquila wrote:
>>
>> Hi,
>>
>> When you have an embedded list property, you have to pass a list to make
>> it work. You are passing a single document now.
>> Please try the following:
>>
>> CREATE VERTEX Profile SET name = "John", phone = [{ "@type":"d", "number"
>> : "212" }]
>>
>> Thanks
>>
>> Luigi
>>
>>
>> Il giorno mer 11 lug 2018 alle ore 06:17 Paarek  ha
>> scritto:
>>
>>>
>>> Hi! I am using OrientDB3.0.2 and need to use embeddedList
>>> (or embeddedSet)
>>>
>>> I tried following but does not work, not sure why. Any help is much
>>> appreciated.
>>>
>>> --
>>> Schema:
>>> create class Phone EXTENDS V
>>> create property Phone.number String
>>>
>>> create class Profile EXTENDS V
>>> create property Profile.name String
>>> create property Profile.phone embeddedList Phone
>>>
>>> --
>>> CREATE VERTEX Profile CONTENT { "name" : "John", "phone" : {"@type":"d",
>>> "number" : "212" }}
>>> CREATE VERTEX Profile SET name = "John", phone = { "@type":"d", "number"
>>> : "212" }
>>> INSERT INTO Profile (name, phone) VALUES ("John", { "@type": "d",
>>> "number": "212", "@version": 0 })
>>>
>>> Results In:
>>>
>>> Error: com.orientechnologies.orient.core.exception.OValidationException:
>>> The field 'Profile.phone' has been declared as EMBEDDEDLIST but an
>>> incompatible type is used. Value: 212
>>>
>>>
>>>
>>> -- But following Works because profile has no address property --
>>>
>>> INSERT INTO Profile (name, address) VALUES ('John', { "@type": "d",
>>> "number": "212", "@version": 0 })
>>>
>>> --
>>>
>>> I tried the same with Java but also getting exception as follows:
>>>
>>>
>>> com.orientechnologies.orient.core.exception.OValidationException: The
>>> field 'Profile.phone' has been declared as EMBEDDEDLIST but an incompatible
>>> type is used.
>>> at
>>> com.orientechnologies.orient.core.record.impl.ODocument.validateEmbedded(ODocument.java:814)
>>> at
>>> com.orientechnologies.orient.core.record.impl.ODocument.validateField(ODocument.java:601)
>>> at
>>> com.orientechnologies.orient.core.record.impl.ODocument.validate(ODocument.java:2364)
>>> at
>>> com.orientechnologies.orient.core.db.document.ODatabaseDocumentAbstract.saveInternal(ODatabaseDocumentAbstract.java:2039)
>>> at
>>> com.orientechnologies.orient.core.db.document.ODatabaseDocumentAbstract.save(ODatabaseDocumentAbstract.java:2019)
>>> at
>>> com.orientechnologies.orient.core.db.document.ODatabaseDocumentAbstract.save(ODatabaseDocumentAbstract.java:84)
>>> at
>>> com.orientechnologies.orient.core.record.impl.ODocument.save(ODocument.java:2108)
>>> at
>>> com.orientechnologies.orient.core.record.impl.ODocument.save(ODocument.java:2099)
>>> at
>>> com.orientechnologies.orient.core.record.impl.ODocument.save(ODocument.java:63)
>>> at
>>> com.sqad.repository.OrientDBOperationsImpl.updateVertexProperty(OrientDBOperationsImpl.java:330)
>>>
>>> --
>>>
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "OrientDB" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to orient-databa...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] Deserialization issue (InvalidClassException) during communication with remote storage

[Luigi Dell'Aquila]

Hi Simon,

Ok, so it must be a bug. Could you please file an issue here
https://github.com/orientechnologies/orientdb/issues

Thanks

Luigi

Il giorno ven 14 set 2018 alle ore 09:28 'Simon Erhardt' via OrientDB <
orient-database@googlegroups.com> ha scritto:

> Hi Luigi,
>
> yes, although we use the remote protocol, client and server are run in the
> same process. Our classpath contains the following libraries:
>
> orientdb-client-2.2.34.jar
> orientdb-core-2.2.34.jar
> orientdb-graphdb-2.2.34.jar
> orientdb-server-2.2.34.jar
> orientdb-tools-2.2.34.jar
>
> Simon
>
> Am Fr., 14. Sep. 2018 um 07:47 Uhr schrieb Luigi Dell'Aquila <
> luigi.dellaqu...@gmail.com>:
>
>> Hi Simon,
>>
>> Are you using the exact same OrientDB version on both the client and the
>> server?
>>
>> Thanks
>>
>> Luigi
>>
>> Il giorno gio 13 set 2018 alle ore 14:16 'Simon Erhardt' via OrientDB <
>> orient-database@googlegroups.com> ha scritto:
>>
>>> Hello community,
>>>
>>> we are using OrientDB in our product, and since the update from version
>>> 2.1.15 to version 2.2.34, we have the problem described below, which occurs
>>> sporadically.
>>> Is there anything we can do to mitigate it or to identify the actual
>>> error source?
>>> We are grateful for every kind of help.
>>>
>>> - Simon
>>>
>>> *OrientDB release?*
>>> 2.2.34
>>>
>>> *What steps will reproduce the problem?*
>>> Unknown - our attempts to reproduce the problem have been very
>>> unsatisfying yet. Nonetheless, the problem occurs again and again (without
>>> a recognizable pattern), in different runtime environments of different
>>> customers, and in different situations. It seems to happen in random
>>> situations when the database is accessed. It happens that one query is
>>> successful, and the next one fails (with the error below), and then every
>>> subsequent query also fails.
>>>
>>> Symptoms:
>>> An InvalidClassException occurs sometimes when querying the database:
>>> Caused by: com.orientechnologies.common.io.OIOException: com.o;
>>> serializable and externalizable flags conflict
>>> at
>>> com.orientechnologies.orient.client.remote.OStorageRemote.handleIOException(OStorageRemote.java:321)
>>> at
>>> com.orientechnologies.orient.client.remote.OStorageRemote.baseNetworkOperation(OStorageRemote.java:292)
>>> at
>>> com.orientechnologies.orient.client.remote.OStorageRemote.networkOperationRetry(OStorageRemote.java:204)
>>> at
>>> com.orientechnologies.orient.client.remote.OStorageRemote.networkOperation(OStorageRemote.java:215)
>>> at
>>> com.orientechnologies.orient.client.remote.OStorageRemote.command(OStorageRemote.java:1187)
>>> at
>>> com.orientechnologies.orient.core.command.OCommandRequestTextAbstract.execute(OCommandRequestTextAbstract.java:69)
>>> at
>>> com.tinkerpop.blueprints.impls.orient.OrientGraphCommand.execute(OrientGraphCommand.java:49)
>>> at com.mycompany.BaseDAOImpl.query(OrientConnection.java:188)
>>> ... 13 common frames omitted
>>> Caused by: java.io.InvalidClassException: com.o; serializable and
>>> externalizable flags conflict
>>> at java.base/java.io.ObjectStreamClass.readNonProxy(Unknown Source)
>>> at java.base/java.io.ObjectInputStream.readClassDescriptor(Unknown
>>> Source)
>>> at java.base/java.io.ObjectInputStream.readNonProxyDesc(Unknown Source)
>>> at java.base/java.io.ObjectInputStream.readClassDesc(Unknown Source)
>>> at java.base/java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
>>> at java.base/java.io.ObjectInputStream.readObject0(Unknown Source)
>>> at java.base/java.io.ObjectInputStream.readObject(Unknown Source)
>>> at
>>> com.orientechnologies.orient.client.binary.OChannelBinaryAsynchClient.throwSerializedException(OChannelBinaryAsynchClient.java:436)
>>> at
>>> com.orientechnologies.orient.client.binary.OChannelBinaryAsynchClient.handleStatus(OChannelBinaryAsynchClient.java:400)
>>> at
>>> com.orientechnologies.orient.client.binary.OChannelBinaryAsynchClient.beginResponse(OChannelBinaryAsynchClient.java:283)
>>> at
>>> com.orientechnologies.orient.client.binary.OChannelBinaryAsynchClient.beginResponse(OChannelBinaryAsynchClient.java:167)
>>> at
>>> com.orientechnologies.orient.client.remote.OStorageRemote.beginResponse(OStorageRemote.java:2365)
>>> at
>>> com.orientechnologie

Re: [orientdb] Deserialization issue (InvalidClassException) during communication with remote storage

[Luigi Dell'Aquila]

Hi Simon,

Are you using the exact same OrientDB version on both the client and the
server?

Thanks

Luigi

Il giorno gio 13 set 2018 alle ore 14:16 'Simon Erhardt' via OrientDB <
orient-database@googlegroups.com> ha scritto:

> Hello community,
>
> we are using OrientDB in our product, and since the update from version
> 2.1.15 to version 2.2.34, we have the problem described below, which occurs
> sporadically.
> Is there anything we can do to mitigate it or to identify the actual error
> source?
> We are grateful for every kind of help.
>
> - Simon
>
> *OrientDB release?*
> 2.2.34
>
> *What steps will reproduce the problem?*
> Unknown - our attempts to reproduce the problem have been very
> unsatisfying yet. Nonetheless, the problem occurs again and again (without
> a recognizable pattern), in different runtime environments of different
> customers, and in different situations. It seems to happen in random
> situations when the database is accessed. It happens that one query is
> successful, and the next one fails (with the error below), and then every
> subsequent query also fails.
>
> Symptoms:
> An InvalidClassException occurs sometimes when querying the database:
> Caused by: com.orientechnologies.common.io.OIOException: com.o;
> serializable and externalizable flags conflict
> at
> com.orientechnologies.orient.client.remote.OStorageRemote.handleIOException(OStorageRemote.java:321)
> at
> com.orientechnologies.orient.client.remote.OStorageRemote.baseNetworkOperation(OStorageRemote.java:292)
> at
> com.orientechnologies.orient.client.remote.OStorageRemote.networkOperationRetry(OStorageRemote.java:204)
> at
> com.orientechnologies.orient.client.remote.OStorageRemote.networkOperation(OStorageRemote.java:215)
> at
> com.orientechnologies.orient.client.remote.OStorageRemote.command(OStorageRemote.java:1187)
> at
> com.orientechnologies.orient.core.command.OCommandRequestTextAbstract.execute(OCommandRequestTextAbstract.java:69)
> at
> com.tinkerpop.blueprints.impls.orient.OrientGraphCommand.execute(OrientGraphCommand.java:49)
> at com.mycompany.BaseDAOImpl.query(OrientConnection.java:188)
> ... 13 common frames omitted
> Caused by: java.io.InvalidClassException: com.o; serializable and
> externalizable flags conflict
> at java.base/java.io.ObjectStreamClass.readNonProxy(Unknown Source)
> at java.base/java.io.ObjectInputStream.readClassDescriptor(Unknown Source)
> at java.base/java.io.ObjectInputStream.readNonProxyDesc(Unknown Source)
> at java.base/java.io.ObjectInputStream.readClassDesc(Unknown Source)
> at java.base/java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
> at java.base/java.io.ObjectInputStream.readObject0(Unknown Source)
> at java.base/java.io.ObjectInputStream.readObject(Unknown Source)
> at
> com.orientechnologies.orient.client.binary.OChannelBinaryAsynchClient.throwSerializedException(OChannelBinaryAsynchClient.java:436)
> at
> com.orientechnologies.orient.client.binary.OChannelBinaryAsynchClient.handleStatus(OChannelBinaryAsynchClient.java:400)
> at
> com.orientechnologies.orient.client.binary.OChannelBinaryAsynchClient.beginResponse(OChannelBinaryAsynchClient.java:283)
> at
> com.orientechnologies.orient.client.binary.OChannelBinaryAsynchClient.beginResponse(OChannelBinaryAsynchClient.java:167)
> at
> com.orientechnologies.orient.client.remote.OStorageRemote.beginResponse(OStorageRemote.java:2365)
> at
> com.orientechnologies.orient.client.remote.OStorageRemote$27.execute(OStorageRemote.java:1211)
> at
> com.orientechnologies.orient.client.remote.OStorageRemote$2.execute(OStorageRemote.java:207)
> at
> com.orientechnologies.orient.client.remote.OStorageRemote.baseNetworkOperation(OStorageRemote.java:252)
> ... 19 common frames omitted
>
> The *BaseDAOImpl.query* looks like:
> public Iterable query(String query, Object... params) throws
> PersistenceException {
> OrientBaseGraph graph = OrientGraph.getActiveGraph();
> try {
> OCommandSQL command = new OCommandSQL(query);
> graph.clearCache();
> return graph.command(command).execute(params);
> } catch (Exception e) {
> throw new PersistenceException("Query triggered an exception", e);
> }
> }
>
> It is called in the following context:
> OrientGraphFactory factory = new
> OrientGraphFactory("remote:localhost/mydb", user, password).setupPool(10,
> 50);
> setRequireTransaction(true);
> setAutoStartTx(false);
> OrientGraph db = factory.getTx();
> ...
> baseDAO.query("select from MyClass");
> ...
> db.shutdown();
>
>
> *If you're using custom settings please provide them below (to dump all
> the settings run the application using the JVM
> argument -Denvironment.dumpCfgAtStartup=true):*
> OrientDB 2.2.34 (build f340442755a31eabc91b87cb3ef99eda5cee6ebd, branch
> 2.2.x) configuration dump:
> - ENVIRONMENT
>   + environment.dumpCfgAtStartup = true
>   + environment.concurrent = true
>   + environment.lockManager.concurrency.level = 64
>   + environment.allowJVMShutdown = true
> - SCRIPT
>   + script.pool.maxSize = 20
> - MEMORY
>   + me

Re: [orientdb] how to perform deep traversal

[Luigi Dell'Aquila]

Hi Suraj,

it will return an OElement per path, containing a property named "thePath"
that is a list of RIDs.
If you need expanded data, you can use nested projections
https://orientdb.com/docs/3.0.x/sql/SQL-Projections.html#nested-projections

Thanks

Luigi

Il giorno mar 28 ago 2018 alle ore 17:24 Suraj Shankar <
surajhebbarshanka...@gmail.com> ha scritto:

> Thanks a lot luigi. Just one more question adding to it. If I execute this
> command from java code, how can I work with the results? Like the
> individual nodes ? What will be the return type once I execute from
> command() statement?
>
> On Tue, Aug 28, 2018 at 1:07 AM, Luigi Dell'Aquila <
> luigi.dellaqu...@gmail.com> wrote:
>
>> hi Suraj,
>>
>> The TRAVERSE statement automatically skips already traversed nodes, this
>> is why you don't see all the parents
>>
>> You can use a MATCH with "while" condition instead:
>>
>> MATCH
>>   {class:nodesLeaf, as:a} <-contains- {as:b, while:(true),
>> pathAlias:b_path}
>> RETURN b_path || b as thePath
>>
>> I hope it helps
>>
>> Thanks
>>
>> Luigi
>>
>> Il giorno mar 28 ago 2018 alle ore 09:52 Suraj Shankar <
>> surajhebbarshanka...@gmail.com> ha scritto:
>>
>>>
>>> My query is
>>> traverse in(“contains”) from (select from nodesLeaf) strategy
>>> depth_first
>>>
>>> On Tue, Aug 28, 2018 at 12:37 AM, Suraj Shankar <
>>> surajhebbarshanka...@gmail.com> wrote:
>>>
>>>> Yes I am using the traverse command in sql
>>>>
>>>> On Tue, Aug 28, 2018 at 12:37 AM, Luigi Dell'Aquila <
>>>> luigi.dellaqu...@gmail.com> wrote:
>>>>
>>>>> Hi Suraj,
>>>>>
>>>>> how do you do the traversal? in SQL?
>>>>>
>>>>> Thanks
>>>>>
>>>>> Luigi
>>>>>
>>>>>
>>>>> Il giorno mar 28 ago 2018 alle ore 09:31 Suraj Shankar <
>>>>> surajhebbarshanka...@gmail.com> ha scritto:
>>>>>
>>>>>> HI All,
>>>>>>  I have a graph as following :
>>>>>> 1->1.1
>>>>>> 1->1.2
>>>>>> 2->2.1
>>>>>> 2->2.2
>>>>>> 2->2.3
>>>>>>
>>>>>> Now when i start at any of the leaf nodes and traverse using in
>>>>>> nodes, i get
>>>>>> 1.1,1
>>>>>> 1.2
>>>>>> 2.1,2
>>>>>> 2.2
>>>>>> 2.3
>>>>>> However i want the parent node as well in all the paths. How can i
>>>>>> perform this?
>>>>>>
>>>>>> --
>>>>>>
>>>>>> ---
>>>>>> You received this message because you are subscribed to the Google
>>>>>> Groups "OrientDB" group.
>>>>>> To unsubscribe from this group and stop receiving emails from it,
>>>>>> send an email to orient-database+unsubscr...@googlegroups.com.
>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>
>>>>> --
>>>>>
>>>>> ---
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups "OrientDB" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>>> an email to orient-database+unsubscr...@googlegroups.com.
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>
>>>> --
>>>
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "OrientDB" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to orient-database+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
>>
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "OrientDB" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to orient-database+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] how to perform deep traversal

[Luigi Dell'Aquila]

hi Suraj,

The TRAVERSE statement automatically skips already traversed nodes, this is
why you don't see all the parents

You can use a MATCH with "while" condition instead:

MATCH
  {class:nodesLeaf, as:a} <-contains- {as:b, while:(true), pathAlias:b_path}
RETURN b_path || b as thePath

I hope it helps

Thanks

Luigi

Il giorno mar 28 ago 2018 alle ore 09:52 Suraj Shankar <
surajhebbarshanka...@gmail.com> ha scritto:

>
> My query is
> traverse in(“contains”) from (select from nodesLeaf) strategy depth_first
>
> On Tue, Aug 28, 2018 at 12:37 AM, Suraj Shankar <
> surajhebbarshanka...@gmail.com> wrote:
>
>> Yes I am using the traverse command in sql
>>
>> On Tue, Aug 28, 2018 at 12:37 AM, Luigi Dell'Aquila <
>> luigi.dellaqu...@gmail.com> wrote:
>>
>>> Hi Suraj,
>>>
>>> how do you do the traversal? in SQL?
>>>
>>> Thanks
>>>
>>> Luigi
>>>
>>>
>>> Il giorno mar 28 ago 2018 alle ore 09:31 Suraj Shankar <
>>> surajhebbarshanka...@gmail.com> ha scritto:
>>>
>>>> HI All,
>>>>  I have a graph as following :
>>>> 1->1.1
>>>> 1->1.2
>>>> 2->2.1
>>>> 2->2.2
>>>> 2->2.3
>>>>
>>>> Now when i start at any of the leaf nodes and traverse using in nodes,
>>>> i get
>>>> 1.1,1
>>>> 1.2
>>>> 2.1,2
>>>> 2.2
>>>> 2.3
>>>> However i want the parent node as well in all the paths. How can i
>>>> perform this?
>>>>
>>>> --
>>>>
>>>> ---
>>>> You received this message because you are subscribed to the Google
>>>> Groups "OrientDB" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to orient-database+unsubscr...@googlegroups.com.
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>> --
>>>
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "OrientDB" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to orient-database+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] how to perform deep traversal

[Luigi Dell'Aquila]

Hi Suraj,

how do you do the traversal? in SQL?

Thanks

Luigi


Il giorno mar 28 ago 2018 alle ore 09:31 Suraj Shankar <
surajhebbarshanka...@gmail.com> ha scritto:

> HI All,
>  I have a graph as following :
> 1->1.1
> 1->1.2
> 2->2.1
> 2->2.2
> 2->2.3
>
> Now when i start at any of the leaf nodes and traverse using in nodes, i
> get
> 1.1,1
> 1.2
> 2.1,2
> 2.2
> 2.3
> However i want the parent node as well in all the paths. How can i perform
> this?
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] How can I read edges from a cluster of E

[Luigi Dell'Aquila]

Hi,

The syntax is correct, if the clusters contain data they will be returned.
Are you sure that clusters e_1, e_2 contain records?

Thanks

Luigi

2018-05-27 14:20 GMT+02:00 :

>
> I can run a query such as follow to read edges from cluster 1,2 of IP
> class:
>
>
> select from cluster:[ip_1, ip_2]
>
>
> but I can't run such a query for all edges:
>
>
> select from cluster:[e_1, e_2]
>
>
> It always returns null. Would you mind telling me how I can do that?
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] Web site no longer shows ODB 3.0.0 docs or release???

[Luigi Dell'Aquila]

Hi Hristo,

You're right, I'm fixing it

Thanks

Luigi


2018-05-18 0:41 GMT+02:00 Hristo Stoyanov :

> DOCS->
>  -> DOCS
>  -> RELEASES
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] Is OCommandSQL done synchronously?

[Luigi Dell'Aquila]

Hi Erik,

The Command is intended for the execution of non-idempotent statements
(e.g. UPDATE or INSERT), while the Query can only execute idempotent
statements (eg. SELECT, MATCH)

Thanks

Luigi



2018-05-17 12:31 GMT+02:00 Erik T :

> Thanks Luigi.
>
> So what's the difference between OCommandSQL and OSQLSyncQuery? They seem
> to be the same so why have two classes?
>
> On Thu, May 17, 2018, 3:30 AM Luigi Dell'Aquila <
> luigi.dellaqu...@gmail.com> wrote:
>
>> Hi Erik,
>>
>> The query is executed synchronously. The result is returned as soon as
>> all the result set is available.
>>
>> With the new API (v 3.0) the queries are still synchronous, but the
>> result set is paginated, so the first results are returned as soon as they
>> are available
>>
>> Thanks
>>
>> Luigi
>>
>>
>> 2018-05-16 21:43 GMT+02:00 Erik T :
>>
>>> For this code
>>>
>>> OCommandSQL preparedQuery = new OCommandSQL(query);
>>> OrientBaseGraph graph = (OrientBaseGraph) getGraph().getBaseGraph();
>>> return AccessController.doPrivileged((PrivilegedAction) () -> 
>>> graph.command(preparedQuery).execute(stationNames));
>>>
>>>
>>> Is preparedQuery executed synchronously or asynchronously?
>>>
>>> --
>>>
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "OrientDB" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to orient-database+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
>>
>> ---
>> You received this message because you are subscribed to a topic in the
>> Google Groups "OrientDB" group.
>> To unsubscribe from this topic, visit https://groups.google.com/d/
>> topic/orient-database/OheQJchmXME/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> orient-database+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] OrientDB 3.x JCA adapter

[Luigi Dell'Aquila]

Hi Hristo,

Thank you very much for letting us know, I think this could be of interest
for many users in the community.
Please keep us updated on the progress and, if you need any advice during
the development, please do not hesitate to ask

Thanks

Luigi


2018-05-17 0:04 GMT+02:00 Hristo Stoyanov :

> Hello,
> I created an OrientDB 3.x - compatible JCA adapter here
> . It is at a very early stage (I
> have only tested it in OpenLiberty server).
> Feedback/pull requests/github stars are welcome!
>
> Cheers
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] Is OCommandSQL done synchronously?

[Luigi Dell'Aquila]

Hi Erik,

The query is executed synchronously. The result is returned as soon as all
the result set is available.

With the new API (v 3.0) the queries are still synchronous, but the result
set is paginated, so the first results are returned as soon as they are
available

Thanks

Luigi


2018-05-16 21:43 GMT+02:00 Erik T :

> For this code
>
> OCommandSQL preparedQuery = new OCommandSQL(query);
> OrientBaseGraph graph = (OrientBaseGraph) getGraph().getBaseGraph();
> return AccessController.doPrivileged((PrivilegedAction) () -> 
> graph.command(preparedQuery).execute(stationNames));
>
>
> Is preparedQuery executed synchronously or asynchronously?
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] In 3.0.0 unlike ODatabaseDocumentTx , OrientDB constructor throwing exception for in memory DB

[Luigi Dell'Aquila]

Hi Arjun,

With the new API the db creation is a bit different, programmatically it
would be something as follows:

OrientDB orient = new OrientDB("embedded:./",config);
orient.create("neurosys_orientdb_odb",ODatabaseType.MEMORY);

// and create a pool
ODatabasePool pool = new ODatabasePool(orient,"neurosys_orientdb_odb
","admin","admin",config);

// or open a connection directly
orient.open("neurosys_orientdb_odb","admin","admin",config);


So you need four parameters:
- the db path ("embedded:./" in this case, but if you only have in-memory
databases you can hard-wire it, as it will never be used)
- the actual db name (neurosys_orientdb_odb)
- the username
- the password

Probably you will have to do little changes to your application
accordingly, but it should not be too complex

I hope it helps

Thanks

Luigi





2018-05-14 9:16 GMT+02:00 Luigi Dell'Aquila :

> Hi Arjun,
>
> Thank you very much for reporting, I'll check it asap.
>
> Thanks
>
> Luigi
>
> 2018-05-14 7:23 GMT+02:00 arjun dhar :
>
>> Hi,
>>
>> *Summary*
>> Am on OrientDB 3.0.0 ; and am trying to avoid the use of Depreicated API
>> like: ODatabaseDocumentTx
>> However, when I replace it with com.orientechnologies.ori
>> ent.core.db.OrientDB ; for the same configs that otherwise work fine it
>> blows up.
>>
>> Details below...
>>
>> *Configuration*
>> ```
>> odb.url=memory:neurosys_orientdb_odb
>> odb.username=admin
>> odb.password=admin
>> odb.maxPartitionSize=2
>> odb.maxPoolSize=10
>> ```
>>
>> *Spring Configs *using ODatabaseDocumentTx that work
>> ```
>> 
>> 
>> 
>>
>> 
>>   
>>   
>>   
>>   
>> 
>>   
>> ```
>>
>> *Spring Configs *using com.orientechnologies.orient.core.db.OrientDB
>> that does *not *work
>> Simply replacing the  `*dataSourceOdb*` bean.
>> ```
>> 
>> 
>>   
>>   
>> 
>> 
>> ```
>>
>> *Exception thrown*
>> ```
>> com.orientechnologies.orient.core.exception.ODatabaseException: Cannot
>> open database 'neurosys_orientdb_odb'
>> at com.orientechnologies.orient.core.db.OrientDBEmbedded.open(O
>> rientDBEmbedded.java:140)
>> at com.orientechnologies.orient.core.db.document.ODatabaseDocum
>> entTx.open(ODatabaseDocumentTx.java:908)
>> at com.orientechnologies.orient.core.db.OPartitionedDatabasePoo
>> l$DatabaseDocumentTxPooled.internalOpen(OPartitionedDatabase
>> Pool.java:441)
>> at com.orientechnologies.orient.core.db.OPartitionedDatabasePoo
>> l.openDatabase(OPartitionedDatabasePool.java:306)
>> at com.orientechnologies.orient.core.db.OPartitionedDatabasePoo
>> l.acquire(OPartitionedDatabasePool.java:261)
>> ...
>> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(
>> RemoteTestRunner.java:192)
>> Caused by: com.orientechnologies.orient.core.exception.OStorageException:
>> Cannot open the storage 'neurosys_orientdb_odb' because it does not exist
>> in path: D:\orientdb\./neurosys_orientdb_odb
>> at com.orientechnologies.orient.core.storage.impl.local.OAbstra
>> ctPaginatedStorage.open(OAbstractPaginatedStorage.java:267)
>> at com.orientechnologies.orient.core.db.OrientDBEmbedded.open(O
>> rientDBEmbedded.java:131)
>> ... 34 more
>>
>> ```
>>
>> *Possible cause*
>> Looks like the path is getting messed up and assuming unix convention
>> path even for an in memory DB. Am on windows, but I dont see why that
>> anyway matters for an in-memory DB, plus it works with the deprecated one. 
>> *So
>> I assume this to be a bug, if not please let me know what Im missing.*
>>
>> thanks,
>> Arjun
>>
>> --
>>
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "OrientDB" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to orient-database+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] In 3.0.0 unlike ODatabaseDocumentTx , OrientDB constructor throwing exception for in memory DB

[Luigi Dell'Aquila]

Hi Arjun,

Thank you very much for reporting, I'll check it asap.

Thanks

Luigi

2018-05-14 7:23 GMT+02:00 arjun dhar :

> Hi,
>
> *Summary*
> Am on OrientDB 3.0.0 ; and am trying to avoid the use of Depreicated API
> like: ODatabaseDocumentTx
> However, when I replace it with com.orientechnologies.
> orient.core.db.OrientDB ; for the same configs that otherwise work fine
> it blows up.
>
> Details below...
>
> *Configuration*
> ```
> odb.url=memory:neurosys_orientdb_odb
> odb.username=admin
> odb.password=admin
> odb.maxPartitionSize=2
> odb.maxPoolSize=10
> ```
>
> *Spring Configs *using ODatabaseDocumentTx that work
> ```
> 
> 
> 
>
> 
>   
>   
>   
>   
> 
>   
> ```
>
> *Spring Configs *using com.orientechnologies.orient.core.db.OrientDB that
> does *not *work
> Simply replacing the  `*dataSourceOdb*` bean.
> ```
> 
> 
>   
>   
> 
> 
> ```
>
> *Exception thrown*
> ```
> com.orientechnologies.orient.core.exception.ODatabaseException: Cannot
> open database 'neurosys_orientdb_odb'
> at com.orientechnologies.orient.core.db.OrientDBEmbedded.open(
> OrientDBEmbedded.java:140)
> at com.orientechnologies.orient.core.db.document.ODatabaseDocumentTx.open(
> ODatabaseDocumentTx.java:908)
> at com.orientechnologies.orient.core.db.OPartitionedDatabasePool$
> DatabaseDocumentTxPooled.internalOpen(OPartitionedDatabasePool.java:441)
> at com.orientechnologies.orient.core.db.OPartitionedDatabasePool.
> openDatabase(OPartitionedDatabasePool.java:306)
> at com.orientechnologies.orient.core.db.OPartitionedDatabasePool.acquire(
> OPartitionedDatabasePool.java:261)
> ...
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.
> main(RemoteTestRunner.java:192)
> Caused by: com.orientechnologies.orient.core.exception.OStorageException:
> Cannot open the storage 'neurosys_orientdb_odb' because it does not exist
> in path: D:\orientdb\./neurosys_orientdb_odb
> at com.orientechnologies.orient.core.storage.impl.local.
> OAbstractPaginatedStorage.open(OAbstractPaginatedStorage.java:267)
> at com.orientechnologies.orient.core.db.OrientDBEmbedded.open(
> OrientDBEmbedded.java:131)
> ... 34 more
>
> ```
>
> *Possible cause*
> Looks like the path is getting messed up and assuming unix convention path
> even for an in memory DB. Am on windows, but I dont see why that anyway
> matters for an in-memory DB, plus it works with the deprecated one. *So I
> assume this to be a bug, if not please let me know what Im missing.*
>
> thanks,
> Arjun
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] WAL Files

[Luigi Dell'Aquila]

Hi Erik,

When there is no space left on disk, OrientDB tries to the WAL (do a full
checkpoint) and then delete the files.
This also happens as a normal activity, so WAL files are eventually deleted
even if there is still space left on disk

Thanks

Luigi


2018-05-09 20:19 GMT+02:00 Erik T :

> What happens when the WAL files reach the maximum size? Does Orient start
> to overwrite old logs?
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] DECIMAL data type is rounding values?

[Luigi Dell'Aquila]

Mmm... just thinking out loud... JSON does not allow absolute precision
numbers, so there is no native way to pass the equivalent of a BigDecimal.
The alternatives are:
- keep sending a number and lose precision
- pass the value as a string, but it will make it harder to manipulate it
on the client and won't help when you convert it to a number in js.
Moreover, it will break backward compatibility in OrientDB, so I don't know
if I can do it...

Thanks

Luigi


2018-05-07 12:45 GMT+02:00 Luigi Dell'Aquila :

> Hi Peter,
>
> I just did a quick test, the problem is only on the REST/JSON layer.
> If you do the queries from console (or from a binary driver) you'll see
> that the results are correct and the numbers are not rounded.
> Could you please open an issue here https://github.com/
> orientechnologies/orientdb/issues
> I'll try to fix it asap
>
> Thanks
>
> Luigi
>
>
> 2018-05-07 12:09 GMT+02:00 :
>
>> Hi Luigi,
>> Thank you for replying so quickly.
>>
>> I've tried it from the studio through the tab Schema -> Vertex Classes ->
>> New Record dialog.
>>
>> It also happens if I do the following from the Studio SQL console:
>> INSERT INTO bigvertex (bigvalue)
>>   VALUES (DECIMAL("9223372036854775807"))
>>
>> I would like to use OrientDB to store edges with an attribute describing
>> amounts - big numbers up to 80 digits, and be able to do calculations like
>> SUM or AVG on them.
>> I was hoping OrientDB is the right tool, maybe I'm just doing something
>> wrong?
>>
>> Cheers,
>> Peter
>>
>> --
>>
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "OrientDB" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to orient-database+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] DECIMAL data type is rounding values?

[Luigi Dell'Aquila]

Hi Peter,

I just did a quick test, the problem is only on the REST/JSON layer.
If you do the queries from console (or from a binary driver) you'll see
that the results are correct and the numbers are not rounded.
Could you please open an issue here
https://github.com/orientechnologies/orientdb/issues
I'll try to fix it asap

Thanks

Luigi


2018-05-07 12:09 GMT+02:00 :

> Hi Luigi,
> Thank you for replying so quickly.
>
> I've tried it from the studio through the tab Schema -> Vertex Classes ->
> New Record dialog.
>
> It also happens if I do the following from the Studio SQL console:
> INSERT INTO bigvertex (bigvalue)
>   VALUES (DECIMAL("9223372036854775807"))
>
> I would like to use OrientDB to store edges with an attribute describing
> amounts - big numbers up to 80 digits, and be able to do calculations like
> SUM or AVG on them.
> I was hoping OrientDB is the right tool, maybe I'm just doing something
> wrong?
>
> Cheers,
> Peter
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] DECIMAL data type is rounding values?

[Luigi Dell'Aquila]

Hi Peter,

How are you instantiating the value? From SQL? Did you try to use decimal()
function?

Thanks

Luigi

2018-05-07 1:25 GMT+02:00 :

> Hi everyone. I'm quite new to OrientDB, but have found it because it
> appeared it has support for large numbers.
>
> The DECIMAL data type appeared to be the solution.
> https://orientdb.com/docs/last/Types.html says its without rounding and
> any number.
>
> However, when I try to create a vertex from the studio with a DECIMAL
> value of 9223372036854775807, it gets saved as 922337203685478.
> Is this expected behavior?
> Do I need to user another data type?
>
> It happens in version 2.2.34 and 3.0.0RC2
>
> Cheers,
> Peter
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] Using OrientDB on Android?

[Luigi Dell'Aquila]

Hi Alex,

A few years ago some community users tried to do a porting of OrientDB for
Android, but it was never completed.
I never tried to run current OrientDB version on Android, but I'm pretty
sure that it doesn't work out of the box.

Thanks

Luigi

2018-04-07 21:23 GMT+02:00 Alex Fowler :

> Hello! Is it possible to use OrientDB (any modern version) in an Android
> application, as an in-memory graph database?
>
> If not, could you suggest any alternatives, please?
>
> Thank you :)
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] Lucene query with sorting. Performance problem

[Luigi Dell'Aquila]

Hi Mohammad,

Lucene indexes do not provide ordering (or better, they return results
based on their score, but it's not what you need).
What you can do here is define an additional NOTUNIQUE index on "name",
this will do the job

Thanks

Luigi

2018-03-31 23:45 GMT+02:00 Mohammad Hossein Ganjyar <
hossein.ganj...@gmail.com>:

> I have this problem with orientdb v2.2.31. I have vertex Users with
> properties id (no index), name (lucene index), family(lucene index).
> My quesry is :
> SELECT @rid, name , family FROM profiles
> order by name asc
> limit 10
> This query is very slow (exc in ~17 seconds).
> Do you best idea?
> thanks
>
> On Friday, September 26, 2014 at 1:20:12 PM UTC+3:30, Enrico Risa wrote:
>>
>> Hi Etienne
>>
>> can you try to remove the not unique index
>> and paste here the explain of
>>
>> *select from Tracks [Title, ArtistName, AlbumName] LUCENE 'daft+punk'
>> order by relevance desc*
>>
>>
>> Thanks
>>
>> Enrico
>>
>> 2014-09-26 11:30 GMT+02:00 Etienne Crinier :
>>
>>> Hi,
>>>
>>> I have a 'fulltext lucene' index to do a quick search on multiple
>>> fields. It is working properly.
>>> Now i would like to sort these results through a numeric field.
>>> Therefore, I created a 'notunique' index to this field.
>>> You can find below my request :
>>> *select from Tracks [Title, ArtistName, AlbumName] LUCENE 'daft+punk'
>>> order by relevance desc*
>>>
>>> Without the "order by" method performance is good:
>>> explainwithoutorderby.jpg
>>>
>>> Now with "order by": explainwithoutorderby.jpg
>>>
>>>
>>> You can see the order by index unused. Performance decreases
>>> dramatically.
>>>
>>> Do you have any idea on how to solve this issue?
>>>
>>> --
>>>
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "OrientDB" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to orient-databa...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] OrientDB sql query involving multiple classes

[Luigi Dell'Aquila]

---
> 
> ---
> IN THE OTHER HAND, When i delete records with relations , My Select query
> works fine. I can see all records without relation.
> But my main goal is getting companyCode when i query on
> PersonelInformation vertex.
>
>
> Also i tried This.
>
> -select adress from user where = out('PersonelRelation')[0].name =
> "orient"
>
> 
> --------
>
> OUT comes like this.
>  b64:'AQEAggAA'
>
> IN SHORT my main problem is when i connect the Company And Personel
> Classes, i want to see Company class informations over personelInformation
> Query. But i dont want to restrict my query like , select from where rid =
> 37
> i just want to get company information  wihtout giving any company
> information in Personel Query. Just want to get informations about Company
> in Back end and want to read them. Its not important after a query like =
> select from personel where CompanyCode "abc"
>
>
> Really Thanks alot from now
> Looking for your answer
>
>
> Regards,
> Ersin
>
>
>
>
> 5 Mart 2018 Pazartesi 12:21:40 UTC+3 tarihinde Luigi Dell'Aquila yazdı:
>>
>> Hi Ersin,
>>
>> There is no SQL statement to do this, but you can use Teleporter
>> (included in OrientDB Studio) to do a full import from SQL to a pure graph.
>>
>> About multiple classes as target in a query, you cannot do it that way,
>> what you probably need is MATCH https://orientdb.com/docs/3.0.
>> x/sql/SQL-Match.html
>>
>> Thanks
>>
>> Luigi
>>
>>
>>
>> 2018-03-03 19:57 GMT+01:00 Ersin Sevinc :
>>
>>> Hi there, m new at orient db trying to figure out something about
>>> relations ,
>>> In this code Line => create edge owns from (select from Person where
>>> name = 'Matt') to (select from Car where model = 'Ferrari')
>>> We have edge between record to record. Its fine for few records. But
>>> what will happen if i ve millions of data ? Should i create edge from
>>> backend for every new record?
>>> Or can i just link the Property Fields like => create edge owns from
>>> Person.Name to Car.model ??
>>>
>>> I want to know that is there any possible way for relation database like
>>> MSSQL , you know in ms sql , we can create PK and FK between Fields , with
>>> that way we do not need to create relations for every new record.
>>>
>>> Here another question -> select car.model person.name from car, person
>>> Where ..   I think i can not use 2
>>> different class after FROM m i right ?
>>>
>>> 27 Mart 2014 Perşembe 17:03:33 UTC+3 tarihinde Andrey Lomakin yazdı:
>>>>
>>>> Hi,
>>>> Could you try
>>>>
>>>> select name from Person where gender = 'M' and out('owns')[0].model =
>>>> "Ferrari" and out('likes')[0].mov_name = "Need For Speed"
>>>>
>>>>
>>>> On Thu, Mar 27, 2014 at 5:13 AM, Joel Mathew  wrote:
>>>>
>>>>> Hi group,
>>>>> I have below schema with three classes
>>>>>
>>>>> orientdb {demo1}> select from Person
>>>>> +-+-+--++-
>>>>> #   |@RID |name |gender|out_owns|out_likes
>>>>> +-+-+--++-
>>>>> 0   |#11:0|Matt |M |#12:0   |#13:0
>>>>> 1   |#11:1|Helen|F |#12:1   |#13:1
>>>>> +-+-+--++-
>>>>>
>>>>> orientdb {demo1}> select from Car
>>>>> +-+---+---
>>>>> #   |@RID |model  |in_owns
>>>>> +-+---+---
>>>>> 0   |#12:0|Ferrari|#11:0
>>>>> 1   |#12:1|BMW|#11:1
>>>>> +-+---+---
>>>>>
>>>>> orientdb {demo1}> select from Movie
>>>>> +-+--+
>>>>> #   |@RID |mov_name  |in_likes
>>>>> +-+--+
>>>>> 0   |#13:0|Need For Speed|#11:0
>>>>> 1   |#13:1|Matrix|#11:1
>>>>> +-+--+
>>>

Re: [orientdb] Select from where traverse operator not working

[Luigi Dell'Aquila]

Hi Steve,

Sorry, we are pretty busy with the release of v 3.0.0, I'll try to follow
up as soon as I can.

The traverse() executor is still there, but only in the old SQL executor.
The new parser (strict SQL) was implemented for the new executor, so it
doesn't make much sense to have it in the parser without implementing it in
the new executor.
I have to say that in general we don't like the traverse() operator syntax
much, and now we have many alternatives like TRAVERSE and MATCH queries
that are supposed to do the same thing, so adding complexity re-introducing
a legacy behavior does not sound a very good choice.
To be honest, since we switched on the strictSQL option by default (more
than two years ago), it's maybe the second time we have an explicit request
for the traverse() operator, and in both cases it was for a migration from
previous versions, so I'm pretty confident that we can cover your use case
what we have, with better performance and a more elegant way.

I'll keep you posted

Thanks

Luigi


2018-03-26 15:52 GMT+02:00 Steven Tomer :

> Luigi,
>
> I haven't heard back on this.
>
> Since the backend to the traverse() is still there, we're wondering how
> much trouble it would be to add it into the new parser.
>
> It definitely has some powerful and unique use cases.  If these aren't
> covered by the new match projection, I would suggest that it should live on
> to cover them.
>
> Thanks,
>
> Steve
>
> On Tue, Mar 20, 2018, 9:37 AM Steven Tomer  wrote:
>
>> Thanks so much!
>>
>> Steve
>>
>> On Tue, Mar 20, 2018 at 9:34 AM, Luigi Dell'Aquila <
>> luigi.dellaqu...@gmail.com> wrote:
>>
>>> Hi Steve,
>>>
>>> Thank you very much, I'll check it asap.
>>> There is a way to re-enable the old traverse, you have to disable strict
>>> SQL parsing:
>>>
>>> ALTER DATABASE CUSTOM strictSQL=false
>>>
>>> Anyway, I wouldn't recommend it in the long run, as you will lose a lot
>>> of stability in SQL parsing
>>>
>>> I'll give you a feedback asap about the query
>>>
>>> Thanks
>>>
>>> Luigi
>>>
>>> 2018-03-20 16:30 GMT+01:00 Steven Tomer :
>>>
>>>> Luigi,
>>>>
>>>> I've zipped up the dataset I've been using and am attaching it here.
>>>>
>>>> We really need a way to do queries like this.  Is there any chance we
>>>> can re-enable the old traverse() operator?
>>>>
>>>> Thanks,
>>>>
>>>> Steve
>>>>
>>>> On Tue, Mar 13, 2018 at 9:08 AM, Luigi Dell'Aquila <
>>>> luigi.dellaqu...@gmail.com> wrote:
>>>>
>>>>> Hi Steve,
>>>>>
>>>>> ah, got it, the old traverse() stopped when it found duplicates, while
>>>>> the MATCH doesn't.
>>>>>
>>>>> Do you have a dataset I can check, so that I can try it and give you
>>>>> better help?
>>>>>
>>>>> Thanks
>>>>>
>>>>> Luigi
>>>>>
>>>>>
>>>>>
>>>>> 2018-03-13 16:03 GMT+01:00 Steven Tomer :
>>>>>
>>>>>> Luigi,
>>>>>>
>>>>>> That query never returns (looks like it goes into an infinite loop).
>>>>>>
>>>>>> I had to kill the server process to make it stop.
>>>>>>
>>>>>> Any other ideas?
>>>>>>
>>>>>> Steve
>>>>>>
>>>>>> On Tue, Mar 13, 2018 at 8:16 AM, Luigi Dell'Aquila <
>>>>>> luigi.dellaqu...@gmail.com> wrote:
>>>>>>
>>>>>>> Hi Steve,
>>>>>>>
>>>>>>> Try this
>>>>>>>
>>>>>>> SELECT expand(person) FROM (
>>>>>>>   MATCH {class: Person, as: person, where: (givenname =
>>>>>>> 'William')}.in(){while: ($depth = 0 OR givenname != 'George'), where:
>>>>>>> (givenname = 'George')} RETURN person
>>>>>>> )
>>>>>>>
>>>>>>> The $depth = 0 guarantees that you don't stop traversing
>>>>>>> immediately; the givenname != 'George' just stops traversing as
>>>>>>> soon as you find a "George", I guess it is what you want (you don't need
>>>>>>>

Re: [orientdb] Select from where traverse operator not working

[Luigi Dell'Aquila]

Hi Steve,

Thank you very much, I'll check it asap.
There is a way to re-enable the old traverse, you have to disable strict
SQL parsing:

ALTER DATABASE CUSTOM strictSQL=false

Anyway, I wouldn't recommend it in the long run, as you will lose a lot of
stability in SQL parsing

I'll give you a feedback asap about the query

Thanks

Luigi

2018-03-20 16:30 GMT+01:00 Steven Tomer :

> Luigi,
>
> I've zipped up the dataset I've been using and am attaching it here.
>
> We really need a way to do queries like this.  Is there any chance we can
> re-enable the old traverse() operator?
>
> Thanks,
>
> Steve
>
> On Tue, Mar 13, 2018 at 9:08 AM, Luigi Dell'Aquila <
> luigi.dellaqu...@gmail.com> wrote:
>
>> Hi Steve,
>>
>> ah, got it, the old traverse() stopped when it found duplicates, while
>> the MATCH doesn't.
>>
>> Do you have a dataset I can check, so that I can try it and give you
>> better help?
>>
>> Thanks
>>
>> Luigi
>>
>>
>>
>> 2018-03-13 16:03 GMT+01:00 Steven Tomer :
>>
>>> Luigi,
>>>
>>> That query never returns (looks like it goes into an infinite loop).
>>>
>>> I had to kill the server process to make it stop.
>>>
>>> Any other ideas?
>>>
>>> Steve
>>>
>>> On Tue, Mar 13, 2018 at 8:16 AM, Luigi Dell'Aquila <
>>> luigi.dellaqu...@gmail.com> wrote:
>>>
>>>> Hi Steve,
>>>>
>>>> Try this
>>>>
>>>> SELECT expand(person) FROM (
>>>>   MATCH {class: Person, as: person, where: (givenname =
>>>> 'William')}.in(){while: ($depth = 0 OR givenname != 'George'), where:
>>>> (givenname = 'George')} RETURN person
>>>> )
>>>>
>>>> The $depth = 0 guarantees that you don't stop traversing immediately;
>>>> the givenname != 'George' just stops traversing as soon as you find a
>>>> "George", I guess it is what you want (you don't need duplicates)
>>>>
>>>> Thanks
>>>>
>>>> Luigi
>>>>
>>>> 2018-03-13 14:52 GMT+01:00 Steven Tomer :
>>>>
>>>>> Hello Luigi,
>>>>>
>>>>> That's sad news indeed.  It will require a major task to rip out all
>>>>> of the places we're using traverse().
>>>>>
>>>>> I've been playing around with the MATCH operator, and I can't get it
>>>>> to model the former query:
>>>>>
>>>>> SELECT FROM Person WHERE givenname = 'William' and in
>>>>> traverse(0,-1,'in') ( givenname = 'George' )
>>>>>
>>>>> I've tried:
>>>>>
>>>>> MATCH {class: Person, as: person, where: (givenname =
>>>>> 'William')}.in(){while: ($depth > 0), where: (givenname = 'George')} 
>>>>> RETURN
>>>>> person
>>>>> MATCH {class: Person, as: person, where: (givenname =
>>>>> 'William')}.in('in'){while: ($depth > 0), where: (givenname = 'George')}
>>>>> RETURN person
>>>>> MATCH {class: Person, as: person, where: (givenname =
>>>>> 'William')}.in('MyEdge'){while: ($depth > 0), where: (givenname =
>>>>> 'George')} RETURN person
>>>>>
>>>>> None of your examples have an intermediary 'edge' type between them.
>>>>> We have Person -> MyEdge -> Person -> MyEdge -> Person.  The traverse
>>>>> operator lets me hop over the edges.  How do you do it with MATCH?
>>>>>
>>>>> Steve
>>>>>
>>>>>
>>>>>
>>>>> On Tue, Mar 13, 2018 at 2:07 AM, Luigi Dell'Aquila <
>>>>> luigi.dellaqu...@gmail.com> wrote:
>>>>>
>>>>>> Hi Steven,
>>>>>>
>>>>>> The traverse() operator was deprecated long time ago and is not fully
>>>>>> supported anymore.
>>>>>> I strongly suggest you to use TRAVERSE queries (
>>>>>> https://orientdb.com/docs/2.2.x/SQL-Traverse.html) or even better
>>>>>> MATCH queries (https://orientdb.com/docs/2.2.x/SQL-Match.html)
>>>>>>
>>>>>> Another thing: if you are migrating no

Re: [orientdb] The value '1' is not supported for writeQuorum in distributed configuration

[Luigi Dell'Aquila]

Hi Maxim,

Try to just remove the quotes, I guess it's just a matter of "1" as a
string vs. 1 as a number

Thanks

Luigi


2018-03-14 9:34 GMT+01:00 Maxim Nikolaev :

> *I **receive error *
>
>
> com.orientechnologies.orient.server.distributed.ODistributedStartupException:
> Error on starting distributed plugin
>
> at com.orientechnologies.orient.server.hazelcast.
> OHazelcastPlugin.startup(OHazelcastPlugin.java:312)
>
> at com.orientechnologies.orient.server.OServer.
> registerPlugins(OServer.java:1268)
>
> at com.orientechnologies.orient.server.OServer.activate(
> OServer.java:415)
>
> at com.orientechnologies.orient.server.OServerMain$1.run(
> OServerMain.java:48)
>
> Caused by: 
> com.orientechnologies.orient.core.exception.OConfigurationException:
> The value '1' is not supported for writeQuorum in distributed configuration
>
> at com.orientechnologies.orient.server.distributed.
> ODistributedConfiguration.getQuorum(ODistributedConfiguration.java:820)
>
> at com.orientechnologies.orient.server.distributed.
> ODistributedConfiguration.getWriteQuorum(ODistributedConfiguration.
> java:722)
>
> at com.orientechnologies.orient.server.distributed.impl.
> ODistributedOutput.formatClusterTable(ODistributedOutput.java:542)
>
> at com.orientechnologies.orient.server.distributed.impl.
> ODistributedStorage.setDistributedConfiguration(
> ODistributedStorage.java:1791)
>
> at com.orientechnologies.orient.server.distributed.impl.
> ODistributedStorage.getDistributedConfiguration(
> ODistributedStorage.java:1772)
>
> at com.orientechnologies.orient.server.distributed.impl.
> ODistributedAbstractPlugin.getDatabaseConfiguration(
> ODistributedAbstractPlugin.java:452)
>
> at com.orientechnologies.orient.server.distributed.impl.
> ODistributedAbstractPlugin.getDatabaseConfiguration(
> ODistributedAbstractPlugin.java:443)
>
> at com.orientechnologies.orient.server.distributed.impl.
> ODistributedAbstractPlugin.executeInDistributedDatabaseLo
> ck(ODistributedAbstractPlugin.java:1778)
>
> at com.orientechnologies.orient.server.hazelcast.OHazelcastPlugin.
> loadLocalDatabases(OHazelcastPlugin.java:761)
>
> at com.orientechnologies.orient.server.hazelcast.
> OHazelcastPlugin.startup(OHazelcastPlugin.java:257)
>
> ... 3 more
>
> *{*
>
>   *"autoDeploy"**:* true*,*
>
>   *"readQuorum"**:* 1*,*
>
>   *"writeQuorum"**:** "1"**,*
>
>   *"executionMode"**:** "undefined"**,*
>
>   *"readYourWrites"**:* true*,*
>
>   *"newNodeStrategy"**:** "static"**,*
>
>   *"servers"**:* *{*
>
> *"*"**:** "master"*
>
>   *},*
>
>   *"clusters"**:* *{*
>
> *"internal"**:* *{*
>
> *},*
>
> *"public_message"**:{*
>
> *"servers"**:**[**"wideriver"**]*
>
> *},*
>
> *"reestrcompany"**:{*
>
> *"servers"**:**[**"orientEE"**]*
>
> *}*
>
>   *}*
>
> *}*
>
>
>
> But in documentation was wrote:
>
>
> writeQuorum On "write" operation (any write on database) this is the
> number of responses to be coherent before sending the response to the
> client. Set to 1 if you don't want this check at write time. Suggested
> value is N/2+1 where N is the number of replicas. In this way the quorum is
> reached only if the majority of nodes are coherent
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] Select from where traverse operator not working

[Luigi Dell'Aquila]

Hi Steve,

ah, got it, the old traverse() stopped when it found duplicates, while the
MATCH doesn't.

Do you have a dataset I can check, so that I can try it and give you better
help?

Thanks

Luigi



2018-03-13 16:03 GMT+01:00 Steven Tomer :

> Luigi,
>
> That query never returns (looks like it goes into an infinite loop).
>
> I had to kill the server process to make it stop.
>
> Any other ideas?
>
> Steve
>
> On Tue, Mar 13, 2018 at 8:16 AM, Luigi Dell'Aquila <
> luigi.dellaqu...@gmail.com> wrote:
>
>> Hi Steve,
>>
>> Try this
>>
>> SELECT expand(person) FROM (
>>   MATCH {class: Person, as: person, where: (givenname =
>> 'William')}.in(){while: ($depth = 0 OR givenname != 'George'), where:
>> (givenname = 'George')} RETURN person
>> )
>>
>> The $depth = 0 guarantees that you don't stop traversing immediately;
>> the givenname != 'George' just stops traversing as soon as you find a
>> "George", I guess it is what you want (you don't need duplicates)
>>
>> Thanks
>>
>> Luigi
>>
>> 2018-03-13 14:52 GMT+01:00 Steven Tomer :
>>
>>> Hello Luigi,
>>>
>>> That's sad news indeed.  It will require a major task to rip out all of
>>> the places we're using traverse().
>>>
>>> I've been playing around with the MATCH operator, and I can't get it to
>>> model the former query:
>>>
>>> SELECT FROM Person WHERE givenname = 'William' and in
>>> traverse(0,-1,'in') ( givenname = 'George' )
>>>
>>> I've tried:
>>>
>>> MATCH {class: Person, as: person, where: (givenname =
>>> 'William')}.in(){while: ($depth > 0), where: (givenname = 'George')} RETURN
>>> person
>>> MATCH {class: Person, as: person, where: (givenname =
>>> 'William')}.in('in'){while: ($depth > 0), where: (givenname = 'George')}
>>> RETURN person
>>> MATCH {class: Person, as: person, where: (givenname =
>>> 'William')}.in('MyEdge'){while: ($depth > 0), where: (givenname =
>>> 'George')} RETURN person
>>>
>>> None of your examples have an intermediary 'edge' type between them.  We
>>> have Person -> MyEdge -> Person -> MyEdge -> Person.  The traverse
>>> operator lets me hop over the edges.  How do you do it with MATCH?
>>>
>>> Steve
>>>
>>>
>>>
>>> On Tue, Mar 13, 2018 at 2:07 AM, Luigi Dell'Aquila <
>>> luigi.dellaqu...@gmail.com> wrote:
>>>
>>>> Hi Steven,
>>>>
>>>> The traverse() operator was deprecated long time ago and is not fully
>>>> supported anymore.
>>>> I strongly suggest you to use TRAVERSE queries (
>>>> https://orientdb.com/docs/2.2.x/SQL-Traverse.html) or even better
>>>> MATCH queries (https://orientdb.com/docs/2.2.x/SQL-Match.html)
>>>>
>>>> Another thing: if you are migrating now, you could probably consider v
>>>> 3.0 (see https://orientdb.com/orientdb-labs/), the final GA will be
>>>> released this week
>>>>
>>>> Thanks
>>>>
>>>> Luigi
>>>>
>>>>
>>>> 2018-03-12 23:00 GMT+01:00 StevenTomer :
>>>>
>>>>> Hello,
>>>>>
>>>>> I'm using OrientDB 2.2.32.  We're updating our software from 2.0.8.
>>>>>
>>>>> The traverse() operator in selects does not appear to be working.
>>>>>
>>>>> When I run the attached program, I get a com.orientechnologies.orient
>>>>> .core.sql.OCommandSQLParsingException.
>>>>>
>>>>> Exception in thread "main" com.orientechnologies.orient.c
>>>>> ore.sql.OCommandSQLParsingException: Error parsing query:
>>>>> SELECT FROM Person WHERE givenname = 'William' and in
>>>>> traverse(0,-1,'in') ( givenname = 'George' )
>>>>> ^
>>>>> Encountered "" at line 1, column 52.
>>>>> Was expecting one of:
>>>>>
>>>>> DB name="familytree"
>>>>>
>>>>> I hope it hasn't been removed.  We use both the TRAVERSE FROM and
>>>>> SELECT FROM WHERE traverse() extensively.
>>>

Re: [orientdb] Select from where traverse operator not working

[Luigi Dell'Aquila]

Hi Steve,

Try this

SELECT expand(person) FROM (
  MATCH {class: Person, as: person, where: (givenname =
'William')}.in(){while: ($depth = 0 OR givenname != 'George'), where:
(givenname = 'George')} RETURN person
)

The $depth = 0 guarantees that you don't stop traversing immediately;
the givenname
!= 'George' just stops traversing as soon as you find a "George", I guess
it is what you want (you don't need duplicates)

Thanks

Luigi

2018-03-13 14:52 GMT+01:00 Steven Tomer :

> Hello Luigi,
>
> That's sad news indeed.  It will require a major task to rip out all of
> the places we're using traverse().
>
> I've been playing around with the MATCH operator, and I can't get it to
> model the former query:
>
> SELECT FROM Person WHERE givenname = 'William' and in traverse(0,-1,'in')
> ( givenname = 'George' )
>
> I've tried:
>
> MATCH {class: Person, as: person, where: (givenname =
> 'William')}.in(){while: ($depth > 0), where: (givenname = 'George')} RETURN
> person
> MATCH {class: Person, as: person, where: (givenname =
> 'William')}.in('in'){while: ($depth > 0), where: (givenname = 'George')}
> RETURN person
> MATCH {class: Person, as: person, where: (givenname =
> 'William')}.in('MyEdge'){while: ($depth > 0), where: (givenname =
> 'George')} RETURN person
>
> None of your examples have an intermediary 'edge' type between them.  We
> have Person -> MyEdge -> Person -> MyEdge -> Person.  The traverse
> operator lets me hop over the edges.  How do you do it with MATCH?
>
> Steve
>
>
>
> On Tue, Mar 13, 2018 at 2:07 AM, Luigi Dell'Aquila <
> luigi.dellaqu...@gmail.com> wrote:
>
>> Hi Steven,
>>
>> The traverse() operator was deprecated long time ago and is not fully
>> supported anymore.
>> I strongly suggest you to use TRAVERSE queries (
>> https://orientdb.com/docs/2.2.x/SQL-Traverse.html) or even better MATCH
>> queries (https://orientdb.com/docs/2.2.x/SQL-Match.html)
>>
>> Another thing: if you are migrating now, you could probably consider v
>> 3.0 (see https://orientdb.com/orientdb-labs/), the final GA will be
>> released this week
>>
>> Thanks
>>
>> Luigi
>>
>>
>> 2018-03-12 23:00 GMT+01:00 StevenTomer :
>>
>>> Hello,
>>>
>>> I'm using OrientDB 2.2.32.  We're updating our software from 2.0.8.
>>>
>>> The traverse() operator in selects does not appear to be working.
>>>
>>> When I run the attached program, I get a com.orientechnologies.orient
>>> .core.sql.OCommandSQLParsingException.
>>>
>>> Exception in thread "main" com.orientechnologies.orient.c
>>> ore.sql.OCommandSQLParsingException: Error parsing query:
>>> SELECT FROM Person WHERE givenname = 'William' and in
>>> traverse(0,-1,'in') ( givenname = 'George' )
>>> ^
>>> Encountered "" at line 1, column 52.
>>> Was expecting one of:
>>>
>>> DB name="familytree"
>>>
>>> I hope it hasn't been removed.  We use both the TRAVERSE FROM and
>>> SELECT FROM WHERE traverse() extensively.
>>>
>>> TRAVERSE FROM is wonderful for gathering a group of records from a given
>>> point.
>>> The traverse() operator is wonderful for queries like the above (return
>>> all people named William
>>> descended from a person named George.
>>>
>>> We really need both.
>>>
>>> Thanks,
>>>
>>> Steven Tomer
>>>
>>> --
>>>
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "OrientDB" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to orient-database+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
>>
>> ---
>> You received this message because you are subscribed to a topic in the
>> Google Groups "OrientDB" group.
>> To unsubscribe from this topic, visit https://groups.google.com/d/to
>> pic/orient-database/ic5UE-kyi-w/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> orient-database+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] Select from where traverse operator not working

[Luigi Dell'Aquila]

Hi Steven,

The traverse() operator was deprecated long time ago and is not fully
supported anymore.
I strongly suggest you to use TRAVERSE queries (
https://orientdb.com/docs/2.2.x/SQL-Traverse.html) or even better MATCH
queries (https://orientdb.com/docs/2.2.x/SQL-Match.html)

Another thing: if you are migrating now, you could probably consider v 3.0
(see https://orientdb.com/orientdb-labs/), the final GA will be released
this week

Thanks

Luigi


2018-03-12 23:00 GMT+01:00 StevenTomer :

> Hello,
>
> I'm using OrientDB 2.2.32.  We're updating our software from 2.0.8.
>
> The traverse() operator in selects does not appear to be working.
>
> When I run the attached program, I get a com.orientechnologies.
> orient.core.sql.OCommandSQLParsingException.
>
> Exception in thread "main" 
> com.orientechnologies.orient.core.sql.OCommandSQLParsingException:
> Error parsing query:
> SELECT FROM Person WHERE givenname = 'William' and in traverse(0,-1,'in')
> ( givenname = 'George' )
> ^
> Encountered "" at line 1, column 52.
> Was expecting one of:
>
> DB name="familytree"
>
> I hope it hasn't been removed.  We use both the TRAVERSE FROM and
> SELECT FROM WHERE traverse() extensively.
>
> TRAVERSE FROM is wonderful for gathering a group of records from a given
> point.
> The traverse() operator is wonderful for queries like the above (return
> all people named William
> descended from a person named George.
>
> We really need both.
>
> Thanks,
>
> Steven Tomer
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] OrientDB sql query involving multiple classes

[Luigi Dell'Aquila]

Hi Ersin,

There is no SQL statement to do this, but you can use Teleporter (included
in OrientDB Studio) to do a full import from SQL to a pure graph.

About multiple classes as target in a query, you cannot do it that way,
what you probably need is MATCH
https://orientdb.com/docs/3.0.x/sql/SQL-Match.html

Thanks

Luigi



2018-03-03 19:57 GMT+01:00 Ersin Sevinc :

> Hi there, m new at orient db trying to figure out something about
> relations ,
> In this code Line => create edge owns from (select from Person where name
> = 'Matt') to (select from Car where model = 'Ferrari')
> We have edge between record to record. Its fine for few records. But what
> will happen if i ve millions of data ? Should i create edge from backend
> for every new record?
> Or can i just link the Property Fields like => create edge owns from
> Person.Name to Car.model ??
>
> I want to know that is there any possible way for relation database like
> MSSQL , you know in ms sql , we can create PK and FK between Fields , with
> that way we do not need to create relations for every new record.
>
> Here another question -> select car.model person.name from car, person
> Where ..   I think i can not use 2 different
> class after FROM m i right ?
>
> 27 Mart 2014 Perşembe 17:03:33 UTC+3 tarihinde Andrey Lomakin yazdı:
>>
>> Hi,
>> Could you try
>>
>> select name from Person where gender = 'M' and out('owns')[0].model =
>> "Ferrari" and out('likes')[0].mov_name = "Need For Speed"
>>
>>
>> On Thu, Mar 27, 2014 at 5:13 AM, Joel Mathew  wrote:
>>
>>> Hi group,
>>> I have below schema with three classes
>>>
>>> orientdb {demo1}> select from Person
>>> +-+-+--++-
>>> #   |@RID |name |gender|out_owns|out_likes
>>> +-+-+--++-
>>> 0   |#11:0|Matt |M |#12:0   |#13:0
>>> 1   |#11:1|Helen|F |#12:1   |#13:1
>>> +-+-+--++-
>>>
>>> orientdb {demo1}> select from Car
>>> +-+---+---
>>> #   |@RID |model  |in_owns
>>> +-+---+---
>>> 0   |#12:0|Ferrari|#11:0
>>> 1   |#12:1|BMW|#11:1
>>> +-+---+---
>>>
>>> orientdb {demo1}> select from Movie
>>> +-+--+
>>> #   |@RID |mov_name  |in_likes
>>> +-+--+
>>> 0   |#13:0|Need For Speed|#11:0
>>> 1   |#13:1|Matrix|#11:1
>>> +-+--+
>>>
>>> Person(name,gender)
>>> Car(model)
>>> Movie(mov_name)
>>> Person > owns > Car
>>> Person > likes > Movie
>>>
>>> I'm looking at a query which matches values across three classes across
>>> the edges
>>> Find Person.name where Person.gender='M' and who owns
>>> Car.model='Ferrari' and who likes Movie.mov_name='Need For Speed'
>>>
>>> One way to achieve the same with gremlin is
>>> g.V('@class','Car').has('model','Ferrari').in('owns').has('@
>>> class','Person').has('gender','M').as('x').out('likes').has(
>>> '@class','Movie').has('mov_name','Need For Speed').select(["x"])
>>> I'm using OrientDB 1.7-rc2-SNAPSHOT..
>>> Please help me with some pointers towards equivalent orientdb sql.
>>>
>>> Thanks,
>>> Mathew
>>>
>>>
>>> --
>>>
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "OrientDB" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to orient-databa...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Best regards,
>> Andrey Lomakin.
>>
>> Orient Technologies
>> the Company behind OrientDB
>>
>> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] OOM Exception while fetching records with Functions

[Luigi Dell'Aquila]

Hi Naveen,

Can you please some more information on how to reproduce the problem?
Do you have a database you can share to show this behaviour?

Thanks

Luigi

2018-02-28 10:04 GMT+01:00 Naveen Kumar :

> Hello Team,
>
> I'm facing issue in using functions for fetching data with recent release
> 2.2.32, the same was working fine with 2.2.17.
>
> Sample query: Select  test2() from Store limit 2
>
> Here test2 suppose to return few records, but even if it returns integer
> also the query is giving the same Exception. How to handle this. thanks.
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] Class name stored in every record in cluster PCL file

[Luigi Dell'Aquila]

Hi Chris,

I think you could be interested in this PR
https://github.com/orientechnologies/orientdb/pull/8115
Marko is working on it now

Thanks

Luigi


2018-02-22 14:07 GMT+01:00 cm-perrs :

> Hi Luigi,
>
> I would be happy to help contribute to this, as it is having a severe
> impact on file size in our application. Please can you point me to the
> classes where the issue is?
>
> Thanks,
> Chris
>
>
> On Thursday, February 8, 2018 at 11:47:19 PM UTC+10, Luigi Dell'Aquila
> wrote:
>>
>> Hi Ata,
>>
>> It will be a different format, but we will keep backward compatibility.
>> It's pretty hard to do it now, as it's not a trivial change and we are
>> close to the release
>>
>> Thanks
>>
>> Luigi
>>
>>
>> 2018-02-08 14:29 GMT+01:00 Ata Annamamedov :
>>
>>> Dear Luigi,
>>> will it break DB files compatibility then?
>>> Maybe it is better to have such dramatic change before v3.0 is out (fix
>>> it while moving from v2.x to 3.0), to make migration to next 3.X versions
>>> smoother?
>>>
>>>
>>> On Tuesday, February 6, 2018 at 1:46:53 PM UTC+5, Luigi Dell'Aquila
>>> wrote:
>>>>
>>>> Hi Chris,
>>>>
>>>> Yes, it's something we already considered. We couldn't manage to
>>>> refactor it in v 3.0 just for a matter of priorities, but I can tell you
>>>> that we will do it soon
>>>>
>>>> Thanks
>>>>
>>>> Luigi
>>>>
>>>> 2018-02-06 2:18 GMT+01:00 cm-perrs :
>>>>
>>>>> Hi,
>>>>>
>>>>> We are using OrientDB as document database in plocal mode. Classes are
>>>>> schema-mixed. We manage cluster selection by some record fields such as
>>>>> timestamp, using doc.save(clusterName).
>>>>>
>>>>> When looking inside cluster PCL files I find that every record has the
>>>>> class name as a string. This has a massive impact on the size of the file
>>>>> when the record is small.
>>>>>
>>>>> Why is class name saved with every record? The cluster belongs to the
>>>>> class by oClass.addCluster(clusterName), so maybe the class name in
>>>>> the record is redundant?
>>>>>
>>>>> Thanks, Chris
>>>>>
>>>>> --
>>>>>
>>>>> ---
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups "OrientDB" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>>> an email to orient-databa...@googlegroups.com.
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>
>>>>
>>>> --
>>>
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "OrientDB" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to orient-databa...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] Class name stored in every record in cluster PCL file

[Luigi Dell'Aquila]

Hi Ata,

It will be a different format, but we will keep backward compatibility.
It's pretty hard to do it now, as it's not a trivial change and we are
close to the release

Thanks

Luigi


2018-02-08 14:29 GMT+01:00 Ata Annamamedov :

> Dear Luigi,
> will it break DB files compatibility then?
> Maybe it is better to have such dramatic change before v3.0 is out (fix it
> while moving from v2.x to 3.0), to make migration to next 3.X versions
> smoother?
>
>
> On Tuesday, February 6, 2018 at 1:46:53 PM UTC+5, Luigi Dell'Aquila wrote:
>>
>> Hi Chris,
>>
>> Yes, it's something we already considered. We couldn't manage to refactor
>> it in v 3.0 just for a matter of priorities, but I can tell you that we
>> will do it soon
>>
>> Thanks
>>
>> Luigi
>>
>> 2018-02-06 2:18 GMT+01:00 cm-perrs :
>>
>>> Hi,
>>>
>>> We are using OrientDB as document database in plocal mode. Classes are
>>> schema-mixed. We manage cluster selection by some record fields such as
>>> timestamp, using doc.save(clusterName).
>>>
>>> When looking inside cluster PCL files I find that every record has the
>>> class name as a string. This has a massive impact on the size of the file
>>> when the record is small.
>>>
>>> Why is class name saved with every record? The cluster belongs to the
>>> class by oClass.addCluster(clusterName), so maybe the class name in the
>>> record is redundant?
>>>
>>> Thanks, Chris
>>>
>>> --
>>>
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "OrientDB" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to orient-databa...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] Exception on create FullText LUCENE index from console (and from JAVA API)

[Luigi Dell'Aquila]

Hi Maxim,

Which OrientDB version are you using?
Do you have a deterministic way to reproduce the problem?

Thanks

Luigi

2018-02-06 13:36 GMT+01:00 Maxim Nikolaev :

> 2018-02-06 09:45:28:097 FINE  {db=newdb17122017} Read record #367:465922
> v.3 size=142 bytes (thread=36 tx=false) [OEnterpriseLocalPaginatedStorage]
> 2018-02-06 09:45:28:097 FINE  {db=newdb17122017} Read record #367:465923
> v.2 size=142 bytes (thread=36 tx=false) 
> [OEnterpriseLocalPaginatedStorage]$ANSI{green
> {db=newdb17122017}} *Error during read of record*
> *com.orientechnologies.orient.core.exception.ODatabaseException: Database
> 'plocal:/media/newdb/HD/orient/databases/newdb17122017' is closed*
> DB name="newdb17122017"
> at com.orientechnologies.orient.core.db.document.
> ODatabaseDocumentTx.checkOpeness(ODatabaseDocumentTx.java:3145)
> at com.orientechnologies.orient.core.db.document.
> ODatabaseDocumentTx.getMetadata(ODatabaseDocumentTx.java:837)
> at com.orientechnologies.orient.core.db.document.
> ODatabaseDocumentTx.executeReadRecord(ODatabaseDocumentTx.java:2058)
> at com.orientechnologies.orient.core.tx.OTransactionNoTx.
> loadRecord(OTransactionNoTx.java:98)
> at com.orientechnologies.orient.core.db.document.
> ODatabaseDocumentTx.load(ODatabaseDocumentTx.java:1766)
> at com.orientechnologies.orient.core.db.document.
> ODatabaseDocumentTx.load(ODatabaseDocumentTx.java:102)
> at com.orientechnologies.orient.core.iterator.
> OIdentifiableIterator.readCurrentRecord(OIdentifiableIterator.java:300)
> at com.orientechnologies.orient.core.iterator.
> ORecordIteratorCluster.hasNext(ORecordIteratorCluster.java:141)
> at com.orientechnologies.orient.core.index.OIndexAbstract.
> indexCluster(OIndexAbstract.java:1025)
> at com.orientechnologies.orient.core.index.OIndexAbstract.
> fillIndex(OIndexAbstract.java:539)
> at com.orientechnologies.orient.core.index.OIndexAbstract.
> create(OIndexAbstract.java:250)
> at com.orientechnologies.lucene.index.OLuceneIndexNotUnique.
> create(OLuceneIndexNotUnique.java:250)
> at com.orientechnologies.lucene.index.OLuceneIndexNotUnique.
> create(OLuceneIndexNotUnique.java:51)
> at com.orientechnologies.orient.core.index.OIndexManagerShared.
> createIndex(OIndexManagerShared.java:169)
> at com.orientechnologies.orient.core.index.OIndexManagerProxy.
> createIndex(OIndexManagerProxy.java:87)
> at com.orientechnologies.orient.core.metadata.schema.
> OClassImpl.createIndex(OClassImpl.java:1897)
> at com.orientechnologies.orient.core.sql.
> OCommandExecutorSQLCreateIndex.execute(OCommandExecutorSQLCreateIndex
> .java:269)
> at com.orientechnologies.orient.core.sql.
> OCommandExecutorSQLDelegate.execute(OCommandExecutorSQLDelegate.java:74)
> at com.orientechnologies.orient.core.storage.impl.local.
> OAbstractPaginatedStorage.executeCommand(OAbstractPaginatedStorage.
> java:3208)
> at com.orientechnologies.orient.core.storage.impl.local.
> OAbstractPaginatedStorage.command(OAbstractPaginatedStorage.java:3146)
> at com.orientechnologies.orient.core.command.
> OCommandRequestTextAbstract.execute(OCommandRequestTextAbstract.java:69)
> at com.orientechnologies.orient.server.network.protocol.
> binary.ONetworkProtocolBinary.command(ONetworkProtocolBinary.java:1529)
> at com.orientechnologies.orient.server.network.protocol.
> binary.ONetworkProtocolBinary.executeRequest(ONetworkProtocolBinary.java:
> 646)
> at com.orientechnologies.orient.server.network.protocol.
> binary.ONetworkProtocolBinary.sessionRequest(ONetworkProtocolBinary.java:
> 384)
> at com.orientechnologies.orient.server.network.protocol.
> binary.ONetworkProtocolBinary.execute(ONetworkProtocolBinary.java:207)
> at com.orientechnologies.common.thread.OSoftThread.run(
> OSoftThread.java:77)
>
> 2018-02-06 09:45:28:121 FINE  {db=newdb17122017} Creating Lucene index in
> 'RAMDirectory@2ac7f870 lockFactory=org.apache.lucene.store.
> SingleInstanceLockFactory@55a15a1'... [OLuceneFullTextIndexEngine]
> 2018-02-06 09:45:28:122 FINE  {db=newdb17122017} C*reating Lucene index
> in 'RAMDirectory@133b0946
> lockFactory=org.apache.lucene.store.SingleInstanceLockFactory@12daa33f'...
> [OLuceneFullTextIndexEngine]*
> *2018-02-06 09:45:28:447 INFO  {db=newdb17122017} --> OK, indexed
> 22,050,364 items in 3,575,172 ms [OIndexRebuildOutputListener]$ANSI{green
> {db=newdb17122017}} Exception during index '_Place.address' creation*
> *java.lang.NullPointerException*
> at com.orientechnologies.orient.core.iterator.
> ORecordIteratorCluster.hasNext(ORecordIteratorCluster.java:145)
> at com.orientechnologies.orient.core.index.OIndexAbstract.
> indexCluster(OIndexAbstract.java:1025)
> at com.orientechnologies.orient.core.index.OIndexAbstract.
> fillIndex(OIndexAbstract.java:539)
> at com.orientechnologies.orient.core.index.O

Re: [orientdb] Class name stored in every record in cluster PCL file

[Luigi Dell'Aquila]

Hi Chris,

Yes, it's something we already considered. We couldn't manage to refactor
it in v 3.0 just for a matter of priorities, but I can tell you that we
will do it soon

Thanks

Luigi

2018-02-06 2:18 GMT+01:00 cm-perrs :

> Hi,
>
> We are using OrientDB as document database in plocal mode. Classes are
> schema-mixed. We manage cluster selection by some record fields such as
> timestamp, using doc.save(clusterName).
>
> When looking inside cluster PCL files I find that every record has the
> class name as a string. This has a massive impact on the size of the file
> when the record is small.
>
> Why is class name saved with every record? The cluster belongs to the
> class by oClass.addCluster(clusterName), so maybe the class name in the
> record is redundant?
>
> Thanks, Chris
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] ODB 3.X Vertex Inheritance

[Luigi Dell'Aquila]

Hi Robert,

That's correct, but I understand your concern, probably having an
additional method like createVertexClass(name, superclass), that also
checks that the supeclass is a vertex class, could be convenient. We will
consider it in the near future

Thanks

Luigi


2018-01-29 16:13 GMT+01:00 Robert Bergstrom :

> From the documentation here
> , the you
> create a new vertex class (a subclass of V) by calling "createVertexClass".
> How do you create a subclass of your new vertex class? I've tried using the
> "createClass" method specifying the subclass. It works without exception,
> but I wanted to verity this was the correct way. Looking at the OSchema
> methods, vertexes are not mentioned at all, so a bit confusing.
>
> Am I on the right path? What did I miss?
>
> TIA
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] ODocument in 3.x - can we still use it for missing method on OElement

[Luigi Dell'Aquila]

Hi Harish,

Good point, there is a chance that some methods that we did not expose on
the public interface are indeed useful as public API.
Please let us know which methods you need, we are open to evaluate them

Thanks

Luigi

2018-01-25 20:19 GMT+01:00 Harish :

> In the Orient 3.x user guide, we have the following guideline:
>
>
> *Attention: until v 2.2 the Document API relied on ODocument class only.
> ODocument is still there as the main implementation of OElement, but please
> don't use it directly, always use OElement instead*
> This is fine for most scenarios - but what about methods that cannot be
> reached through OElement? In such cases, is it OK to still cast to
> ODocument in 3.x? A simple case where this applies is the getDirtyFields()
> method on ODocument.
>
>
> Thanks,
> Harish.
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] Re: ODB 3.0 SQL UPDATE - No more ADD|PUT?

[Luigi Dell'Aquila]

Hi Eric,

The UPDATE SET syntax is allowed also in v 2.2.x, but the || operator is a
new addition and won't be backported to 2.2

Thanks

Luigi


2018-01-20 17:34 GMT+01:00 Eric24 :

> Thanks Luigi; makes perfect sense. Is this syntax also supported on 2.2.x?
>
> On Tuesday, January 2, 2018 at 2:23:32 AM UTC-6, Luigi Dell'Aquila wrote:
>>
>> Hi Eric,
>>
>> The alternatives are:
>>
>>
>> PUT: just use dot notation
>>
>> UPDATE ADoc PUT aMap = "aKey", "aValue"
>>
>> can be written as
>>
>> UPDATE ADoc SET aMap.aKey = "aValue"
>> or
>> UPDATE ADoc SET aMap["aKey"] = "aValue"
>>
>>
>> ADD: use array concatenation ||
>>
>> UPDATE ADoc PUT aList = "aValue"
>>
>> can be written as
>>
>> UPDATE ADoc SET aList = aList || "aValue"
>> or
>> UPDATE ADoc SET aList =  "aValue" || aList
>> depending on where you want to add the value (first or last element of
>> the list). For sets it does not make any difference of course
>>
>> For a full reference see http://orientdb.com/docs/3
>> .0.x/sql/SQL-Syntax.html
>>
>> Thanks
>>
>> Luigi
>>
>>
>> 2018-01-02 7:32 GMT+01:00 :
>>
>>> Hi,
>>>
>>> you can take a look at these links:
>>>
>>> *OrientDB 3.0 Release Notes: *https://github.com/orie
>>> ntechnologies/orientdb/wiki/OrientDB-3.0-Release-Notes
>>>
>>> *OrientDB 2.2 Release Notes: *https://github.com/orie
>>> ntechnologies/orientdb/wiki/OrientDB-2.2-Release-Notes
>>>
>>> Here you can see all the differences / enhancement.
>>>
>>> Hope it helps
>>>
>>> Regards,
>>>
>>> Michela
>>>
>>> --
>>>
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "OrientDB" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to orient-databa...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] Unwanted fields are returned in sql queries from Function

[Luigi Dell'Aquila]

Hi Ashwini,

Unfortunately in v 2.2 there is no way to suppress such information
(because of how data are processed when sent on the network).
We already addressed this problem in v 3.0, that will be released in a few
days. If you want to try it now, you can download the RC1 here
http://orientdb.com/orientdb-labs/

Thanks

Luigi

2018-01-15 0:37 GMT+01:00 Ashwini. Kumar :

> Hi,
> I created a function like this
>
> 
> def attractions = orient.getDatabase().query("select @rid, Type, Name
> from Attractions");
> return attractions.getClass();
> 
>
> All I was expecting to get back was rid, type and Name.  Instead I am
> getting a lot of other attributes like @version , @type, @rid, @fieldTypes.
>
>
> Also, this @rid attribute seems wrong. It starts with a negative number
> ("#-2:0")
>
> These additional unwanted attributes are complicating my middleware and
> frontend.   Can we just suppress them at the funtion level?
>
> thanks,
> Ashwini
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] Result sets not closing in 3.0RC1?

[Luigi Dell'Aquila]

Hi Tielman

The result sets are supposed to properly close when you do close(), if it's
not the case, it could be related to some internals (eg. subqueries). Do
you have a test case to reproduce the problem?

Thanks

Luigi


2018-01-05 22:30 GMT+01:00 Tielman Van Vleck :

> Am I doing something wrong or is it possible OResultSets in 3.0RC1 aren't
> always released when you call .close()? I believe I am calling it on every
> result set created, yet am still blowing up:
>
> 2018-01-05 14:48:59:848 WARNI {db=phenlp_rels} This database instance has
> 10 open command/query result sets, please make sure you close them with
> OResultSet.close()
>
> 2018-01-05 14:48:59:866 WARNI {db=phenlp_rels} This database instance has
> 20 open command/query result sets, please make sure you close them with
> OResultSet.close()
>
> 2018-01-05 14:48:59:882 WARNI {db=phenlp_rels} This database instance has
> 30 open command/query result sets, please make sure you close them with
> OResultSet.close()
>
> ...
>
> 2018-01-05 15:20:29:195 WARNI {db=phenlp_rels} This database instance has
> 10410 open command/query result sets, please make sure you close them with
> OResultSet.close()
>
> 2018-01-05 15:20:29:195 WARNI {db=phenlp_rels} This database instance has
> 10410 open command/query result sets, please make sure you close them with
> OResultSet.close()
>
> 2018-01-05 15:20:32:591 WARNI {db=phenlp_rels} This database instance has
> 10410 open command/query result sets, please make sure you close them with
> OResultSet.close()java.lang.OutOfMemoryError: GC overhead limit exceeded
>
> Dumping heap to java_pid21078.hprof ...
>
> Heap dump file created [3026507582 <(302)%20650-7582> bytes in 16.011
> secs]
>
> Exception in thread 'OrientDB WAL Flush Task (phenlp_rels)'
>
> java.lang.OutOfMemoryError: GC overhead limit exceeded
>
> at com.orientechnologies.orient.core.storage.impl.local.
> paginated.wal.OLogSegmentV2.preparePageForFlush(OLogSegmentV2.java:275)
>
> at com.orientechnologies.orient.core.storage.impl.local.
> paginated.wal.OLogSegmentV2.access$500(OLogSegmentV2.java:30)
>
> at com.orientechnologies.orient.core.storage.impl.local.
> paginated.wal.OLogSegmentV2$WriteTask.run(OLogSegmentV2.java:160)
>
> at com.orientechnologies.common.concur.executors.SubExecutorService$
> RunnableTask.run(SubExecutorService.java:296)
>
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
>
> at java.util.concurrent.ScheduledThreadPoolExecutor$
> ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
>
> at java.util.concurrent.ScheduledThreadPoolExecutor$
> ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
>
> at java.util.concurrent.ThreadPoolExecutor.runWorker(
> ThreadPoolExecutor.java:1149)
>
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(
> ThreadPoolExecutor.java:624)
>
> at java.lang.Thread.run(Thread.java:748)
>
> I assumed I was missing one, but in the debugger, it appears they still
> persist even after calling .close() - of course that could be just what is
> in my client vs. on the server.
>
> Many thanks,
> Tielman
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] Re: ODB 3.0 SQL UPDATE - No more ADD|PUT?

[Luigi Dell'Aquila]

Hi Eric,

The alternatives are:


PUT: just use dot notation

UPDATE ADoc PUT aMap = "aKey", "aValue"

can be written as

UPDATE ADoc SET aMap.aKey = "aValue"
or
UPDATE ADoc SET aMap["aKey"] = "aValue"


ADD: use array concatenation ||

UPDATE ADoc PUT aList = "aValue"

can be written as

UPDATE ADoc SET aList = aList || "aValue"
or
UPDATE ADoc SET aList =  "aValue" || aList
depending on where you want to add the value (first or last element of the
list). For sets it does not make any difference of course

For a full reference see http://orientdb.com/docs/3.0.x/sql/SQL-Syntax.html

Thanks

Luigi


2018-01-02 7:32 GMT+01:00 :

> Hi,
>
> you can take a look at these links:
>
> *OrientDB 3.0 Release Notes: *https://github.com/
> orientechnologies/orientdb/wiki/OrientDB-3.0-Release-Notes
>
> *OrientDB 2.2 Release Notes: *https://github.com/
> orientechnologies/orientdb/wiki/OrientDB-2.2-Release-Notes
>
> Here you can see all the differences / enhancement.
>
> Hope it helps
>
> Regards,
>
> Michela
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] Re: SELECT QUERY ERROR

[Luigi Dell'Aquila]

Hi Krishna,

How can we reproduce this problem? Do you have a deterministic way to do it?

Thanks

Luigi

2017-12-23 20:23 GMT+01:00 Krishna Chandra Prajapati 
:

> Hello Michelle,
>
> I'm using the latest version 3.0
>
> Regards,
> Krishna
>
> On Dec 23, 2017 9:48 AM,  wrote:
>
>> Hi,
>>
>> what version are you using?
>>
>> Thanks
>>
>> Regards,
>>
>> Michela
>>
>> --
>>
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "OrientDB" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to orient-database+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] OrientDB V3.0RC Load Script Error

[Luigi Dell'Aquila]

Hi Krishna,

Could you please post the script?

Thanks

Luigi

2017-12-20 7:00 GMT+01:00 Krishna Chandra Prajapati :

> Hello Guys,
>
> I'm getting the below error while loading data into class.
>
> orientdb {db=netdevices}> LOAD SCRIPT '/home/krishna/ag1.osql';
>
> Loading script /home/krishna/ag1.osql...
> Error: 
> com.orientechnologies.orient.enterprise.channel.binary.OResponseProcessingException:
> Exception during response processing
>
> Error: java.lang.NullPointerException
>
> This same script file was running successfully on milestone M2
>
> Regards,
> Krishna
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] Show name with vertex

[Luigi Dell'Aquila]

Hi Krishna,

In the graph panel, on the left, you have to select the edit tab (the
second one), then you can choose the label you want to display on the graph
from the vertex attributes

Thanks

Luigi

2017-12-16 6:01 GMT+01:00 Krishna Chandra Prajapati :

>
> Hello,
>
> I'm looking for a way to display name with vertices. Is it possible with
> OrientDB Studio ? If not, how i can achieve it.
>
> Any help is highly appreciated.
>
> Regards,
> Krishna
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] OrientDB Web Interface timeout

[Luigi Dell'Aquila]

Hi Krishna,

which version? In v 3.0 SNAPSHOT you can add this parameter to the command
line: -Dnetwork.http.sessionExpireTimeout=

In v 2.2 you should not have a session expire problem at all...

Thanks

Luigi

2017-12-15 12:20 GMT+01:00 Krishna Chandra Prajapati 
:

> Hello,
>
> The web interface for OrientDB timeout so fast.
>
> How we can increase the timeout ?
>
> Regards,
> Krishna
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] Arrange Graph

[Luigi Dell'Aquila]

Hi Krishna,

Unfortunately right now there is no option to arrange graph display as a
tree, the visualization uses a force based algorithm

Thanks

Luigi


2017-12-14 7:14 GMT+01:00 Krishna Chandra Prajapati :

> Hello,
>
> I'm a newbie for OrientDB.
>
> I would like to know, how i can arrange graph in tree format within
> OrientDB Studio. I don't want to do manually every time. Is there any
> automated way, so that the graph is shown in tree format.
>
> Regards,
> Krishna
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] Re: Select * from V error

[Luigi Dell'Aquila]

Hi Raymond,

You should see some logs in the server console, probably there is something
related to this error that can help me understand where it exactly is

Thanks

Luigi


2017-12-05 15:46 GMT+01:00 Raymond Willems :

> What's a stack trace?
>
> Am Dienstag, 21. November 2017 14:56:32 UTC+1 schrieb Luigi Dell'Aquila:
>>
>> Hi Raymond,
>>
>> Ok, it's quite unlikely that the problem is in the SQL executor (try the
>> same query in the query browser to be sure), I think the problem is in the
>> serialization of the result for the graph rendering.
>> Do you have a chance to send me a stack trace to understand where the
>> exception is thrown exactly?
>>
>> Thanks
>>
>> Luigi
>>
>> 2017-11-21 14:45 GMT+01:00 Raymond Willems :
>>
>>> I am using the Graph section in the Studio. Due to confidentiality, I
>>> cannot share the db. But it appears with a complex document with more than
>>> 300 attributes.
>>>
>>>
>>> Am Dienstag, 19. September 2017 16:24:53 UTC+2 schrieb Raymond Willems:
>>>>
>>>> Dear Community,
>>>>
>>>> when I do "Select * from V", I get the error
>>>>
>>>> java.lang.ClassCastException: java.lang.String cannot be cast to
>>>> com.orientechnologies.orient.core.db.record.OIdentifiable
>>>>
>>>> I'm using the latest version.
>>>>
>>>> Any ideas?
>>>>
>>> --
>>>
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "OrientDB" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to orient-databa...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] Re: Select * from V error

[Luigi Dell'Aquila]

Hi Raymond,

Ok, it's quite unlikely that the problem is in the SQL executor (try the
same query in the query browser to be sure), I think the problem is in the
serialization of the result for the graph rendering.
Do you have a chance to send me a stack trace to understand where the
exception is thrown exactly?

Thanks

Luigi

2017-11-21 14:45 GMT+01:00 Raymond Willems :

> I am using the Graph section in the Studio. Due to confidentiality, I
> cannot share the db. But it appears with a complex document with more than
> 300 attributes.
>
>
> Am Dienstag, 19. September 2017 16:24:53 UTC+2 schrieb Raymond Willems:
>>
>> Dear Community,
>>
>> when I do "Select * from V", I get the error
>>
>> java.lang.ClassCastException: java.lang.String cannot be cast to
>> com.orientechnologies.orient.core.db.record.OIdentifiable
>>
>> I'm using the latest version.
>>
>> Any ideas?
>>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] Adding and Removing Clusters from a Class

[Luigi Dell'Aquila]

Hi Eric,

Moving records from a cluster to another is not supported, because
re-calculating link references is a very expensive operation.
There is a MOVE VERTEX command that (as you can guess) is specific to
vertices, it takes into consideration edges and re-attaches them correctly

Thanks

Luigi


2017-11-21 5:11 GMT+01:00 Eric24 :

> It's easy to add more storage capacity to a Class by simple creating and
> adding a new Cluster to that Class. There is also a way to remove a Cluster
> from a Class, but this doesn't "redistribute" the data in that Cluster to
> other Clusters in the Class. Is that function supported "automatically"
> (i.e. in any way other than to write code to scan through the RIDs in the
> removed Class and create new records in one of the remaining classes)?
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] Re: Concurrency during UPDATE ADD operation

[Luigi Dell'Aquila]

Hi Eric,

all these operations are atomic because of MVCC/optimistic locking, ie. if
you do two INCREMENT on the same record in concurrency, one of the two will
fail. This is why I suggested a commit/retry, just to let OrientDB manage
the retry for you without any further effort at application level

Thanks

Luigi


2017-11-15 19:37 GMT+01:00 Eric24 :

> Hmmm. I had thought that ADD and PUT operations would be atomic? If they
> are not, what about INCREMENT? The docs certainly suggest that INCREMENT is
> atomic (it doesn't make the same claim about ADD or PUT, but I just assumed
> they would be).
>
> On Monday, November 13, 2017 at 2:19:43 AM UTC-6, Luigi Dell'Aquila wrote:
>>
>> Hi Eric,
>>
>> UPDATE ADD is just a normal record change, the record is completely
>> overwritten and the version is increased, so you will have a normal
>> ConcurrentModificationException if two operations happen at the same
>> time.
>> My general advice in these cases is to use a commit/retry strategy. If
>> you are doing it via SQL, just do
>>
>> BEGIN;
>> UPDATE... ADD...;
>> COMMIT RETRY 10;
>>
>> This way you will avoid lock overheads in most of the cases and you will
>> have a retry only when it's strictly needed.
>>
>> I hope it helps
>>
>> Thanks
>>
>> Luigi
>>
>>
>> 2017-11-12 19:11 GMT+01:00 Eric24 :
>>
>>> To follow up on this, would LOCK RECORD be necessary? If I didn't want
>>> to incur the lock overhead, is there a way to set the concurrency strategy
>>> on the transaction (i.e. normally use "version", but select "automerge" for
>>> this operation)?
>>>
>>>
>>> On Saturday, November 11, 2017 at 6:53:27 PM UTC-6, Eric24 wrote:
>>>>
>>>> If two clients perform an UPDATE ADD on the same record at the same
>>>> time, do both ADD operations always succeed without an exception (since
>>>> they can't conflict with each other by definition)? What about two PUT
>>>> operations, with different/non-conflicting keys?
>>>>
>>> --
>>>
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "OrientDB" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to orient-databa...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] Lightweight Edges not maintained when using SQL DELETE VERTEX

[Luigi Dell'Aquila]

Thank you very much, in case you want to track the resolution of this
problem, you can watch this:
https://github.com/orientechnologies/orientdb/issues/new

Thanks

Luigi

2017-11-14 20:30 GMT+01:00 Eric24 :

> Steps to produce bug:
>
>1. Enable Lightweight Edges
>2. CREATE CLASS SimpleV EXTENDS V
>3. CREATE CLASS SimpleE EXTENDS E
>4. INSERT INTO SimpleV CONTENT {"name":"A"}  // this is #25:0
>5. INSERT INTO SimpleV CONTENT {"name":"B"}  // this is #25:1
>6. CREATE EDGE SimpleE FROM #25:0 TO #25:1
>7. SELECT FROM SimpleE  // empty result, provides that Lightweight
>Edge was used
>8. DELETE VERTEX #25:1
>9. SELECT FROM SimpleV  // returns #25:0, with OUT still showing link
>to #25:1
>
>
>
> On Tuesday, November 14, 2017 at 2:18:36 AM UTC-6, Luigi Dell'Aquila wrote:
>>
>> Hi Eric,
>>
>> The main problem with lightweight edges is that they do not have an
>> identity, so they don't "physically" exist.
>> The big disadvantages are that:
>> - you cannot point to a single lightweight edge by RID
>> - you cannot count them, eg. SELECT FROM E will return a wrong result
>>
>> The DELETE VERTEX is supposed to work fine though, if you have a test
>> case that proves the problem please submit it, I'll check it asap
>>
>> Thanks
>>
>> Luigi
>>
>>
>> 2017-11-13 19:21 GMT+01:00 Eric24 :
>>
>>> It has been mentioned many times that using lightweight edges is "more
>>> difficult" with SQL. Can anyone provide specific examples of when this is
>>> true (i.e. what are the SQL issues created by using them)?
>>>
>>> I ask because just about everything I've tried with lightweight edges
>>> works the same way with regular edges (even SELECTs that return linked
>>> records using both kinds of edges in a single query).
>>>
>>> The one thing I've found that doesn't work with lightweight edges (which
>>> is a bit of a surprise to me) is that the links are not "cleaned up" when
>>> doing a DELETE VERTEX operation (i.e. "broken" links are left in the
>>> remaining vertex records). Is this an expected behavior? If so, it should
>>> probably be listed in the documentation as one of the cons to lightweight
>>> edges. If not, what is the appropriate way to delete a vertex record while
>>> ensuring that links to the deleted record are removed from the remaining
>>> records?
>>>
>>> --
>>>
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "OrientDB" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to orient-databa...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] Lightweight Edges not maintained when using SQL DELETE VERTEX

[Luigi Dell'Aquila]

Hi Eric,

The main problem with lightweight edges is that they do not have an
identity, so they don't "physically" exist.
The big disadvantages are that:
- you cannot point to a single lightweight edge by RID
- you cannot count them, eg. SELECT FROM E will return a wrong result

The DELETE VERTEX is supposed to work fine though, if you have a test case
that proves the problem please submit it, I'll check it asap

Thanks

Luigi


2017-11-13 19:21 GMT+01:00 Eric24 :

> It has been mentioned many times that using lightweight edges is "more
> difficult" with SQL. Can anyone provide specific examples of when this is
> true (i.e. what are the SQL issues created by using them)?
>
> I ask because just about everything I've tried with lightweight edges
> works the same way with regular edges (even SELECTs that return linked
> records using both kinds of edges in a single query).
>
> The one thing I've found that doesn't work with lightweight edges (which
> is a bit of a surprise to me) is that the links are not "cleaned up" when
> doing a DELETE VERTEX operation (i.e. "broken" links are left in the
> remaining vertex records). Is this an expected behavior? If so, it should
> probably be listed in the documentation as one of the cons to lightweight
> edges. If not, what is the appropriate way to delete a vertex record while
> ensuring that links to the deleted record are removed from the remaining
> records?
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] Efficiency of delete from manual index using @rid (And possible bug in 2.2.29)

[Luigi Dell'Aquila]

Hi Eric,

The index is optimized to do lookups by key, not by RID, so I'd say the
answer is no, it won't be efficient.

About the SELECT, it's not an expected behavior, I'll check it

Thanks

Luigi


2017-11-13 5:05 GMT+01:00 Eric24 :

> While it's easy enough to delete rows from a manual index by @rid
> (using DELETE FROM INDEX:testindex WHERE rid = #10:4), is the index
> structured in a way that this is efficient? In other words, does ODB have
> to essentially read through the entire index to find all of the occurrences
> of @rid #10:4 to delete or is there any sort of optimization in place to
> prevent this? I'm concerned about using this approach on manual indexed
> that could have millions of records.
>
> Also, I noticed that doing something like SELECT key FROM INDEX:textindex
> (WHERE...) doesn't work if the index has a composite key (works fine on
> simple keys). A bug or is there a different syntax that will work with
> composite keys?
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] Syntax for ADD operation with collection of maps?

[Luigi Dell'Aquila]

Hi Eric,

The correct syntax should be just

UPDATE x ADD list =  {"ddd":444, "dd":44}

If it doesn't work, I'd say it's a bug. Could you please report in issue?

Thanks

Luigi


2017-11-12 19:15 GMT+01:00 Eric24 :

> I can't figure out the proper SQL syntax for adding a map to a collection.
> For example, the record property "list" is "[{"aaa":, "aa":11},
> {"bbb":222, "bb":22}, {"ccc":333, "cc":33}]. I can easily create and query
> this property, but how do I add {"ddd":444, "dd":44} to this collection?
> UPDATE #20:0 ADD list = {"ddd":444, "dd":44} does not error out, but the
> result is that '44' is added to the collection. All other syntax forms I've
> tried result in various errors.
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] Re: Concurrency during UPDATE ADD operation

[Luigi Dell'Aquila]

Hi Eric,

UPDATE ADD is just a normal record change, the record is completely
overwritten and the version is increased, so you will have a normal
ConcurrentModificationException if two operations happen at the same time.
My general advice in these cases is to use a commit/retry strategy. If you
are doing it via SQL, just do

BEGIN;
UPDATE... ADD...;
COMMIT RETRY 10;

This way you will avoid lock overheads in most of the cases and you will
have a retry only when it's strictly needed.

I hope it helps

Thanks

Luigi


2017-11-12 19:11 GMT+01:00 Eric24 :

> To follow up on this, would LOCK RECORD be necessary? If I didn't want to
> incur the lock overhead, is there a way to set the concurrency strategy on
> the transaction (i.e. normally use "version", but select "automerge" for
> this operation)?
>
>
> On Saturday, November 11, 2017 at 6:53:27 PM UTC-6, Eric24 wrote:
>>
>> If two clients perform an UPDATE ADD on the same record at the same time,
>> do both ADD operations always succeed without an exception (since they
>> can't conflict with each other by definition)? What about two PUT
>> operations, with different/non-conflicting keys?
>>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] Query Performance Issue

[Luigi Dell'Aquila]

No, unfortunately there is no such setting for now...

Thanks

Luigi


2017-11-04 6:57 GMT+01:00 shrikant pachauri :

> thanks well thats what I thought.
>
> one more thing while using the DB.command() to execute query can we
> externally set when to commit data into database like gremlin. In gremlin
> we can specify after insertion of how many records the database should
> commit. May be that can help me in getting better performance
>
>
>
> On Friday, November 3, 2017 at 2:08:15 PM UTC+5:30, Luigi Dell'Aquila
> wrote:
>>
>> Hi Shrikant,
>>
>> There are at least two factors that can impact performance here:
>>
>> - OrientDB does some caching of SQL statements, so the first time you
>> execute a query it has to be parsed from scratch, while the second time you
>> will have the AST in cache
>> - there is a layer, called diskCache, that keeps recently used data in
>> memory, so that you don't have to access disk to query it, probably this is
>> the part that impacts your case the most
>>
>> Thanks
>>
>> Luigi
>>
>>
>> 2017-11-03 9:00 GMT+01:00 shrikant pachauri :
>>
>>>
>>> Greeting
>>>
>>> I am trying to insert say 10k vertices in graph DB. I am using a script
>>> file in javascript where I am using Orient DBs native query language. Now
>>> after creating a class from the vertices when i ran the query for the first
>>> time it takes me about 2.51s. Now if I ran the same query again it takes me
>>> about 0.92s to insert the 10k records.
>>>
>>> Now my question is this is there any sort of caching or some other
>>> mechanism which makes my execution of the second query faster than before.
>>> I have a perspective that May be it stored the compiled query of the first
>>> time and it does not need to compile the query next time in case it
>>> encounter the same query.
>>>
>>> Any help would be appreciated
>>>
>>> --
>>>
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "OrientDB" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to orient-databa...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] Query Performance Issue

[Luigi Dell'Aquila]

Hi Shrikant,

There are at least two factors that can impact performance here:

- OrientDB does some caching of SQL statements, so the first time you
execute a query it has to be parsed from scratch, while the second time you
will have the AST in cache
- there is a layer, called diskCache, that keeps recently used data in
memory, so that you don't have to access disk to query it, probably this is
the part that impacts your case the most

Thanks

Luigi


2017-11-03 9:00 GMT+01:00 shrikant pachauri :

>
> Greeting
>
> I am trying to insert say 10k vertices in graph DB. I am using a script
> file in javascript where I am using Orient DBs native query language. Now
> after creating a class from the vertices when i ran the query for the first
> time it takes me about 2.51s. Now if I ran the same query again it takes me
> about 0.92s to insert the 10k records.
>
> Now my question is this is there any sort of caching or some other
> mechanism which makes my execution of the second query faster than before.
> I have a perspective that May be it stored the compiled query of the first
> time and it does not need to compile the query next time in case it
> encounter the same query.
>
> Any help would be appreciated
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] Match query issue

[Luigi Dell'Aquila]

Hi Cyprien,

it's a bit hard (and long) for me to answer without a minimal dataset to
test, if you have a chance to provide one, I'll be happy to review the
queries

Thanks

Luigi

2017-10-30 19:04 GMT+01:00 Cyprien Gottstein :

> Greetings,
>
> OrientDB : Version 2.2.28
>
> I am facing a problem using OSQL MATCH,
>
> Basically, we have a query language which we translate into OSQL to query
> our OrientDB database.
> We have to do graph pattern matching and the MATCH statement seems
> perfectly appropriate for our needs (and you have all my thanks for adding
> that to OrientDB ! Sincerely.), however... it does not work.
>
> So first of all, is this the right way to use a while condition into the
> MATCH statement ?
>
> MATCH
> {class:Projection, as:a} -as_ontology_class-> {as:b},
> {class:owl_class, as:c, where:(ori = "http://purl.org/vso/ns#Bicycle"; )}
> <-isA- {class:owl_class, as:b, while:(true)}
> RETURN a
>
>
>
> What bothers me is that *"a"* may be directly linked to *"c"*, and
> sometimes it must pass through *"b"* to reach *"c"* . It works most of
> the time but i'm never really sure about the global method, if this should
> not be split into two queries.
> Example:
>
> projection (vertex) : P1, P2
> owl_class (vertex) : bicycle, bus, busOrCoach
>
> isA (edge) : Bus -isA-> BusOrCoach
> as_ontology_class (edge) : P1 -as_ontology_class-> bicycle, P2
> -as_ontology_class-> Bus
>
> If i use the following query :
> MATCH
> {class:Projection, as:a} -as_ontology_class-> {as:b},
> {class:owl_class, as:c, where:(ori IN ["http://purl.org/vso/ns#Bicycle";, "
> http://purl.org/vso/ns#BusOrCoach";] )} <-isA- {class:owl_class, as:b,
> while:(true)}
> RETURN a
>
>
>
> both P1 and P2 will be returned, isn't that strange ? OSQL made the
> assumption for me to link directly a and c. It is good to me because that
> is what i want but i can't help but wonder because this is not what i
> expected.
> Next, take the following dataset:
>
> Person (vertex) : A, B, C, D
> Name (property) : A.name = Alice, B.name = Bob, C.name = Charlie, D.name =
> Daniel
>
>
> knows (edge) :
> A -knows-> B,
> A -knows-> C,
> B -knows-> C,
> B -knows-> D,
> C -knows-> A,
> C -knows-> B,
> D -knows-> B
>
> With the following query :
> MATCH
> {class:Person, as:a} -knows-> {class:Person, as:b} -knows-> {class:Person,
> as:c, where:(name NOT IN ["Daniel"] )}
> RETURN a ) )
>
>
>
> I get no person matching even though i see the pattern A -knows-> B -
> knows-> C with C.name NOT IN ["Daniel"].
> Now, if i add a fifth person at the farest location possible from Daniel:
>
> Person (vertex) : A, B, C, D, E
> Name (property) : A.name = Alice, B.name = Bob, C.name = Charlie, D.name =
> Daniel, E.name = Ted
>
>
> knows (edge) :
> A -knows-> B,
> A -knows-> C,
> B -knows-> C,
> B -knows-> D,
> C -knows-> A,
> C -knows-> B,
> E -knows-> C
>
> Same query :
> MATCH
> {class:Projection, as:a} -knows-> {class:Projection, as:b} -knows-> {class
> :Projection, as:c, where:(name NOT IN ["Daniel"] )}
> RETURN a ) )
>
>
>
> For the E vertex there is no  Person called Daniel within a depth of two
> through the "knows" edge, still, the results are the same, no person
> matching.
> If i go back to the dataset without E and i change the "NOT IN" operator
> with "=" :
>
> MATCH
> {class:Person, as:a} -knows-> {class:Person, as:b} -knows-> {class:Person,
> as:c, where:(name != "Daniel" )}
> RETURN a ) )
>
>
>
> The query return A, B, C and D.
>
> Why does the use of a list have such impacts onto the query what am i
> missing ?
> If you take the very first query :
>
> MATCH
> {class:Projection, as:a} -as_ontology_class-> {as:b},
> {class:owl_class, as:c, where:(ori = "http://purl.org/vso/ns#Bicycle"; )}
> <-isA- {class:owl_class, as:b, while:(true)}
> RETURN a
>
>
>
> I have some cases where it fails or work depending the dataset with a
> runtime exception "Invalid pattern to match!" (line 668, version 2.2.28 in
> OMatchStatement)
> I do not know exactly if this has some impact on the execution but when i
> tried to execute in debug mode the query with pointbreaks into
> OMatchStatement i saw that the order of executionPlan.sortedEdges where
> inverted in the case of the query fails or succeed.
> executionPlan.sortedEdges in case of failure : [ { "out" : true, "edge" :
> "b->a" } , { "out" : false, "edge": "b->c" } ]
> executionPlan.sortedEdges in case of success : [ { "out" : true, "edge" :
> "b->c" } , { "out" : false, "edge" : "b->a" } ]
>
> I saw it was based on some estimated size of the roots entries so I tried
> to modify the dataset which fails to have the same sortedEdges ordering but
> i could not manage to change the order back, so no real clue on this. Also,
> after some tries i noticed that if i put a deliberately unsatisfiable
> clause on *"a" *the query will be executed properly:
>
> MATCH
> {class:Projection, as:a, where:(false = true)*} -as_ontology_class-> {as:b
> }, *this could be anything as long as i'm sure it will never be true.
> {class:owl_class,

Re: [orientdb] Is there really any reason to create a "generic" class?

[Luigi Dell'Aquila]

If you are not using graphs, then extending V is absolutely not needed.
Anyway, class hierarchies have negligible overhead, so you can live with it

Thanks

Luigi


2017-10-29 18:44 GMT+01:00 Eric24 :

> In other words, with ODB 2.2+ (and 3,0), is there really any downside to
> using the V superclass for all classes, even if the resulting "document"
> class will never be used in a graph context?
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] SQL SELECT that returns specific properties from linked classes

[Luigi Dell'Aquila]

Hi Eric,

With plain SELECT:

SELECT inV().vertexProp1, inV().vertexProp2, edgeProp1, edgeProp2 from (
select expand(outE("TheEdgeClass")) FROM V WHERE foo = ?
)

With MATCH:

MATCH
   {class:V, as: theRootNode, where:(foo = ?)}
.outE("TheEdgeClass"){as:theEdge} .inV() {as:firstLevel}
RETURN theEdge.prop1 as p1, theEdge.prop2 as p2, firstLevel.prop1, as p3,
firstLevel.prop2 as p4

Thanks

Luigi


2017-10-29 18:01 GMT+01:00 Eric24 :

> I'm looking for a suggestion on how to construct a SELECT statement that
> returns specific properties from linked classes.
>
> I have a V class that can have one or more identical V classes linked via
> standard E edges. What I'm trying to do is select the "root" V class and
> have the query return properties from the first level of linked V classes.
> Selecting the "root" V class is simple, and that query does include the
> "out_" object that contains the RIDs for the linked V classes, but I can't
> figure out how to actually get data from the linked V classes (without
> doing a second query, which I what I'm trying to avoid). I feel like this
> is dirt-simple, but I'm missing some detail.
>
> As a "bonus", it would go nice to optionally include specific properties
> from the link E edges, too.
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] Behavior of elements in EMBEDDEDLIST

[Luigi Dell'Aquila]

Hi Eric,

The syntax is following

CREATE PROPERTY ClassName.propertyName EMBEDDEDLIST EMBEDDEDMAP

but I see that in your list you have a mix of maps and sublists, so I'm
afraid it won't work...

Luigi


2017-10-26 15:27 GMT+02:00 Eric Lenington :

> Thanks for the quick response. I'm not familiar with that option. What's
> the syntax of the create property statement to do this?
>
> On Thu, Oct 26, 2017 at 8:25 AM, Luigi Dell'Aquila <
> luigi.dellaqu...@gmail.com> wrote:
>
>> Hi Eric,
>>
>> Try to define the property as EMBEDDEDMAP with LINKEDTYPE = EMBEDDEDMAP,
>> it should solve the problem
>>
>> Thanks
>>
>> Luigi
>>
>> 2017-10-26 4:37 GMT+02:00 Eric24 :
>>
>>> Using ODB 2.2.28, I have a simple Class that contains an EMBEDDEDLIST
>>> called "data". If I update "data" like this:
>>> UPDATE #12:4 SET data = [{"a":111}, {"b":222}, [{"c":555}, {"d":777}]]
>>>
>>> The result of then selecting "data" from the record is this:
>>> [{"@type":"d","@version":0,"a":111},{"@type":"d","@version":0,"b":222
>>> },[{"c":555},{"d":777}]]
>>>
>>> As you can see, "data" contains three elements, as expected, but why do
>>> the two elements that are standalone objects get @type and @version
>>> properties, while the element that is an array of objects element does not?
>>> And more specifically, I would prefer to avoid the standalone objects from
>>> being treated in this way.
>>>
>>> --
>>>
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "OrientDB" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to orient-database+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
>>
>> ---
>> You received this message because you are subscribed to a topic in the
>> Google Groups "OrientDB" group.
>> To unsubscribe from this topic, visit https://groups.google.com/d/to
>> pic/orient-database/Eo3cdN-DlMM/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> orient-database+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] Select Query issue

[Luigi Dell'Aquila]

Hi Shirkant,

Which version are you working with?
How did you do the insert?

Thanks

Luigi

2017-10-26 12:02 GMT+02:00 Shrikant Pachauri <
shrikant.pacha...@optimizory.com>:

> I am new to orient DB and trying the technology
> Actually i have inserted some records in the database. I want to query for
> a particular record with given value
> In my record I have id= Request ID-4
>
> now when i run query like
> select from Request where id='Request ID-4'
>
> it does not work while i Put the above command in the console while if I
> have data without hyphon(' - ') this works. Any clue where I am doing wrong?
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] Behavior of elements in EMBEDDEDLIST

[Luigi Dell'Aquila]

Hi Eric,

Try to define the property as EMBEDDEDMAP with LINKEDTYPE = EMBEDDEDMAP, it
should solve the problem

Thanks

Luigi

2017-10-26 4:37 GMT+02:00 Eric24 :

> Using ODB 2.2.28, I have a simple Class that contains an EMBEDDEDLIST
> called "data". If I update "data" like this:
> UPDATE #12:4 SET data = [{"a":111}, {"b":222}, [{"c":555}, {"d":777}]]
>
> The result of then selecting "data" from the record is this:
> [{"@type":"d","@version":0,"a":111},{"@type":"d","@version":0,"b":222},[{
> "c":555},{"d":777}]]
>
> As you can see, "data" contains three elements, as expected, but why do
> the two elements that are standalone objects get @type and @version
> properties, while the element that is an array of objects element does not?
> And more specifically, I would prefer to avoid the standalone objects from
> being treated in this way.
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] Query on double indexing

[Luigi Dell'Aquila]

Oh, sorry, you are trying to do a LIKE. Indexes cannot be used for LIKE
operations with left and right wildcars

Thanks

Luigi




2017-10-23 10:08 GMT+02:00 Luigi Dell'Aquila :

> Hi,
>
> The query seems to be correct, could you please post a simple SQL script
> to reproduce the exact case?
>
> Thanks
>
> Luigi
>
>
>
> 2017-10-21 10:42 GMT+02:00 :
>
>> Hai,
>>
>> METADATAPROPERTIESINOUT
>>
>> @rid
>> @class
>> @version
>> mobile_no
>> created_date
>> email_id
>> name
>> is_deleted
>> gender
>> network_id
>> store_customer
>> customer_has_appointment
>> customer_has_billing
>> customer_has_store_service
>> customer_has_preferred_stylest
>> customer_has_wallet_inventory
>> customer_has_wallet_activity
>> customer_has_customer_feedback
>> customer_has_activity
>> #260:103808
>> <http://192.168.1.40:2480/studio/index.html#/database/mio/browse/edit/260:103808>
>> customer 11 31 2017-10-14 17:17:34 h...@woor.com Santhosh false
>> male #25:2049
>> <http://192.168.1.40:2480/studio/index.html#/database/mio/browse/edit/25:2049>
>> #297:106317
>> <http://192.168.1.40:2480/studio/index.html#/database/mio/browse/edit/297:106317>
>> #351:15393
>> <http://192.168.1.40:2480/studio/index.html#/database/mio/browse/edit/351:15393>
>> #339:13080
>> <http://192.168.1.40:2480/studio/index.html#/database/mio/browse/edit/339:13080>
>> #302:18050
>> <http://192.168.1.40:2480/studio/index.html#/database/mio/browse/edit/302:18050>
>> #346:16985
>> <http://192.168.1.40:2480/studio/index.html#/database/mio/browse/edit/346:16985>
>> #443:420
>> <http://192.168.1.40:2480/studio/index.html#/database/mio/browse/edit/443:420>
>> #438:1198
>> <http://192.168.1.40:2480/studio/index.html#/database/mio/browse/edit/438:1198>
>> #280:37779
>> <http://192.168.1.40:2480/studio/index.html#/database/mio/browse/edit/280:37779>
>> #261:135035
>> <http://192.168.1.40:2480/studio/index.html#/database/mio/browse/edit/261:135035>
>>
>> we have index the *customer* vertex as* customer.network_id_mobile_no*
>>
>> i want to query on index like, *network_id = #25:2049
>> <http://192.168.1.40:2480/studio/index.html#/database/mio/browse/edit/25:2049>
>>  and mobile_no
>> like '%1131%'*
>>
>> Below i have wrong query, can u modify it as per my requirement,
>>
>> select from index:customer.network_id_mobile_no where key = [#25:2049,
>> '%31%']
>>
>> Thanks and Regards,
>> T.Pugazhararasan.
>>
>> --
>>
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "OrientDB" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to orient-database+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] Query on double indexing

[Luigi Dell'Aquila]

Hi,

The query seems to be correct, could you please post a simple SQL script to
reproduce the exact case?

Thanks

Luigi



2017-10-21 10:42 GMT+02:00 :

> Hai,
>
> METADATAPROPERTIESINOUT
>
> @rid
> @class
> @version
> mobile_no
> created_date
> email_id
> name
> is_deleted
> gender
> network_id
> store_customer
> customer_has_appointment
> customer_has_billing
> customer_has_store_service
> customer_has_preferred_stylest
> customer_has_wallet_inventory
> customer_has_wallet_activity
> customer_has_customer_feedback
> customer_has_activity
> #260:103808
> 
> customer 11 31 2017-10-14 17:17:34 h...@woor.com Santhosh false
> male #25:2049
> 
> #297:106317
> 
> #351:15393
> 
> #339:13080
> 
> #302:18050
> 
> #346:16985
> 
> #443:420
> 
> #438:1198
> 
> #280:37779
> 
> #261:135035
> 
>
> we have index the *customer* vertex as* customer.network_id_mobile_no*
>
> i want to query on index like, *network_id = #25:2049
> 
>  and mobile_no
> like '%1131%'*
>
> Below i have wrong query, can u modify it as per my requirement,
>
> select from index:customer.network_id_mobile_no where key = [#25:2049,
> '%31%']
>
> Thanks and Regards,
> T.Pugazhararasan.
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] Select * from NOT like '%partOfString%'

[Luigi Dell'Aquila]

+1, I'll do it asap

2017-10-19 18:00 GMT+02:00 Raymond Willems :

> Thanks! This works fine! I propose to take this example into the
> documentation.
>
> Best regards
> Raymond
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [orientdb] Re: Security Manager: Users list limited to 2 pages

[Luigi Dell'Aquila]

By default Studio limits the result sets to 20.
You can change this default clicking on the options (little button next to
the yellow "explain", bottom right corner of the query panel) or you can
explicitly add a LIMIT -1 to the SQL statement

Thanks

Luigi

2017-10-19 15:51 GMT+02:00 Raymond Willems :

> Same problem when using: select * from OUser
>
> Only two pages are shown.
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to orient-database+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to orient-database+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.