WordList to Data gives me example set with no attribute names

mizunooto

I'm runningProcess Documentsto get a word list which I then convert to data usingWordList to Data. All goes well until I try to select, filter or otherwise use the dataset thus created. I cannot see any attribute names in the data. I can manually type them in (e.g. inSelect Attributes,但不是所有运营商允许这样), but subsequent operators in the chain do not see the names.

I have triedSynchronize MetadataandMateriaize Data, but neither of these helps.

In the example, the finalSelect Attributesoperator does not allow me to select attributes from a list, although I can type "word" into the box when the filter type is "single".

Any ideas?

Telcontar120

Yes, this is an annoying RapidMiner bug. It's purely a metadata propagation problem. If you tried to use the "Synchronize Meta Data with Real Data" option but it didn't solve the problem, you can still add the attributes you want manually when selecting the "subset" option. Just type the name of the attributes into the box in the right hand side and then click the green plus button (see screenshot). They won't autopopulate but they will actually work when you run the process.

mizunooto

Thanks - glad it's not just me!

Given that it's a bug, I've got a workaround which is to generate new attributes (equal to the existing attributes) after the dataset conversion. I can then select the new attributes as per normal and throw away the old, hidden attributes. A bit of a faff, but as the issue propagates all through the workflow, it's easier this way.

Telcontar120

@mizunootoI'd love to see the process you are using to do that---I am assuming you are doing it in some kind of automated fashion and not just typing in all the new attribute names manually?

mizunooto

Imagination is a wonderful thing... at present I'm only using a couple of attributes so a manual operation is fine.

e.g. newword = word

Automation sounds like a great idea but I'll need to learn more to make it work.

sgenzer

yes that's a metadata propagation error for sure. Pushing this thread to Product Feedback.

Scott

sgenzer

Metadata problem recognized and reported to dev team. Please watch this board for updates.

SG

sgenzer

just to confirm with people watching this issue - toggling the "Synchronize Metadata with Real Data" feature does not resolve this, correct?

Telcontar120

Correct, the "Sychronize Metadata" option doesn't fix this particular problem. I've found that it doesn't correct it 100% of the time, there are a few other cases where I have found similar behavior.