z-logo
Premium
Sugar demand of ripening grape berries leads to recycling of surplus phloem water via the xylem
Author(s) -
KELLER MARKUS,
ZHANG YUN,
SHRESTHA PRADEEP M.,
BIONDI MARCO,
BONDADA BHASKAR R.
Publication year - 2015
Publication title -
plant, cell and environment
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 2.646
H-Index - 200
eISSN - 1365-3040
pISSN - 0140-7791
DOI - 10.1111/pce.12465
Subject(s) - xylem , phloem , ripening , berry , apoplast , transpiration , transpiration stream , horticulture , sugar , botany , biology , chemistry , photosynthesis , cell wall , food science
Abstract We tested the common assumption that fleshy fruits become dependent on phloem water supply because xylem inflow declines at the onset of ripening. Using two distinct grape genotypes exposed to drought stress, we found that a sink‐driven rise in phloem inflow at the beginning of ripening was sufficient to reverse drought‐induced berry shrinkage. Rewatering accelerated berry growth and sugar accumulation concurrently with leaf photosynthetic recovery. Interrupting phloem flow through the peduncle prevented the increase in berry growth after rewatering, but interrupting xylem flow did not. Nevertheless, xylem flow in ripening berries, but not berry size, remained responsive to root or shoot pressurization. A mass balance analysis on ripening berries sampled in the field suggested that phloem water inflow may exceed growth and transpiration water demands. Collecting apoplastic sap from ripening berries showed that osmotic pressure increased at distinct rates in berry vacuoles and apoplast. Our results indicate that the decrease in xylem inflow at the onset of ripening may be a consequence of the sink‐driven increase in phloem inflow. We propose a conceptual model in which surplus phloem water bypasses the fruit cells and partly evaporates from the berry surface and partly moves apoplastically to the xylem for outflow.

This content is not available in your region!

Continue researching here.

Having issues? You can contact us here