The Altair Community is migrating to a new platform to provide a better experience for you. In preparation for the migration, the Altair Community is on read-only mode from October 28 - November 6, 2024. Technical support via cases will continue to work as is. For any urgent requests from Students/Faculty members, please submit the form linked here
Metadata issues - Store/Retrieve
hughesfleming68
Member Posts: 323
Unicorn
Unicorn
If I had metadata issues in the past I would usually work around them by storing the data set to the repository. Retrieving it would restore the metadata correctly. This would usually happen after an execute R or Python but also transposing a data table. I am finding in 9.21 that this does not work when I run the process. This has nothing to do with the order of the process. To get select attributes for example to see the metadata from a data set retrieved from the repository I have to shutdown and restart Rapidminer and then it works. Running the process with breakpoints sometimes works but when all else fails, restarting Rapidminer is the only option.
On a long process this is a real headache.
regards,
Alex
On a long process this is a real headache.
regards,
Alex
Tagged:
0
Comments
-
Hi Alex,you have always the option of synchronizing meta data with real data:
In general it works, but it's not instantaneous, you may have to run the process a couple of times.I agree that the meta data handling doesn't work as expected, this is maybe an issue that has been overlooked in favor of new features.Best regards,Sebastian0 -
Thanks Sebastian, I tried that but it didn't make a difference.I know where the problem is starting and that it is with execute R. I know I should sort out the metadata inside R but saving to the repository was a quick workaround. Running the process used to be enough to solve that problem. Restarting Rapidminer and reloading the process fixes this but that is a rather extreme workaround.0
-
I think that when the pipeline goes into the Execute R operator, RapidMiner doesn't have a clue about the output of the operator. A faster workaround could be to have a dataset in the repository with the same attributes but only a few rows and use it for development of the process. That is actually what I also do with big datasets.Regards,Sebastian0
-
To be honest, I think this problem is specific to RM91 and newer. I didn't have this problem with older versions of Rapidminer.
regards,
Alex0 -
sgenzer Administrator, Moderator, Employee-RapidMiner, RapidMiner Certified Analyst, Community Manager, Member, University Professor, PM Moderator Posts: 2,959
Community Manager
0 -
Hi @hughesfleming68 ,I do think that it has something to do with how we manage and create metadata since 9.1. We will look into this.The thing that is actually happening here is that the Retrieve operator is not updated if the repository entry was created later.A workaround for now would be to change the repository location to something different and back again.CheersJan@sgenzer, please move this to Product Feedback1
-
Thanks for the explanation Jan.0
-
@jczogalla I have been experiencing another problem with Store and Retrieve that I think could be related to metadata and the changes since 9.1. Studio will sometimes hang when trying to configure the Store or Retrieve path using the file browser that is part of the parameters panel. It seems to be choking on navigating the repository although there are no problems browsing my repository in the repository window. You might want to check with Helge Homburg to see whether these problems are related as he has been investigating that issue.0
-
@Telcontar120 thank you for the hint, will do!
0


