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
Using Database Table for Scoring in Deployment View
RapidMinerUser12
Member Posts: 11 
Learner I
Hi all,
I'm working on a project where I need to use the Deployment View for scoring the models.
So, when I import the scoring data, the dialog shows me all of my existing repositories, from where I can choose my data.
To my knowledge, database tables cannot be accessed directly, they need to be stored in some repository first (Read Database operator, then Store operator). Is there any work-around to this - a way to access the tables directly from the database and import them into Deployment view? The database tables I'm using for scoring have millions of rows of data. I'll lose a lot of time if I store them first.
Thank you in advance.
I'm working on a project where I need to use the Deployment View for scoring the models.
So, when I import the scoring data, the dialog shows me all of my existing repositories, from where I can choose my data.
To my knowledge, database tables cannot be accessed directly, they need to be stored in some repository first (Read Database operator, then Store operator). Is there any work-around to this - a way to access the tables directly from the database and import them into Deployment view? The database tables I'm using for scoring have millions of rows of data. I'll lose a lot of time if I store them first.
Thank you in advance.
1
Best Answer
-
IngoRM
Employee-RapidMiner, RapidMiner Certified Analyst, RapidMiner Certified Expert, Community Manager, RMResearcher, Member, University Professor Posts: 1,751 
RM Founder
Hi,No, that is not possible. The reason why we require a repository is so that we have full control over meta data like column types etc. which makes the scoring more robust. Without this it quickly becomes a bit of gamble if the scoring works or not (although it is relatively robust).We may change this in the future, but for now repository entries are the only supported input for bulk scoring.Best,Ingo7
