Using the GraphDB workbench, I have built a few Similarity indexes The first is just the default query and two custom ones. These worked fine for the build. Now they have a status of outdated but the refresh feature is disabled, the UI will not allow a click, instead presenting bubble indicating I cant do it. Only the delete feature is allows. Has anyone determined why this happens and how to fix it? This is the 3rd time it has happened. Yes I can drop a rebuild but I would prefer to find out why its happening. The logs do not appear to have anything related to this.
Thanks
Similarity queries needed for index rebuild are stored in Workbench settings file in GraphDB Home /work/workbench/settings.js. This may happen if you change your GraphDB Home. Please, also check if you have some errors on initialization.
Related
I have the IDEA Ultimate 2018.1 with flowtype (flow-bin) configured and all the checkboxes selected. I followed this guide: https://www.jetbrains.com/help/idea/2017.2/flow-type-checker.html
The type checking needs much time to be executed. I change something in my code (reverting a wrong annotation, or creating a wrong one), and I need to wait around 30 seconds to get the correct annotation, this is, IDEA triggers the flow server to analyse the files and modify the editor accordingly. That is quite a lot.
Can I trigger that type checking analysis manually inside IDEA to get the editor updated? Or can I change the auto-running interval?
As Kraus noticed, my version of flow-bin was old.
I was using the version 0.26.0 instead of the new 0.74.0, mainly because when I updated flow I was not using flow-bin but flow...
Thanks. Now IDEA and flow are fast.
I have an internal Apache server for testing purpose, not client facing.
I wanted to upgrade the server to apache 2.4, but there is no space left, so I was trying to delete some files on the server.
After checking file size, I found a folder /var/lib/elasticsearch takes 80g space. For example, /var/lib/elasticsearch/elasticsearch/nodes/0/indices/logstash-2015.12.08 takes 60g already. I'm not sure what's elasticsearch. Is it safe if i delete this logstash? Thanks!
Elasticsearch is a search engine, like a NoSql database, and it stores the data in indeces. What you are seeing is the data of one index.
Probobly someone was using the index aroung 2015 when the index was timestamped.
I would just delete it.
I'm afraid that only you can answer that question. One use for logstash+elastic search are to help make sense out of system logs. That combination isn't normally setup by default, so I presume someone set it up at some time for some reason, and it has obviously done some logging. Only you can know if it is still being used, or if it is safe to delete.
As other answers pointed out Elastic search is a distributed search engine. And I believe an earlier user was pushing application or system logs using Logstash to this Elastic search instance. If you can find the source application, check if the log files are already there, if yes, then you can go ahead and delete your index. I highly doubt anyone still needs the logs back from 2015, but it is really your call to see what your application's archiving requirements are and then take necessary action.
I am new to sitecore and currently in sitecore developer training. Today I ahve faced weird issue and after trainer also not able to resolve, I think I should post in this forum.
I have added some custom search field to the solution. These fields also added in Lucene Default Search config. After deploying the solution, I am tried to rebuild index option from developer menu, However I am unable to see any Indexes list over there. I am getting message as "Indexes List Failed to Render"
Also I have tried
sitecore desktop-> Control Panel-> Indexing-> Indexing manager But
Sitecore dialog box does not pop up.
desktop-> Control Panel-> Database-> Rebuild index didnt work.
IIS Reset.
Any help in this regard is highly appreciated. Thanks in advance!!
I would recommend you patch in a separate config with your custom index configuration than changing the default lucene index config. You may need to post your custom field configuration so we can figure out what's causing the error.
Thanks for help. I have now able to figure out what was going wronng. I have not made changes using patch and and messed up directly into the Sitecore.Content.Search.config instead of Lucene config. Because of this changes I am having Sitecore Configuration exception and that caused to indexes list disapper.
I had a similar issue and this worked for me
While integrating Solr, I disabled all Lucene configs and after that internal search wasn't working, and also no search indexes were visible in the developer tab. I enabled this config and its all good now
Sitecore.ContentSearch.Lucene.Indexes.Sharded.Master.config
I'm working on a couple of million records, as soon as I try to run an advanced find, and put as a criteria a linked entity, the advanced find goes in timeout.
Create custom views on this allows me to filter properly? Anyone knows the proper way of using the advanced find this way? Are there limitations on the out of the box CRM that i should be aware of?
In CRM 2013 - it is possible to add indexes for specific fields by adding the columns to the quick find view for the entity.
You will need to wait for the Indexing Management Job to run (which is run every 24 hours by default) - see http://blogs.msdn.com/b/darrenliu/archive/2014/04/02/crm-2013-maintenance-jobs.aspx.
In previous version of CRM, it was necessary to add the indexes directly to the database - this may be necessary for more complex queries.
was too early to post an answer. The problem that I encountered was related to the OOB advanced find. Looking for example for an account with some related contacts (a really plain search with a linked entity) i had a SQL timeout. Everything was OOB so I was a little bit clueless and I opened a case to Microsoft. They found a bug, if i was changing the sorting the advanced find started to work again. They are still investigating. So wasn't a setting problem but a crm bug.
I've been using Toad for more than a year now without problems. All of a sudden the table autocomplete feature has ceased working. No settings have been changed, and I've clean installed a new TOAD version, yet the problem persists.
The image below shows autocomplete defaulting into view IN_INSTRUMENT in schema MCDM. Normal behaviour should result in a table/view list.
It is notable that the above does not happen with all schemas. For some schemas I will still see a table list. In the beginning this error happened only with a single schema. Now it is slowly progressing to other schemas as well, which is exceptionally frustrtating when you're dealing with dozens of schemas that contain hundreds of tables each. It slows down development when you must open Schema Browser and look for the exact table/view/procedure/package each time instead of letting autocomplete give suggestions.
This same issue has been described in this thread and and this thread with less detail, yet no accepted answer has been given.
As can be seen from Code Assist settings, these should be in order.
How to reset autocomplete behaviour into what is its original state?
Under View > Toad Options > Editor > Code Assist > Toad Insight Objects, checking Synonyms (in addition to Public Synonyms) worked for me.
I've found the solution to this problem. The issue was a corrupt configuration file. For anyone else with the same problem, this is how I fixed mine:
Backup your appdata folder - you can find its location in options -> general -> application data.
Create a new set of user files using Utilities -> Copy User Settings -> Create clean set of user files. Make sure you are running Toad with administrator rights.
Note that the above will delete all your saved connection details (schema names, passwords, connection strings), so take a note of these.
Hope this helps someone in the future.
Try to check "Public synonyms" in the "Toad insight objects".
Go to Toad Options, and then Editor > Code Assist and uncheck "Cache Code Insight results". This made it immediately start working for me using Toad for Oracle version 9.7. I could then go back and check the box and it would still work.
I faced the same problem even though I set up everything mentioned above.
So basically Toad does not suggest column names if I don't define the scheme name.
X(schema).TABLE_NAME.(then lists all columns)
Worked for me..