Erro do Elasticsearch: Elastica\Exception\ResponseException (SearchPhaseExecutionException)
991 views
Skip to first unread message
Gregory Bevilaqua
May 21, 2018, 9:53:45 AM5/21/18
to AtoM Users
Olá Dan,
Quanto estou clicando em "Ponto de Acesso - Assunto" ou "Ponto de Acesso - Local" em qualquer dos objetos aparece a seguinte mensagem de erro:
Já pesquisei em todos os tópicos e executei vários comandos, mas nenhum resolveu o problema...
Comandos que já executei:
- php symfony search:populate
- Limpei o Cache
- Reiniciei os serviços
O que poderia fazer para corrigir esse problema ?
Obs: "Ponto de Acesso - Nome" funciona perfeitamente, apenas os dois supracitados que dá esse erro.
Grato,
Gregory Bevilaqua
May 21, 2018, 9:56:34 AM5/21/18
to AtoM Users
Executei o comando "free" e me retornou o seguinte:
Será que pode ser falta de memória ?
Att,
Dan Gillean
May 21, 2018, 2:33:57 PM5/21/18
to ICA-AtoM Users
Hi Gregory,
Whenever you encounter a 500 error, it is useful to try to take a look at the webserver logs to see if there is more information. See:
Please feel free to share any related error message that you find there if the following suggestions do not help to resolve the issue.
I would also suggest trying to rebuild the nested set, and generate slugs. See:
- https://www.accesstomemory.org/docs/2.5/admin-manual/maintenance/troubleshooting/#rebuilding-the-nested-set
- https://www.accesstomemory.org/docs/2.5/admin-manual/maintenance/troubleshooting/#generating-slugs
You may want to repopulate the index, clear the cache, and restart PHP-FPM and memcached after trying these tasks as well.
If that still doesn't work... we may need to wait and see what further information you find in the error logs, if any. One possibility is that there is some data corruption in your database - we have some suggestions on how to check for this, and how to resolve the most common causes, here:
Let us know what you find.
Regards,
--
You received this message because you are subscribed to the Google Groups "AtoM Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-users+unsubscribe@googlegroups.com.
To post to this group, send email to ica-atom-users@googlegroups.com.
Visit this group at https://groups.google.com/group/ica-atom-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/9b6d322e-ed8a-4b2a-99e1-91081b894203%40googlegroups.com.
Gregory Bevilaqua
May 22, 2018, 11:12:27 PM5/22/18
to AtoM Users
Olá Dan,
Tentei tudo o que você falou, mas o problema ainda persiste...
Quando eu executo o comando: sudo tail -f /var/log/nginx/error.log , não traz nada de retorno, pois não está tendo nenhum erro no WebServer.
O problema está sendo especificamente com o ElasticSearch, no primeiro post mandei uma imagem mostrando o uso da memória e o erro....
O erro pode ser pouca memória ?
Grato
To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-user...@googlegroups.com.
To post to this group, send email to ica-ato...@googlegroups.com.
Visit this group at https://groups.google.com/group/ica-atom-users.
Dan Gillean
May 24, 2018, 11:50:56 AM5/24/18
to ICA-AtoM Users
Hi Gregory,
I suppose it is possible, though I have not seen a lack of memory lead to the inability to click on a field like that before. However, if you are able to assign more memory, then you should try!
Did you also run the nested set and slugs task, and try the query to check for data corruption in the link I provided?
If you increase the available memory, remember to restart services such as PHP-FPM after, and clear the application cache. Let us know if it helps! In the meantime, I will see if I can get further suggestions from our team.
Regards,
To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-users+unsubscribe@googlegroups.com.
To post to this group, send email to ica-atom-users@googlegroups.com.
Visit this group at https://groups.google.com/group/ica-atom-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/c7ee174f-93d8-4900-a3c9-91bae341f8ba%40googlegroups.com.
Gregory Bevilaqua
May 25, 2018, 6:26:56 PM5/25/18
to AtoM Users
Olá Dan,
Aumentei a memória e não resolveu o problema... Aproveito para falar que tentei todos os comandos que você disse, mas o erro ainda persiste.
Você poderia me ajudar de como devo proceder ?
Observação: "Ponto de Acesso- Nome" funciona perfeitamente... Os outros que não funcionam....
Agradeço pela atenção.
raddao...@gmail.com
May 28, 2018, 11:02:02 AM5/28/18
to AtoM Users
TestHi Gregory,
I'm not sure if I'm understanding well, but it looks like you're having an Elasticsearch error when going to a subject or place access point page, but not in name access point pages. The first two do a heavy use of Elasticsearch to show the related description with faceting options while the last one it only uses it to show a list of related descriptions in the sidebar.
Although it's an Elasticseach error what you're seeing, you're getting a 500 error in your site, so you should have something in the web server logs. You can also find some important information in the Elasticsearch log: /var/log/elasticsearch/elasticsearch.log.
Are you only getting that error in those pages? Is the archival description browse page (.../informationobject/browse) working?
Also, what versions of AtoM and Elasticsearch have you installed? AtoM 2.4 and lower should use Elasticsearch 1.7.
Regards.
Gregory Bevilaqua
Jul 3, 2018, 9:50:53 AM7/3/18
to AtoM Users
Olá, obrigado pela atenção.
A versão do Elasticsearch que estou usando é a 1.7.6.
O AtoM instalado está na versão 2.3.1
Quando verifico o ultimo arquivo de log em /var/log/elasticsearch/... Aparece o seguinte resultado=
[2018-07-01 12:57:19,059][DEBUG][action.search.type ] [Micromax] [atom][0], node[si87DsWRSX2bFezUR9eWgw], [P], s[STARTED]: Failed to execute [org.elasticsearch.action.search.SearchReque$
org.elasticsearch.search.SearchParseException: [atom][0]: from[-1],size[10]: Parse Failure [Failed to parse source [{"size":"10","sort":{"levelOfDescriptionId":"asc","identifier":"asc","i18n.$
at org.elasticsearch.search.SearchService.parseSource(SearchService.java:747)
at org.elasticsearch.search.SearchService.createContext(SearchService.java:572)
at org.elasticsearch.search.SearchService.createAndPutContext(SearchService.java:544)
at org.elasticsearch.search.SearchService.executeQueryPhase(SearchService.java:306)
at org.elasticsearch.search.action.SearchServiceTransportAction$5.call(SearchServiceTransportAction.java:231)
at org.elasticsearch.search.action.SearchServiceTransportAction$5.call(SearchServiceTransportAction.java:228)
at org.elasticsearch.search.action.SearchServiceTransportAction$23.run(SearchServiceTransportAction.java:559)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.elasticsearch.search.SearchParseException: [atom][0]: from[-1],size[10]: Parse Failure [No mapping found for [i18n.pt_BR.title] in order to sort on]
at org.elasticsearch.search.sort.SortParseElement.addSortField(SortParseElement.java:214)
at org.elasticsearch.search.sort.SortParseElement.addCompoundSortField(SortParseElement.java:140)
at org.elasticsearch.search.sort.SortParseElement.parse(SortParseElement.java:96)
at org.elasticsearch.search.SearchService.parseSource(SearchService.java:731)
... 9 more
[2018-07-01 12:57:19,060][DEBUG][action.search.type ] [Micromax] [atom][2], node[si87DsWRSX2bFezUR9eWgw], [P], s[STARTED]: Failed to execute [org.elasticsearch.action.search.SearchReque$
org.elasticsearch.search.SearchParseException: [atom][2]: from[-1],size[10]: Parse Failure [Failed to parse source [{"size":"10","sort":{"levelOfDescriptionId":"asc","identifier":"asc","i18n.$
at org.elasticsearch.search.SearchService.parseSource(SearchService.java:747)
at org.elasticsearch.search.SearchService.createContext(SearchService.java:572)
at org.elasticsearch.search.SearchService.createAndPutContext(SearchService.java:544)
at org.elasticsearch.search.SearchService.executeQueryPhase(SearchService.java:306)
at org.elasticsearch.search.action.SearchServiceTransportAction$5.call(SearchServiceTransportAction.java:231)
at org.elasticsearch.search.action.SearchServiceTransportAction$5.call(SearchServiceTransportAction.java:228)
at org.elasticsearch.search.action.SearchServiceTransportAction$23.run(SearchServiceTransportAction.java:559)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.elasticsearch.search.SearchParseException: [atom][2]: from[-1],size[10]: Parse Failure [No mapping found for [i18n.pt_BR.title] in order to sort on]
at org.elasticsearch.search.sort.SortParseElement.addSortField(SortParseElement.java:214)
at org.elasticsearch.search.sort.SortParseElement.addCompoundSortField(SortParseElement.java:140)
at org.elasticsearch.search.sort.SortParseElement.parse(SortParseElement.java:96)
at org.elasticsearch.search.SearchService.parseSource(SearchService.java:731)
... 9 more
[2018-07-01 12:57:19,059][DEBUG][action.search.type ] [Micromax] [atom][1], node[si87DsWRSX2bFezUR9eWgw], [P], s[STARTED]: Failed to execute [org.elasticsearch.action.search.SearchReque$
org.elasticsearch.search.SearchParseException: [atom][1]: from[-1],size[10]: Parse Failure [Failed to parse source [{"size":"10","sort":{"levelOfDescriptionId":"asc","identifier":"asc","i18n.$
at org.elasticsearch.search.SearchService.parseSource(SearchService.java:747)
at org.elasticsearch.search.SearchService.createContext(SearchService.java:572)
at org.elasticsearch.search.SearchService.createAndPutContext(SearchService.java:544)
at org.elasticsearch.search.SearchService.executeQueryPhase(SearchService.java:306)
at org.elasticsearch.search.action.SearchServiceTransportAction$5.call(SearchServiceTransportAction.java:231)
at org.elasticsearch.search.action.SearchServiceTransportAction$5.call(SearchServiceTransportAction.java:228)
at org.elasticsearch.search.action.SearchServiceTransportAction$23.run(SearchServiceTransportAction.java:559)
raddao...@gmail.com
Jul 3, 2018, 10:00:51 AM7/3/18
to AtoM Users
Hi Gregory,
The important error is:
No mapping found for [i18n.pt_BR.title] in order to sort on
Is it possible that the Brazilian Portuguese language was recently added to the available languages and that the search index was not rebuilt after it? Maybe going to the AtoM folder with a user with enough permission and running the following command fixes the issue:
php symfony search:populate
Best regards.
Gregory Bevilaqua
Jul 3, 2018, 10:12:25 AM7/3/18
to AtoM Users
Pronto, executei o comando e tive o seguinte retorno:
Index populated with 10040 documents in 82.75 seconds.
Quando tentei acessar novamente algum ponto de acesso de Assunto, deu o mesmo erro :(
Tem alguma outra sugestão para consertar esse erro?
Obrigado pela atenção.
raddao...@gmail.com
Jul 3, 2018, 11:13:41 AM7/3/18
to AtoM Users
Working this out via personal emails. I'll post back if we find any solution.
Regards.
Roberto JR
Mar 23, 2019, 4:09:42 PM3/23/19
to AtoM Users
Hello folks,
same problem ... (No mapping found for [i18n.pt_BR.title] in order to sort on).
changing the language to english (in menu) make it works (but in english, of course), Wonder who knows a solution.
thanks...
Dan Gillean
Mar 25, 2019, 11:51:15 AM3/25/19
to ICA-AtoM Users
Hi Roberto,
What is the default installation culture of your site? You can see this in apps/qubit/config/settings.yml.
Have you confirmed that Brazilian Portuguese has been added to AtoM via Admin > Settings > i18n languages? Have you tried re-indexing your site?
- php symfony search:populate
Does your site have a custom theme? If yes, can you reproduce the issue if you switch back to the default Dominion theme?
What is the full version number of AtoM listed in Admin > Settings > Global at the top of the page?
If you have explored all the above options without any results, you might want to check to see if there is any data corruption in your database. We have some suggestions on how to check for the most common causes here:
The other thing you could try is:
- Make a backup of your database
- You can find tips on how to do this in our upgrading documentation
- Purge all data:
- IMPORTANT: this will delete ALL data currently in AtoM, so make sure you have your database backup!
- php symfony tools:purge
- Drop and recreate the database: this should prune any unnecessary tables and columns in the database.
- The example below assumes your database username and password are root, and your database is named atom - swap in the correct credentials as needed
- mysql -u root -proot -e 'drop database atom; create database atom character set utf8 collate utf8_unicode_ci;'
- Reload your database
- Run the SQL upgrade task - this will make sure that you have the correct database schema version:
- php symfony tools:upgrade-sql
- Clear the application cache, restart services, and re-index the site
- php symfony cc
- Restarting services on Ubuntu 14.04:
- sudo service php5-fpm restart
- sudo service memcached restart
- Restarting services on Ubuntu 16.04:
- sudo systemctl restart php7.0-fpm
- sudo systemctl restart memcached
- php symfony search:populate
Let me know if any of the above helps! If not, please include answers to the questions at the beginning of my response, and I will see if our team has further suggestions.
Cheers,
--
You received this message because you are subscribed to the Google Groups "AtoM Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-user...@googlegroups.com.
To post to this group, send email to ica-ato...@googlegroups.com.
Visit this group at https://groups.google.com/group/ica-atom-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/4c2bca84-f4f8-4c89-8153-f65d937609c1%40googlegroups.com.
Roberto JR
Mar 25, 2019, 2:59:31 PM3/25/19
to ica-ato...@googlegroups.com
Hello Dan,
Thanks for the answer,
Many steps, I will follow carefully and return soon (hope it works!)
Thank you again
You received this message because you are subscribed to a topic in the Google Groups "AtoM Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ica-atom-users/p6VUnNqn1-I/unsubscribe.
To unsubscribe from this group and all its topics, send an email to ica-atom-user...@googlegroups.com.
To post to this group, send email to ica-ato...@googlegroups.com.
Visit this group at https://groups.google.com/group/ica-atom-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/CAC1FhZJN9pLRysDhPxSmUeC6xXbp%3DHkYwU0r_fYQMKKU%2BSNVLw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Roberto JR
Mar 25, 2019, 3:34:19 PM3/25/19
to ica-ato...@googlegroups.com
Hello, Dan
answering your questions:
What is the default installation culture of your site? You can see this in apps/qubit/config/settings.yml.
/usr/share/nginx/atom/apps/qubit/config/settings.yml
->default_culture: pt_BR
->default_timezone: America/Sao_Paulo
Have you confirmed that Brazilian Portuguese has been added to AtoM via Admin > Settings > i18n languages? Have you tried re-indexing your site?
I18n Language
Nooo. Oops. Added pt_BR now... 8O
sudo /usr/share/nginx/atom/symfony search:populate
Does your site have a custom theme? Not yet...
What is the full version number of AtoM listed in Admin > Settings > Global at the top of the page? 2.4.1 - 156
Well, I'll stop follow your instructions because it is working now!!!
*** I guess the error was the I18n pt_BR missing!!! (was only PT) ***
Thanks a lot!
8D
On Mon, Mar 25, 2019 at 12:51 PM Dan Gillean <d...@artefactual.com> wrote:
You received this message because you are subscribed to a topic in the Google Groups "AtoM Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ica-atom-users/p6VUnNqn1-I/unsubscribe.
To unsubscribe from this group and all its topics, send an email to ica-atom-user...@googlegroups.com.
To post to this group, send email to ica-ato...@googlegroups.com.
Visit this group at https://groups.google.com/group/ica-atom-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/CAC1FhZJN9pLRysDhPxSmUeC6xXbp%3DHkYwU0r_fYQMKKU%2BSNVLw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Dan Gillean
Mar 25, 2019, 3:35:42 PM3/25/19
to ICA-AtoM Users
I'm glad it was an easy issue to solve, Roberto!
Cheers,
To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/CAFZR1xpkenpVpAGwnBw3W%2BTKTzfU0GSpYY1CinvrM99NjS0Faw%40mail.gmail.com.
lunaria...@gmail.com
Jun 18, 2020, 8:49:54 AM6/18/20
to AtoM Users
Hello, I'm seeing this error too on an en_GB archive: https://archive.rscds.org
AtoM v 2.4.0-156
Here's the entry in the elasticsearch.log
[2020-06-18 13:09:22,843][DEBUG][action.search.type ] [Spirit of '76] [atom][2], node[U1XESTp6R2CIYmvFe7igoA], [P], s[STARTED]: Failed to execute [org.elasticsearch.action.search.SearchRequest@3de37d25] lastShard [true]
org.elasticsearch.search.SearchParseException: [atom][2]: from[0],size[100]: Parse Failure [Failed to parse source [{"size":"100","from":0,"facets":{"languages":{"terms":{"field":"i18n.languages","size":10}},"types":{"terms":{"field":"entityTypeId","size":10}},"maintainingRepository":{"terms":{"field":"maintainingRepositoryId","size":10}},"occupation":{"terms":{"field":"occupations.id","size":10}}},"sort":{"i18n.en_GB.authorizedFormOfName.untouched":"asc"},"query":{"bool":{"must":[{"match_all":{}}]}}}]]
at org.elasticsearch.search.SearchService.parseSource(SearchService.java:747)
at org.elasticsearch.search.SearchService.createContext(SearchService.java:572)
at org.elasticsearch.search.SearchService.createAndPutContext(SearchService.java:544)
at org.elasticsearch.search.SearchService.executeQueryPhase(SearchService.java:306)
at org.elasticsearch.search.action.SearchServiceTransportAction$5.call(SearchServiceTransportAction.java:231)
at org.elasticsearch.search.action.SearchServiceTransportAction$5.call(SearchServiceTransportAction.java:228)
at org.elasticsearch.search.action.SearchServiceTransportAction$23.run(SearchServiceTransportAction.java:559)
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)
Caused by: org.elasticsearch.search.SearchParseException: [atom][2]: from[0],size[100]: Parse Failure [No mapping found for [i18n.en_GB.authorizedFormOfName.untouched] in order to sort on]
at org.elasticsearch.search.sort.SortParseElement.addSortField(SortParseElement.java:214)
at org.elasticsearch.search.sort.SortParseElement.addCompoundSortField(SortParseElement.java:140)
at org.elasticsearch.search.sort.SortParseElement.parse(SortParseElement.java:96)
at org.elasticsearch.search.SearchService.parseSource(SearchService.java:731)
... 9 more
Here the relevant bit of my \usr\share\nginx\atom\apps\qubit\config\settings.yml
# The language is coded in two lowercase characters,
# according to the ISO 639-1 standard, and the country
# is coded in two uppercase characters, according to
# the ISO 3166-1 standard.
# Examples: en, en_US, es_ES, fr...
default_culture: en_GB
# List of supported timezones
default_timezone: Europe/London
The quick fix is to click the language icon on the toolbar and select "English" but clearing the browser cache brings the error back.
The default langues in settings in the app is English:
I've tried rebuilding the search index, nested set and slugs and checked for data corruption, all to no avail.
Any help is appreciated.
José Raddaoui
Jun 18, 2020, 10:25:03 AM6/18/20
to AtoM Users
Hi there,
The "en_GB" (British English) is missing in the enabled languages settings. Enabling it and running the search:populate task should solve the issue.
Best regards.
lunaria...@gmail.com
Jun 18, 2020, 10:38:56 AM6/18/20
to AtoM Users
Sorted ! Fantastic, thank you José
Dan Field
Jun 30, 2021, 10:02:05 AM6/30/21
to AtoM Users
We're seeing this error now on a well established Atom 2.4 install. It suddenly crept up overnight.
What is strange is that some queries work whereas other fail.
Some times we see
Caused by: org.elasticsearch.search.SearchParseException: [atom][3]: from[0],size[10]: Parse Failure [No mapping found for [i18n.cy.title.untouched] in order to sort on]
(We have Welsh language enabled and always have had)
Other times it can be
Caused by: org.elasticsearch.search.SearchParseException: [atom][3]: from[0],size[20]: Parse Failure [No mapping found for [dates.endDate] in order to sort on]
Dan Field
Jun 30, 2021, 11:21:36 AM6/30/21
to AtoM Users
I've included the output from:
$ curl localhost:9200/_mapping?pretty
It looks like reasonable atom data to me but does seem to not contain the fields that are being complained about e.g. startDate, endDate, untouched
{
"atom" : {"mappings" : {
"QubitInformationObject" : {
"properties" : {
"alternativeIdentifiers" : {
"properties" : {
"identifier" : {
"type" : "string"
},
"label" : {
"type" : "string"
}
}
},
"ancestors" : {
"type" : "string"
},
"children" : {
"type" : "string"
},
"createdAt" : {
"type" : "date",
"format" : "dateOptionalTime"
},
"creators" : {
"properties" : {
"createdAt" : {
"type" : "date",
"format" : "dateOptionalTime"
},
"entityTypeId" : {
"type" : "string"
},
"i18n" : {
"properties" : {
"en" : {
"properties" : {
"authorizedFormOfName" : {
"type" : "string"
},
"history" : {
"type" : "string"
}
}
},
"languages" : {
"type" : "string"
}
}
},
"id" : {
"type" : "string"
},
"slug" : {
"type" : "string"
},
"sourceCulture" : {
"type" : "string"
},
"updatedAt" : {
"type" : "date",
"format" : "dateOptionalTime"
}
}
},
"dates" : {
"properties" : {
"actorId" : {
"type" : "string"
},
"i18n" : {
"properties" : {
"en" : {
"properties" : {
"date" : {
"type" : "string"
}
}
},
"languages" : {
"type" : "string"
}
}
},
"sourceCulture" : {
"type" : "string"
},
"typeId" : {
"type" : "string"
}
}
},
"directPlaces" : {
"type" : "string"
},
"directSubjects" : {
"type" : "string"
},
"findingAid" : {
"properties" : {
"status" : {
"type" : "long"
}
}
},
"generalNotes" : {
"properties" : {
"i18n" : {
"properties" : {
"en" : {
"properties" : {
"content" : {
"type" : "string"
}
}
},
"languages" : {
"type" : "string"
}
}
},
"sourceCulture" : {
"type" : "string"
}
}
},
"hasDigitalObject" : {
"type" : "boolean"
},
"i18n" : {
"properties" : {
"en" : {
"properties" : {
"accessConditions" : {
"type" : "string"
},
"accruals" : {
"type" : "string"
},
"acquisition" : {
"type" : "string"
},
"archivalHistory" : {
"type" : "string"
},
"arrangement" : {
"type" : "string"
},
"extentAndMedium" : {
"type" : "string"
},
"findingAids" : {
"type" : "string"
},
"institutionResponsibleIdentifier" : {
"type" : "string"
},
"locationOfCopies" : {
"type" : "string"
},
"physicalCharacteristics" : {
"type" : "string"
},
"relatedUnitsOfDescription" : {
"type" : "string"
},
"reproductionConditions" : {
"type" : "string"
},
"revisionHistory" : {
"type" : "string"
},
"rules" : {
"type" : "string"
},
"scopeAndContent" : {
"type" : "string"
},
"sources" : {
"type" : "string"
},
"title" : {
"type" : "string"
}
}
},
"languages" : {
"type" : "string"
}
}
},
"identifier" : {
"type" : "string"
},
"levelOfDescriptionId" : {
"type" : "string"
},
"lft" : {
"type" : "string"
},
"names" : {
"properties" : {
"createdAt" : {
"type" : "date",
"format" : "dateOptionalTime"
},
"entityTypeId" : {
"type" : "string"
},
"i18n" : {
"properties" : {
"en" : {
"properties" : {
"authorizedFormOfName" : {
"type" : "string"
},
"history" : {
"type" : "string"
},
"rules" : {
"type" : "string"
},
"sources" : {
"type" : "string"
}
}
},
"languages" : {
"type" : "string"
}
}
},
"id" : {
"type" : "string"
},
"slug" : {
"type" : "string"
},
"sourceCulture" : {
"type" : "string"
},
"updatedAt" : {
"type" : "date",
"format" : "dateOptionalTime"
}
}
},
"parentId" : {
"type" : "string"
},
"partOf" : {
"properties" : {
"i18n" : {
"properties" : {
"en" : {
"properties" : {
"title" : {
"type" : "string"
}
}
},
"languages" : {
"type" : "string"
}
}
},
"id" : {
"type" : "string"
},
"slug" : {
"type" : "string"
},
"sourceCulture" : {
"type" : "string"
}
}
},
"physicalObjects" : {
"properties" : {
"i18n" : {
"properties" : {
"en" : {
"properties" : {
"location" : {
"type" : "string"
},
"name" : {
"type" : "string"
}
}
},
"languages" : {
"type" : "string"
}
}
},
"sourceCulture" : {
"type" : "string"
}
}
},
"places" : {
"properties" : {
"createdAt" : {
"type" : "date",
"format" : "dateOptionalTime"
},
"i18n" : {
"properties" : {
"en" : {
"properties" : {
"name" : {
"type" : "string"
}
}
},
"languages" : {
"type" : "string"
}
}
},
"id" : {
"type" : "string"
},
"isProtected" : {
"type" : "boolean"
},
"numberOfDescendants" : {
"type" : "string"
},
"slug" : {
"type" : "string"
},
"sourceCulture" : {
"type" : "string"
},
"taxonomyId" : {
"type" : "string"
},
"updatedAt" : {
"type" : "date",
"format" : "dateOptionalTime"
}
}
},
"publicationStatusId" : {
"type" : "string"
},
"referenceCode" : {
"type" : "string"
},
"referenceCodeWithoutCountryAndRepo" : {
"type" : "string"
},
"repository" : {
"properties" : {
"contactInformations" : {
"properties" : {
"contactPerson" : {
"type" : "string"
},
"countryCode" : {
"type" : "string"
},
"i18n" : {
"properties" : {
"cy" : {
"properties" : {
"city" : {
"type" : "string"
},
"region" : {
"type" : "string"
}
}
},
"en" : {
"properties" : {
"city" : {
"type" : "string"
},
"region" : {
"type" : "string"
}
}
},
"languages" : {
"type" : "string"
}
}
},
"postalCode" : {
"type" : "string"
},
"sourceCulture" : {
"type" : "string"
},
"streetAddress" : {
"type" : "string"
}
}
},
"createdAt" : {
"type" : "date",
"format" : "dateOptionalTime"
},
"i18n" : {
"properties" : {
"cy" : {
"properties" : {
"accessConditions" : {
"type" : "string"
},
"city" : {
"type" : "string"
},
"collectingPolicies" : {
"type" : "string"
},
"descInstitutionIdentifier" : {
"type" : "string"
},
"descRevisionHistory" : {
"type" : "string"
},
"descRules" : {
"type" : "string"
},
"descSources" : {
"type" : "string"
},
"disabledAccess" : {
"type" : "string"
},
"findingAids" : {
"type" : "string"
},
"history" : {
"type" : "string"
},
"internalStructures" : {
"type" : "string"
},
"openingTimes" : {
"type" : "string"
},
"publicFacilities" : {
"type" : "string"
},
"region" : {
"type" : "string"
},
"reproductionServices" : {
"type" : "string"
},
"researchServices" : {
"type" : "string"
}
}
},
"en" : {
"properties" : {
"accessConditions" : {
"type" : "string"
},
"authorizedFormOfName" : {
"type" : "string"
},
"city" : {
"type" : "string"
},
"collectingPolicies" : {
"type" : "string"
},
"descInstitutionIdentifier" : {
"type" : "string"
},
"descRevisionHistory" : {
"type" : "string"
},
"descRules" : {
"type" : "string"
},
"descSources" : {
"type" : "string"
},
"disabledAccess" : {
"type" : "string"
},
"findingAids" : {
"type" : "string"
},
"history" : {
"type" : "string"
},
"internalStructures" : {
"type" : "string"
},
"openingTimes" : {
"type" : "string"
},
"publicFacilities" : {
"type" : "string"
},
"region" : {
"type" : "string"
},
"reproductionServices" : {
"type" : "string"
},
"researchServices" : {
"type" : "string"
}
}
},
"languages" : {
"type" : "string"
}
}
},
"id" : {
"type" : "string"
},
"identifier" : {
"type" : "string"
},
"logoPath" : {
"type" : "string"
},
"slug" : {
"type" : "string"
},
"sourceCulture" : {
"type" : "string"
},
"types" : {
"type" : "string"
},
"updatedAt" : {
"type" : "date",
"format" : "dateOptionalTime"
}
}
},
"slug" : {
"type" : "string"
},
"sourceCulture" : {
"type" : "string"
},
"subjects" : {
"properties" : {
"createdAt" : {
"type" : "date",
"format" : "dateOptionalTime"
},
"i18n" : {
"properties" : {
"en" : {
"properties" : {
"name" : {
"type" : "string"
}
}
},
"languages" : {
"type" : "string"
}
}
},
"id" : {
"type" : "string"
},
"isProtected" : {
"type" : "boolean"
},
"numberOfDescendants" : {
"type" : "string"
},
"slug" : {
"type" : "string"
},
"sourceCulture" : {
"type" : "string"
},
"taxonomyId" : {
"type" : "string"
},
"updatedAt" : {
"type" : "date",
"format" : "dateOptionalTime"
}
}
},
"updatedAt" : {
"type" : "date",
"format" : "dateOptionalTime"
Ndivhuwo Phaduli
Nov 27, 2023, 8:44:41 AM11/27/23
to AtoM Users
Elasticsearch error: Elastica\Exception\Connection\HttpException am experiencing this error kindly assist with a permanent solution
To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-user...@googlegroups.com.
To post to this group, send email to ica-ato...@googlegroups.com.
Visit this group at https://groups.google.com/group/ica-atom-users.
Reply all
Reply to author
Forward
0 new messages