hi folks, I managed to do all the ingest of the gl...
# ingestions
silly-beach-19296
02/28/2022, 5:43 PMhi folks, I managed to do all the ingest of the glossary terms, but when manually associating the terms to the columns they do not appear in related entities
plus1 1
silly-beach-19296
02/28/2022, 5:44 PMI tried to run the job to index, but it didn't work anyway.
plus1 1
b
big-carpet-38439
02/28/2022, 5:49 PMUh oh - believe this is an issue related to the spaces here. Let me try to reproduce locally and get back soon
big-carpet-38439
02/28/2022, 10:27 PMWhich version are you running? I know this was a problem a while back
big-carpet-38439
02/28/2022, 10:29 PMStrange I haven't been able to reproduce..
big-carpet-38439
02/28/2022, 10:30 PMI even tried creating the term with same name
big-carpet-38439
02/28/2022, 10:30 PMbig-carpet-38439
02/28/2022, 10:30 PMlet me try one more thing
big-carpet-38439
02/28/2022, 10:37 PMAh I've managed to reproduce this in cases where the parent glossary node also has spaces in the name
s
silly-beach-19296
03/01/2022, 4:03 AMfor the moment, remove the spaces and special characters (Spanish), it worked fine for me. But what I saw is that at the level of the arn it creates it with spaces and that is the problem when indexing, the URN with "&" in the spaces of the URL was not recognized, but with the spaces (this when trying to permanently delete ) example :
{"urn":"urn:li:glossaryTerm:Ops. Previsionales y Créditos.Afiliado"}s
shy-kitchen-7972
05/05/2022, 9:15 AMIs this logged as bug or do is it the datahbub practice to create nodes without the spaces?
2 Views