Skip to main content
Question

Update mongodb reader

  • December 13, 2019
  • 4 replies
  • 17 views

pg.souque
Forum|alt.badge.img

Hi,When i update my mongodb reader with "update reader and feature types" one column (properties.observations) of my collection (that i see with robomongo) doesn't appear in User attribute. I have try many times but nothing happen. It's really a big problem for me. The same thing when i delete and create my reader.

When i use format attribute/mongodbjson i retrieve this column in the column mongodb_json

Is it a bug ?

Best regards

4 replies

pg.souque
Forum|alt.badge.img
  • Author
  • December 13, 2019

After tests:

- If i have null values: no column

- if i have null values and string values: no column

- if i have string value: YESSS it works

 

I think something is wrong...


chrisatsafe
Contributor
Forum|alt.badge.img+2
  • Contributor
  • December 16, 2019
pg.souque wrote:

After tests:

- If i have null values: no column

- if i have null values and string values: no column

- if i have string value: YESSS it works

 

I think something is wrong...

Hi @pg.souque,

Just wanted to confirm, what build of FME are you working with? Interesting that we are only reading in the properties.observations attribute if they values are not null.

Do you have the same issue when the Read Original JSON Document parameter is set to yes?


pg.souque
Forum|alt.badge.img
  • Author
  • December 17, 2019
pg.souque wrote:

After tests:

- If i have null values: no column

- if i have null values and string values: no column

- if i have string value: YESSS it works

 

I think something is wrong...

Hi,

Thank you for your answer.

This is build 19801 for WIN64.

Yes same problem if the Read Original JSON Document parameter is set to yes.

If i put a value in all document it's ok but if only some documents have this value so the update don't work.

Best regards

 


chrisatsafe
Contributor
Forum|alt.badge.img+2
  • Contributor
  • December 17, 2019
pg.souque wrote:

Hi,

Thank you for your answer.

This is build 19801 for WIN64.

Yes same problem if the Read Original JSON Document parameter is set to yes.

If i put a value in all document it's ok but if only some documents have this value so the update don't work.

Best regards

 

Hi @pg.souque,

Thanks for the follow up.

I have created an issue report (FMEENGINE-62528) in our system for this. It seems the MongoDB schema is established based on the first batch of features and, in your case, the first batch may not contain a non-null value in the first batch which is causing the unexpected behavior.

I'll follow up on this thread as soon as we release solution for this!


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings